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
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug
Adding IP addresses in access lists causes a dummy certificate from localhost to be delivered. The vHosts that use this access lists have no SSL configuration - they listen only on port 80.

Nginx Proxy Manager Version
v2.9.13

To Reproduce
Steps to reproduce the behavior:

1. Add a "Private" Access List with an Allow address, e.g. 192.168.0.0/16.
2. Use this access list in different vHosts (Force SSL and HTTP/2 enabled).
3. Visit your site via SSL - everything should work.
4. Now add another IP address to the access list.
5. Then visit a vHost that uses this access list. Now a localhost certificate should be served, because the SSL configuration in the vHost is missing.

Workaround: Take a vHost and save it again - the SSL configuration should be regenerated.

Expected behavior
The new IP address is added to the access list and my pages are still accessible via SSL.

Further information

app_1  | 2021-12-30T14:01:18.688684912Z [12/30/2021] [2:01:18 PM] [Nginx    ] › ℹ  info      Reloading Nginx
app_1  | 2021-12-30T14:01:19.564689136Z [12/30/2021] [2:01:19 PM] [Access   ] › ℹ  info      Building Access file #2 for: Private

Broken vHost: https://pastebin.com/HVj1sPKw
Functional vHost: https://pastebin.com/tPNYEA2i

Operating System
Banana Pi M1 with Armbian and latest Docker