Apple TV 4k app not finding NextPVR (Docker) server

[stash201518]

Like I said, I am a newbie to Docker. I use Portainer to manage my container. What exactly (step by step) should be my command line? I tried your script, it does not work. 

Thank you.

[mvallevand]

It seems too many people are trying to get Docker running without doing research. Unfortunately I've personally never used portainer so can't help you there.

Martin

[stash201518]

It seems too many people are trying to get Docker running without doing research.  Unfortunately I've personally never used portainer so can't help you there.

Martin

Ok, thank you. Except Apple Tv, everything is running smoothly. I can deal with this hiccup, no problem.

Thank you

[mvallevand]

You need to expose the udp discovery port 16891

Martin

[DjurreP]

I had the same problem with the AppleTV NextPVR client not being able to find my NextPVR server running in Docker on my LAN.
After adding the following to my docker-compose file, the problem is resolved.

    environment:

      - HOST_IP=182.168.178.40

[pato345]

I just had the same problem today, so I am posting what happened to me and how I fixed it.

I was using NextPVR on Windows10 for several years.
I just installed NextPVR in Docker on a Synology DS220+ (64 bit OS). 
Everything works fine from my laptop I can watch/record etc through the browser pointed at the same IP as my NAS:8866

But when I tried AppleTV it found an address of 172.17.0.2. Thats not my network so I deleted it and manually added my NAS ip and Pin. It just tried to connect with the Apple TV eventually going to sleep. I added the Host_IP variable and it still didnt connect.

The problem was that I had hastily created the container with a Bridge network instead of Host.  The only way to fix this on Synology that I could find was to just shut down the container and create a new one. Selecting Host for the Network and also adding the HOST_IP variable.

All of the setup I had done earlier in the day was still there, channel lineups imported recordings etc. SO the fix just takes a minute.

Hopefully this helps the next person.

[mvallevand]

It exposed 172.17.0.2 because the HOST_IP wasn't set for discovery. You do need to restart after adding it.

Martin