Can't forward ports to Docker Apps - Solved!

    Every since I started with OMV a couple of years ago I have not been able to forward ports to Docker apps in OMV. I had hoped that may have been caused by Google wifi causing a Double NAT situation but that is no longer running in my network. I've probably tried it with 5 or 6 apps - no luck. I can access them all from inside of my network without issue. Plex, murmer, several more. When I was running on release 4 of OMV I could put them inside of a virtual box windows pc running on OMV and they worked just fine. If I then change my ddwrt port forwarding to look at the Docker version of the app it fails. I do not have a firewall set up in OMV nor do I do anything that I would think would be out of the ordinary.


    I'll post the config for my murmer app. I am not sure where to start with this one - any help would be greatly appreciated.




    What happens if you open this inside your browser http://<insert_ip_of_omv> :64738?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Zitat von Zoki

    What happens if you open this inside your browser http://<insert_ip_of_omv> :64738?

    right, sorry - that's what I meant when I said I can access everything normally inside of my network. I probably have 10 docker apps running right now and I can manage them fine internally by opening via url. I also have other apps on my network accessing sql docker app on omv - no problems. I've hosted a variety of web and ftp servers over the years on other platforms so port forwarding is nothing new to me.

    So please change the thread itle, as it is not related to portainer / docker.

    How do you want to access the containers fom the outside? Do you have a reverse proxy running od do you forward individual ports?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Zitat von Zoki

    So please change the thread itle, as it is not related to portainer / docker.

    How do you want to access the containers fom the outside? Do you have a reverse proxy running od do you forward individual ports?

    The issue only happens for Docker apps - why would I change the title? Maybe the issue is in docker or the container setup, maybe it isn't.

    I don't have a reverse proxy set up so I am only looking to forward individual ports.



    So here is part of my port forwarding in ddwrt. I currently have ports forwarded to windows pcs on the network and they work fine. As I said in the original post, I also had these programs running in virtualbox inside of OMV and that worked fine. If I change the IP address to OMV (192.168.1.100) they fail.

    Change the port forwards so they point to the right IP of you omv.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    You network doesn't know anything about docker or portainer. if the port is open on the OMV host this part works as expected.

    Do you have firewall rules set up?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    So 192.168.1.100 is the ip of you omv, not the .200 you are forwarding http to?


    Try a short check, if ou can reach the OMV UI by your port forward.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Zitat von Zoki

    So 192.168.1.100 is the ip of you omv, not the .200 you are forwarding http to?


    Try a short check, if ou can reach the OMV UI by your port forward.

    No luck. I forwarded port 80 to 192.168.1.100 and then tried to pull it up on my phone with wifi disabled and it did not come up. I had port 80 pointing to a different web server (not on OMV) and it works fine. I also tried again with mumble on port 64738 - it doesn't work when pointed to 192.168.1.100 (omv / docker). It works fine when I change it back to my windows pc (.206).

    Are you running fail2ban?

    Let me see iptables -L and ip a on the omv server.


    Try to ping the omv from your router and look into the firewall logs of the router

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Zitat von Zoki

    Are you running fail2ban?

    Let me see iptables -L and ip a on the omv server.


    Try to ping the omv from your router and look into the firewall logs of the router

    Sure thing, thank you again!


    I've never heard of fail2ban so safe to say I am not running it :-).





    Code
    PING 192.168.1.100 (192.168.1.100): 56 data bytes
64 bytes from 192.168.1.100: seq=0 ttl=64 time=0.445 ms
64 bytes from 192.168.1.100: seq=1 ttl=64 time=0.278 ms
64 bytes from 192.168.1.100: seq=2 ttl=64 time=0.300 ms

--- 192.168.1.100 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.278/0.341/0.445 ms

    From the router

    Does ddwrt have the option to telnet / wget a port in the local network?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    To my understanding, it is something in the config of ddwrt.


    One last thing: if you have a system outside you lan, try curl -vv http://my_external_ip:64738 to see if something weird happenes on the http protocol level. If you dont hav, pn me the ip and I'l try

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Zitat von Zoki

    To my understanding, it is something in the config of ddwrt.


    One last thing: if you have a system outside you lan, try curl -vv http://my_external_ip:64738 to see if something weird happenes on the http protocol level. If you dont hav, pn me the ip and I'l try

    I think you are probably right about that, although it is still odd that the issue only happens on OMV docker apps. IP address sent.

    A very common mistake when setting up port forwards in a router is to specify a source port.


    In your case it is in your screenshot as Port from


    Remove those.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    From port is external port in DDWrt speak, not port range.


    Try 0.0.0.0/0 fo source net. Maybe it helps, but this is doing voodoo now.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden