aptalca

Post your docker run

The readme explains it in detail. It has nothing to do with subdomains. You need to define full urls (fqdn) in that variable

There is an extra domains variable. No need for another instance

That's harmless

When the ppa is updated

.htaccess is an apache thing. What you need to look into is .htpasswd

That's really a question for code-server

Iirc there were some minor changes to where things are stored under config. So I recommend setting up the new one fresh, and then you can copy over your books and database to the correct locations

Easiest way to test is, turn http auth on for some service, enter the password wrong a few times. Boom, banned.

Sounds like your isp put your router behind a nat, so your router is not getting the public ip (10.x.x.x are typically private addresses). The public ip address seems to be the one starting with 96. What kind of fiber box are you using? Is it a router? My isp has a fiber ont on the outside of my house, which is the equivalent of a modem. They also tried to sell me their router which they claim is required for tv capability. If you have that and connected your own router to it, then you're double natted. I refused their router and instead hooked up my own router (pfsense) directly to the ont unit via Ethernet so my router gets the public ip directly (I don't care for tv service).

IP checks including duckdns' auto check rely on pinging a remote server and asking the remote server to respond back with the address they see the request coming from. Somehow your internet connection is going out through that IP you're seeing but don't recognize. Does your internet connection go out through a vpn? If so, that's your vpn provider's IP

Post your setup details and post what you tried and we'll take a look. If you redact sensitive info, keep the structure, don't redact the whole thing ie. https://redacted.com/blah:444

If you're doing a chown -R on unraid console and the files are still owned by root, you have deeper issues with unraid. That's not related to docker at all.

Read our documentation. It's explained very clearly there.

Likely an issue with how you mounted the drive. You should ask in the unassigned disks thread as it's not related to sab or docker

It's just another bridge network like the default bridge all containers run on by default. The difference is, user defined bridge allows containers to connect to each other via container names as dns hostnames. See here: https://blog.linuxserver.io/2017/10/17/using-docker-networks-for-better-inter-container-communication/

Not related, just an alert

That's why the readme states "comma separated, no spaces" 😉

Don't change the port in the proxy confs. They refer to internal container ports. If you're reverse proxying that way, you don't even need to map a port for the container, you can remove them. Or set then to whatever, it doesn't matter.

Glad to hear you figured it out, but it sounds like you didn't follow the troubleshooting guide properly as that test would tell you the IP was not correct for that subdomain

Use the guide linked in the post above yours

Nginx logs in letsencrypt will show you all the connections. They're in the config folder. Also, if you reverse proxied with all the correct headers, letsencrypt will pass the original ip in there. You may have to tell apache to trust those headers. For nginx, you do it via "real ip" module and settings. Not sure what apache needs

You need to provide more context. Are you reverse proxying the server? And by server do you mean unraid?

Restart the container and it should fix the permissions

The user is abc and its pid is set to 99 (unless you changed it). It should have access to those folders on host