Access List + Restart = invalid Cert on all endpoints with access list applied

[JohnGalt1717]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? yes
• Are you sure you're not using someone else's docker image? yes
• If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? na

Describe the bug Per Title

To Reproduce Create an access list that has an internal subnet white listed (i.e. 10.0.0.0/8). Apply it to endpoints and save with let's encrypt certificate. Save. Verify that it works without issue Restart nginx proxy manager docker container Close browser, open it again and go to same url

-- Results in invalid certificate and inspection shows that it's the dummy certificate.

Go into the endpoint Save the endpoint without changes Refresh browser Works fine again.

Note that all endpoints that do not have an access list assigned work fine.

Expected behavior Should survive restarts properly and apply the certs correctly without having to save the endpoints individually every time.

Operating System Ubuntu 20.10

[Kareltje1980]

I can confirm this. As so far that the issue I am seeing is very similar.

(I am on the latest docker version 2.7.3)

Change an access list, by adding/removing an IP range on the access tab. Then all the proxies using that end point have invalid certificates. It appears this is because the region # Let's Encrypt in the data/nginx/proxy_host/00.conf is missing. Opening and saving the proxy restores the missing data.

[apainter2]

Also confirmed that this bug still exists. I am using NPM version 2.8.1 from the jc21 docker image.

@Kareltje1980 solution was a fix for it, but I had to open 20+ proxies to fix it. But its not ideal.

[tgrimminger]

I can confirm that this bug still exists in NPM version 2.9.6 hosted via docker. @Kareltje1980 solution still works but is not ideal obviously.

[SteveGBuck]

Confirmed, I've got this issue too with ubuntu 20.04.2 LTS server as the docker host.

Upgraded to 2.9.7 and still experiencing the issue.

[AlfaJackal]

Upgraded to 2.9.9, issue still exists.

[kffl]

Still experiencing this issue in version 2.9.12. After editing an access list, all of the proxy hosts with that access list selected start using a self-signed certificate instead of the Let's Encrypt one. The workaround described by @Kareltje1980 appears to be working.

[exgame]

It still persist to this date. Latest docker image.

[gmaurice]

Hello, I faced to the same issue too with the version v2.9.14.

[OnkelKeule]

Same in v2.9.15

[sethiele]

And Still in v2.9.18

[kroese]

Also experienced this issue in v2.9.18

I don't understand why this is still not fixed after a year?

[TopBanana123]

Well I'm glad its not just me, v2.9.18, same problem!

[jonathanhoskin]

Same here in v2.9.18. Thought I was loosing my mind!

[NeitherSound]

At least it is not me alone having this issue. Is a fix ever coming out for this? I am on the latest version of Nginx, no issues other than this one known bug

[ukewea]

Same here in v2.9.19, any help would be appreciated, thanks.

[joaquinvacas]

Hey! Any news on this?

[Realmagnum]

nope. still have problem, I think It is time to learn something else traefik for example.

[iveney]

wow this just happened to me. Debugged for quite a while. I have to manually go through each proxy_host and edit save to let the cert populate in the actual proxy host conf.

[AustinLeath]

Can confirm, this is still happening in 2.9.19. Affected all 18 hosts. had to remove each host from the access list and add them all back in.

[github-actions[bot]]

Issue is now considered stale. If you want to keep it open, please comment :+1: