aptalca

https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

Then the problem is your port forwarding

Yeah, if you nuke the appdata, the license won't be valid anymore. What we need tested is, recreating the container with the same appdata. Openvpn-as won't tell us what parameters they use to check. I'm not sure if mac address is one of them. But you can indeed set a custom one for your docker container: https://stackoverflow.com/questions/42946453/how-does-the-docker-assign-mac-addresses-to-containers

Can you confirm that the license remains valid through container recreation? We had a couple people ask in the past but they never confirmed. No one on the team has a paid license so we can't test. Thanks

No, this is a server. What you need is a client

If you can access via cell phone, then there is nothing wrong with letsencrypt or ports. Issue is your router. Google hairpin nat or nat loopback

In container settings, additional arguments, enter "--hostname blah"

You'll have to create a new server block for the subdomain. See the default proxy conf for examples. Server name is defined in there. And then, inside that new server block, you'll create a location block for whatever subfolder you want.

Once you connect to the vpn, just browse to your server ip address and put in the port for the relevant gui. If you want to do it with reverse proxy (properly), then you can use our letsencrypt image. Here's a guide for that: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/

edit the container settings, STAGING should be there, if not, add it and set it to true

Use allow/deny statements to block outside access and only allow internal access Location does not refer to the domain. Server name directive is for the domain name

Yeah, don't run manual commands in the container unless we tell you to. Things are sure to break

If anybody's affected, set the staging var to true, hit save. Then edit again and set it back to false. That action will force a renewal of the cert.

LT dropped by once and asked for a summary, then crickets. Try emailing them and linking to this thread

Post a full log. Those are harmless errors

When I try to connect to your domain, I get a blank yellow/green page with "webcam" as the page title. Are you sure you did the test correctly as described?

Either your IP is incorrect, or you have port forwarding issues. Also, you really don't need to create multiple domains on duckdns. Create one, use that as the url here, and everything else will be a sub-subdomain. For example, you register mycustom as your duckdns subdomain, so you'll put "mycustom.duckdns.org" into url, and put "nextcloud,sonarr,sabnzbd" into subdomains and your services will be accessible at "nextcloud.mycustom.duckdns.org". See here to troubleshoot the port/IP issue: https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

You said you followed the linuxserver troubleshooting guide. So what happened? Did you do the test?

Roxedus already answered you there. It's a macvlan issue. You have some containers on macvlan, and they can't access the host or any service running on the host. That's a docker security feature.

Edit the default site config, create 3 server blocks, one for each site, and set their server names and root directives accordingly. You can create folders "/config/www-domain1", "/config/www-domain2", etc. This is just basic nginx config. There are plenty of guides online.

Yes, see the extradomains variable

No longer needed but won't hurt

You'll have to contact spaceinvaderone on that one.

Maxmind already provides a script that you can run via cron on the host. Luajit alert is an upstream issue with the luajit nginx module on alpine. It's harmless, just an alert.

Letsencrypt generates one cert that covers all domains and subdomains you validated