Please assist with clearer setup instructions

[mvallevand]

1) Run in and see if it is running in host mode. That is easier for your to debug.

2) The IP of your OMV host which is also the IP of the the NextPVR that you should be trying to connect with http://IP:8866

Martin

[sub]

" Don't forget to change the HOST as noted in the original post I linked to."
what ip is this?  The ip of the server?  The ip of the network tuner?

It's the IP address of your OMV machine on your home network. NextPVR has no visibility of this address inside the docker container, but needs to know it when you're using an older HDHomeRun tuner, so the HOST_IP environment variable in this docker compose file is a way to let NextPVR know the address.

[JonnyGators]

1) Run in and see if it is running in host mode. That is easier for your to debug.

2) The IP of your OMV host which is also the IP of the the NextPVR that you should be trying to connect with http://IP:8866

Martin

- "host.docker.internal:host-gateway" - is this line literal, or is this information I should know? If this is information I need to fill in, what is it, how do I find it?

[JonnyGators]

" Don't forget to change the HOST as noted in the original post I linked to."
what ip is this?  The ip of the server?  The ip of the network tuner?

It's the IP address of your OMV machine on your home network. NextPVR has no visibility of this address inside the docker container, but needs to know it when you're using an older HDHomeRun tuner, so the HOST_IP environment variable in this docker compose file is a way to let NextPVR know the address.

Still nothing!

Browsing to the ip of my server:8866 consistently results in a refused to connect error.

ip address on it's own still consistently works to load the OMV console, and ip address with correct following information works to load my plex server, which is running in docker as well.

Server works.

IP address is correct.

Docker works with up and running plex server.

So I have working OMV, Docker, server - but no NextPVR, this is clearly a NextPVR issue.

[sub]

What exactly did OMV say when you tried ‘docker-compose up’? (Or it’s equivalent if using a GUI)

Surely it either tells you it’s a success or gives you some error message.

[JonnyGators]

What exactly did OMV say when you tried ‘docker-compose up’? (Or it’s equivalent if using a GUI)

Surely it either tells you it’s a success or gives you some error message.

There is no "docker-compose up"

There is pasting the syntax into docker-files, and saving/applying.

I reviewed my notes and correspondences from setting up my plex server in docker, at no point in that process did I do anything to the effect of docker-compose up.  My response to the person assisting me was that (once I fixed a setting in docker that was preventing me from saving/applying the syntax to docker-files), I pasted the syntax, I saved, I applied, and then it worked, my plex server was up, and my folders were accessible to add libraries.

I can only speculate that the "docker-compose up" syntax you are referring to is something OMV automatically runs in the background after I paste and save the syntax into the gui.

[sub]

It sounds like you're missing some OMV specific step somewhere, so it's never actually starting it.

[mvallevand]

Maybe if your aren't running command line programs did you setup Plex using a GUI like this with Portainer https://www.wundertech.net/how-to-instal...ediavault/

Martin

[sub]

Did you click this "up" button on NextPVR? ie, should say Status is "Up" next to NextPVR. Below is a screenshot of someone doing it for another app they were installing (called 'portainer')

[JonnyGators]

Ok - here's the important part. I am not using portainer.

Here's the backstory for me to say this - some years ago I followed an online guide to setup plex using portainer, it worked for a few months, it was an unstable mess, eventually it completely stopped working, which resulted in lots of frustrating conversations on the plex forums until I finally found someone there that actually knew what he was doing, which led to the command line docker setup that had a flaw that it would never restart so anytime the server restarted I had to rerun the script and recreate the entire thing, which led to more conversation which led to adding the docker-containers stuffs that I currently use.

But I do not use portainer.

When I go into services-compose-files, there is no item listed in there.

Not having NextPVR where you expect me to would suggest it isn't setup - but remember, I have a working Plex server setup in docker, and that's not listed there either.

If I go into services-compose-dockerfiles, that is where I have 2 entries, one for plex, the other that I created today for NextPVR.

There's no up button. But there is a build button. Perhaps I'm supposed to click that to build it after saving it and applying it? I don't remember if I did that for plex or not, only did that once, so it's easy to forget little steps. Very unintuitive setup.

Anyways, if I click build, I get an error.

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker build --progress plain --tag 'NextPVR' '/srv/dev-disk-by-label-Storage/Plex-OMV/NextPVR/' 2>&1': ERROR: invalid tag "NextPVR": repository name must be lowercase


I reviewed the syntax and title I put in - and verified everywhere I typed nextpvr it was all lowercase, so I do not know where this invalid tag that must be lowercase is coming from, or how to fix it.