aptalca

https://lmgtfy.com/?q=How+to+use+docker+tags

Those logs are from March and they are several days apart. I'm guessing you shut down the container at night, which is when it's supposed to renew the certs

You can pull an earlier tag from docker hub but badge sure the version variable is set to docker so it doesn't update on start

Don't change the port in the proxy confs

Yup, edit the heimdall subdomain conf and change the server name directive to www.* or server.*

It's all working from here. Check your sonarr if you don't believe me 😁 you really should password protect those services

You keep insinuating that a lot of people are having renewal issues, therefore there must be something wrong with the image. However, 1) Users aren't even checking whether their certs are really expiring, which can be easily done in a browser by clicking on the lock icon, but instead rely on an e-mail that is non-specific and may not even be about the cert that is currently used (you included) 2) Nobody's checking their logs to see what the issues may be that cause a non-renewal (also you included) The logs are rotated weekly and 52 log files are kept. That means you have up to a year's worth of renewal attempt logs. Feel free to go back and find the ones that failed and if you really do identify a bug with the image, we'll fix it.

Read the last few posts

If it works from outside the lan, your issue is hairpin nat. Google how to enable it for your new router

Are you sure your certs were expired? What made you think they were? And what error are you referring to? You might be confusing two separate issues

Check the log folder, under letsencrypt and it will tell you exactly why the renewal failed. Then you can figure out what you may or may not have done

It's usually because the user makes changes to either port 80 mapping or their dns settings so validation fails

Check line 4 of the default site config

Open your domain in a better and click on the lock to see if it really expired If so, check the log in the config folder under letsencrypt to see why the renewal failed

Then check your port forwarding and post your docker log here

Your db was likely already corrupted before the switch. Google how to restore Plex db

Move the config folder to /mnt/cache or /mnt/diskX if it's not there already

How about port 80 tcp? A lot of public wifi also block vpns (mainly block all udp connections as well as tcp except for 80 and 443) so I use port 80 for mine

Switch to bridge networking and some other changes. See the GitHub or docker hub pages for specific info (links on the first page)

Just the naked domain will suffice, without /admin at the end This is all in official openvpn-as documentation by the way

There is a separate thread for discussing the script as it's not published by the lsio team. In your screenshot, you see hw next to the encode portion (h264 after the arrow), but no hw next to decode (h264 before the arrow)

What about https://domain.com ? From outside your wan like on a phone with cell connection

Define not working

You have some incorrect port forwards. For starters, your outside port 443 has two rules trying to forward it to different ports. And some have the outside and inside ports switched. It should go from 80 to 81 not the other way around

Your encode is hw, but the decode is sw