Comic Book/ eBook Docker Recommendations

fbeye · 18. November 2022

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.

Soma · 18. November 2022

Zitat von fbeye

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

fbeye · 23. November 2022

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;

HTML

 -1 }">Created .donoteditthisfile.conf
 -1 }">Using Let's Encrypt as the cert provider
 -1 }">No subdomains defined
 -1 }">No e-mail address entered or address invalid
 -1 }">http validation is selected
 -1 }">Generating new certificate
 -1 }">Saving debug log to /var/log/letsencrypt/letsencrypt.log
 -1 }">Account registered.
 -1 }">Requesting a certificate for x.x.x.net (a domain i have registered to my ip)
 -1 }">Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
 -1 }">  Domain: x.x.x.x.net (a domain i do have registered to the ip i am using)
 -1 }">  Type:   unauthorized
 -1 }">  Detail: x.x.x.181: Invalid response from http://x.x.x.x.net:80/#/404: "<!DOCTYPE html><html lang=\"en\"><head>\n  <meta charset=\"utf-8\">\n  <title>openmediavault Workbench</title>\n  <base href=\"/\">\n\n  <m"
 -1 }">Hint: 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.
 -1 }">Some challenges have failed.
 -1 }">Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
 -1 }">ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container


Being my Cisco is no store bought and everthing is locked down until I open it, am I needing to open any other ports than 8080 or 4443 such as anything for DNS?

Alles anzeigen

BernH · 23. November 2022

Zitat von Soma

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)

Soma · 23. November 2022

Zitat von fbeye

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.

Zitat von fbeye

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

fbeye · 25. November 2022

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.

jamihanf · 18. Januar 2024

Thanks for the information!

fbeye · 18. Januar 2024

Zitat von fbeye

Hello

So I have a lot or comic books and ebooks on my server but want to access them remotely. I know the books are .pdf but brainfart I think comics are .cbr or cbz?.
I see several threads about things but not really getting a good answer. Is there a docker for both these formats in one or should separate dockers serve ebooks and comics separately?
Just curious about any of your successes.

I do not even remember making this! I was h4x0red!

Comic Book/ eBook Docker Recommendations

fbeye 28. November 2022

Jetzt mitmachen!