Https access via own domain over reverse proxy fails

Configuration
,
1

Hello all,
because I want to have my nextcloud as well as homeassistant accessible over internet with let’s encrypt certificate, I have installed the nginx proxy manager.

Acess via my dyndns (that is updated by my FritzBox router) works with http and also https. :grinning:

In the next step I want to access via my own domain.
So my own domain forwards to the dyndns which then lands at the reverse proxy and is forwared to home assistant:
ha.mydoamin.de → mydyndns → reverse proxy → home assistant

Without touching nginx, when I open my domain URL, it does go via dyndns to home assistant, but only with http (even though the domain forward is explicitley to https://).
When I add another proxy host in nginx proxy manager with my own domain and try to create a certificate for that, it fails with an internal error, and the log says

http-01 challenge for ha.mydomain.de
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.
Waiting for verification...
Challenge failed for domain ha.mydomain.de
http-01 challenge for ha.mydomain.de
Cleaning up challenges
Some challenges have failed.

Is that because mydomain.de also already has a let’s encrypt certificate by itself? Becuase this is the case, I would have expected that it directly works. mydomain has a certificate, and the dyndns has one issued by the proxy manager. So what do I have to do to get this working?

2

Port forward port 80 to HA

3

80 and 443 are forwarded, and I could also successfully create certificates for my dyndns URLs. Only for my own domain it is failing.

4

When you run the letsencrypt client with http verification, the port 80 must be forwarded (at least temporarily) to the machine where you run the client (and you must be sure nothing else listen on 80 on that machine).

5

That I know. Port 80 and 443 are permanently forwarded to the RPi that hosts the proxy manager.
As I said, that is why generelly certificate issuance out of the proxy manager for dyndns URLs has worked, but for another domain it doesn’t, and the error messages do not tell me what is different in this case.

6

Only support one domain I think