Nginx-proxy-manager: Satisfy All Not Populating in .conf files

[McCloudS]

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? Yes

Describe the bug

• A clear and concise description of what the bug is. Literally every proxy_host that I use an access list for fails with:

[4/21/2020] [4:44:13 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[4/21/2020] [4:44:13 PM] [Express  ] › ⚠  warning   Command failed: /usr/sbin/nginx -t -g "error_log off;"
nginx: [emerg] unexpected ";" in /data/nginx/proxy_host/6.conf:43
nginx: configuration file /etc/nginx/nginx.conf test failed

My access list contains a single user, satisfy any checked (speaking of which, in the code satisfy_all is misspelled as satify_all), and a single 'allow' of '192.168.1.0/24'

The .conf files ends up looking like below after applying the access list

# Authorization
    auth_basic            "Authorization required";
    auth_basic_user_file  /data/access/1;

    # Access Rules
    deny all;

    #Access checks must...
    ;

Adding satisfy any manually fixes it temporarily.

• What version of Nginx Proxy Manager is reported on the login page? 2.2.3

To Reproduce
Steps to reproduce the behavior:

1. Created an access list as shown above
2. Apply it to a proxy_host
3. Attempt to generate SSL for the host and save
4. "Internal Error" popup and above issue.

Operating System

• Docker

[Indemnity83]

I'm pretty sure the job that updates Nginx configs after a certificate is added doesn't have the access list relationship loaded and is the cause of this bug, I haven't had a chance to determine where I can load the relationship to fix the bug though.

[McCloudS]

This is still an issue on the newest build. However, it can be bypassed by creating a proxy host without the access list enabled, generating the cert, then going back and enabling the access list after the cert is auto-generated. Seems like doing most actions with an access list attached to domain fail and need to be done totally separately.

[maxi1134]

Hi there.

I am still getting "[emerg] unexpected ";" in /data/nginx/proxy_host/3.conf:44" when trying to generate an SSL certificate on version 2.5.0

Is there any fix to this?