aptalca

You need to tell curl to follow redirects

That doesn't seem like the correct config for that. In that configuration, http auth is not dependent on the source ip, only general access is. Http auth is requested for every successful connection

502 means letsencrypt can't reach the service at the specified address and port

Your issues are with "outgoing" connections, not incoming. That's why I suggested dns

Did you confirm it's not dns or networking issues?

Yup, and the line after that, which closes the the bracket

So you can connect to your server without having to keep track of ip changes. Just connect to the domain

You have networking or dns issues. The container cannot reach out to letsencrypt servers. Check your dns, turn off pihole or whatever else blocker you may be using.

The readme covers that

No idea what port it uses to connect but you would need to map that port so it can connect to boinc

I guarantee cloudflare is a better option than your current dns provider. Do yourself a favor, get a free account, point your nameservers there and do dns validation with wildcard

Edit the default site conf and comment out the block with listen 80 Also, if you use dns validation, you don't have to forward port 80

The readme tells you not to set/change the interface in bridge

Because it's not a desktop os, it's a docker container

Set version var to docker so it doesn't update during start

https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/

Click on open folder, delete everything in the bar and put a forward slash `/` in there, it will let you browser the entire container contents including other mapped folders

Not restarted but when recreated/updated

There are a multitude of options to update ip on dns. Many routers provide that feature. We also have a ddclient image that does just that

A records point to IP addresses

You have to wait until you're assigned a job

Did you look at the link above your post?

The heimdall subfolder method is only for setting the homepage of the main domain. You don't need to do that for the homepage of a secondary domain because it is not already set up. For ombi as the homepage of the second domain, just use the ombi subdomain conf, and edit the server name to read "seconddomain.com"

Server name directive. Create a new subdomain conf for the new server name

For the last two posters: 502 means letsencrypt can't reach the other service at the address and port defined. Fyi, 443 is not the correct port for ombi. Also ombi does not use https, it's http