Posts by muchgooder

    When you remove docker-ce you remove docker capability. If you want it back, reinstall docker from the OMV GUI.

    Thank you for your response. Just to be clear, it shows that Docker is installed but not running. I click install and everything appears to be good (it shows ports, etc). If I click restart it errors out:

    apt-get remove docker-ce 

    Well, good news and bad news. The good news is that I could pass through the port to the OMV GUI. The bad news is that it looks like running that command may have hosed my setup. It now says that Portainer is not installed and it errors out if I try to install it. Docker won't start - I get an error trying to initialize docker.service. Hopefully there is a way to undo this?

    There is one other change that I had made yesterday that didn't occur to me until a minute ago. I had removed a switch in my network that brought the OMV box one step closer to the router (there is now only one switch in between). I had meant to try this test yesterday but then ran out of time.

    I am still in doubt if this is related to docker at all, except it may be messing with your firewall rules.


    Yopu could try to remove docker (do not purge) and try if you can forward to the omv ui,


    I have no idea of what to do except that and take one part out of the puzzel.

    Sure, sounds good. How would I temporarily remove docker?

    docker creates it's own networks, but this should not be a problem, as long as you have the correct port assignement in you docker-compose files.

    Have you been able to test with the omv web ui?

    Thank you again. I did pass port 80 to .100 and it came back with a fail (I tested on my phone as well). I am mildly surprised by this because I was able to pass ports to a windows session running on virtualbox on .100 before upgrading to 5.


    Please. If you are not going to try exactly as I suggest, then just say so, I will spend my time elsewhere.


    Delete the Source Net and delete the From port.


    And please keep in mind that I am following suggestions that both of you are feeding me. I added "Source Net" at Zoki's urging as it was not originally set (and not working). Again, I am happy to try any suggestions. Also, as I noted in the post that you replied to the "From port" is required in DDWRT so I could not remove it.



    Plex works

    Unfortunately not - I had just switched it back to look at the windows pc because a family member wanted to watch something off of my server. Speaking of Plex, in the Plex remote access setup it (not surprisingly) detects that remote access is not set up correctly when I point the port to the Docker App.




    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.

    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

    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).

    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.

    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.