Comic Book/ eBook Docker Recommendations

  • I completely understand that.

    But, am I wrong or right in saying then that when I connect to SWAG, I would do https://{domain}:4656 or would I do https://{domain}

    If I am to NOT do :4656 at the end, then how does my WAN know were to direct traffic coming in on https://{domain} if I have multiple https servers running.

    What I mean is if WAN stays Port 80/443 how does it know which web server to forward to. ugh sorry i am so slow. I don't expect you to teach me it all. I will just do every combo til it works.

  • when I connect to SWAG, I would do https://{domain}:4656 or would I do https://{domain}

    You have to use the latest since SWAG can't run with other ports than 443 & 80 on wan.


    Please, read the GitHub to better understand what is SWAG:

    https://github.com/linuxserver…idation-and-initial-setup

  • Hello


    So, for testing purposes I wanted to bypass the WAN Static IP for my Cisco FTD and am using a "spare" static ip I have.

    When I set up SWAG and it "installs" without error I get this error on the log;


  • You have to use the latest since SWAG can't run with other ports than 443 & 80 on wan.


    Please, read the GitHub to better understand what is SWAG:

    https://github.com/linuxserver…idation-and-initial-setup

    As Soma said, SWAG requires port 80 and 443 to be accessible from the internet not 8080 and 4443. Those standard 80 & 443 ports are the ports required by lets encrypt to negotiate the certificate generation.


    As is also mentioned in the SWAG documentation, you can't have anything else using those ports (including the OMV GUI)


    I am personally not running SWAG at the moment (currently nginx-proxy-manager), but will probably be switching to it on one of the servers I look after, so I can't attest to doing docker port remaps in it, (ie. using 8080:80 in the container to avoid having to move the OMV GUI to a different port) but having 80 & 443 internet accessible is a must with lets encrypt. If you can do the docker port remap, you would have to do the reverse map on your router, so that traffic goes internet 80 -> 8080, then the docker container goes 8080 -> 80 (same idea with 443)

  • The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

    Your port 80 isn't reacheable.

    am I needing to open any other ports than 8080 or 4443

    Again (and this will be my last post in this thread), you need to make a portforward rule from WAN port 80 to the LAN IP where SWAG is running and the port you choose on the YML.

    The same for WAN port 443.


    If your SWAG instance is running on IP 192.168.5.42:

    Make a portforward on your router from WAN port 80 to IP 192.168.5.42 port 8080

    Make a portforward on your router from WAN port 443 to IP 192.168.5.42 port 4443


    Make sure that your SWAG YML ports are:

    8080:80

    4443:443


    Good luck

  • Got everything working. I will confess, because NGINX was already the one I had installed and no indifference to SWAG, I got that working. I can connect from Internet to (through) NGINX to my Kavita and read remotely. All is done awesome. I thank you all for the help and the constant help on my ignorance.

    I will be posting a follow-up question as a new thread as it would not really fit under this thread.

  • fbeye

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!