aptalca

Post your full log. It worked when I tested it

You're manually running commands inside the container and heavily customizing it, therefore we can no longer provide support.

It tells you right there in the log. Fix your dns entry for the sonarr subdomain

Comma separated, no spaces

502 means letsencrypt can't reach code-server. You likely forgot to put them in the same user defined bridge network

Check the nginx logs to see what ip is listed as the source when you connect over vpn. I suspect it will look like the openvpn container ip as everything is nat'ed through that

Can't say without seeing your settings

My bad, missed the link

We're not the admins of duckdns service. https://groups.google.com/forum/m/#!forum/duckdns

You have way too many modifications there. Either contact the author of the guide you used, or use our guide here: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/

Post what you changed/tried to make it work and we'll take a look

Oh yeah I did overlook on mobile 😄 I thought you were trying to send emails from within the container. That's exactly what you want for proxy. The nginx.conf I believe has a very basic sample in there which you can enable and modify: https://github.com/linuxserver/docker-letsencrypt/blob/master/root/defaults/nginx.conf#L85

I recommend unraid console for those operations. Simple "cp sourcefilename targetfilename" will do what you want. And use "nano filename" to edit files

Smh. You see the linuxserver version and the binhex version side by side in your screenshot and you still select the binhex version. Why? Not that there is anything wrong with that version, but I'm asking you to follow the simple steps outlined in the troubleshooting article. We put a lot of time into it and it gets frustrating when users still don't follow them even when we spell them out step by step. The whole point of the troubleshooting article is so you can make sure that your ports are properly mapped and forwarded and that the container is accessible from the internet. Only then, you should try to set up letsencrypt. Otherwise there are too many reasons why it can fail and as you experienced, if it fails a bunch of times, you're throttled. So read the directions carefully.

Did you set up nginx with the same port mappings as letsencrypt and can see the welcome page when you connect to your domain on http port 80 via cell phone with wifi disabled?

Yes

That's imap proxy, completely different. But in any case, nginx is already compiled with mail in our image

Follow those steps exactly

I believe there is sendmail in there

Perhaps you should read the readme linked in the first post

Post the proxy conf you used

My guess is that option tells the software process to quit (rather than pause). However, the supervisor is set to restart the process whenever it quits (like when it crashes). So the app itself stops, but is promptly restarted by the container.

You don't need to provide certs to anything else. You can reverse proxy. You'll also still be able to access unraid on port 80 with http via its ip. If you want remote access, reverse proxy it. You can use allow/deny statements to control access. There is a post here on one of the last couple of pages about that.

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