Introducton of Docker to Plex appliance seems to have broken connection to all pages including webdav
I have to admit that I'm lost on a lot of these apps and languages that appear to be endless rabbit holes to me but for my own enjoyment and education I'm trying to build a really nice media appliance.
Everything was working fine and then I took the step of installing super transfer 2, it installed docker which is what I believe was the cause of the pages not being found. The webserver is running because I get "Not Found
The requested URL /setup/ was not found on this server.
Apache/2.4.18 (Ubuntu) Server at 10.1.3.39 Port 80"
So I'm kind of stuck and there doesn't appear to be any support on the topic in the plexguide forums.
Everything was working fine and then I took the step of installing super transfer 2, it installed docker which is what I believe was the cause of the pages not being found. The webserver is running because I get "Not Found
The requested URL /setup/ was not found on this server.
Apache/2.4.18 (Ubuntu) Server at 10.1.3.39 Port 80"
So I'm kind of stuck and there doesn't appear to be any support on the topic in the plexguide forums.
ASKER
I'm looking in portainer (which I know nothing about) and I'm seeing it configured to some 172... address. Is this what you mean?can you explain how to append that please?
ASKER
what this is is Openflixr. I configure the startup page to include my media server ip of 10.1.3.39 and config the gateway but the DNS was greyed out (not allowing input) but the grey form field looked to be set to 127.0.0.1 and said managed by pi-hole on mouseover
Docker will run each container with its own ip address. and use NAT rules to connect them.
If your media server needs port 80, 443 then if will nat the host IP addresses to the docker instance, blocking access to those ports from the host.
The option i mentioned if for the docker system service, and need to mentioned in it's sysvinit startup script or systemd startup parameter file as one of the argument. I amnot familiar with portainer.
With the option present you can run a reverse proxy on the host on say port 80/443 and then check on hostname and forward it to the right system from there.
like: if host.example.org -> localhost:8080,
if docker.example.org -> 172.16.0.1:80
if docker2.example.org 172.16.0.2:80
haproxy, nginx or lighttpd are excelent lowoverhead reverse proxies
If your media server needs port 80, 443 then if will nat the host IP addresses to the docker instance, blocking access to those ports from the host.
The option i mentioned if for the docker system service, and need to mentioned in it's sysvinit startup script or systemd startup parameter file as one of the argument. I amnot familiar with portainer.
With the option present you can run a reverse proxy on the host on say port 80/443 and then check on hostname and forward it to the right system from there.
like: if host.example.org -> localhost:8080,
if docker.example.org -> 172.16.0.1:80
if docker2.example.org 172.16.0.2:80
haproxy, nginx or lighttpd are excelent lowoverhead reverse proxies
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Try to have the the docker daemon started with the option: --iptables=false
and reboot your system.