[GH-ISSUE #77] Problem with conditionals #4474

New issue

Closed

opened 2026-03-01 15:33:31 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 15:33:31 +03:00

Owner

Originally created by @kcholoren on GitHub (Feb 9, 2023).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/77

Hi, I found a problem that I think is new, because this configuration was already working, but yesterday I edited a Site and a problem appeared.
My configuration has several ifs inside the location part.
For example:

location /XXXX/ {
        proxy_pass YYYY
       ....
        if ($allowed_country = no) {        return 444; }
    }

But when I re-edit the site, in the editor it becomes:

location /XXXX/ {
        proxy_pass YYYY
       ....
        if ($allowed_country = no);
        return 444;
    }

And I get an error when I try to save:

Nginx Configuration Parse Error
nginx: [emerg] directive "if" has no opening "{" in /etc/nginx/sites-enabled/tkl-default:83 nginx: configuration file /etc/nginx/nginx.conf test failed

Any ideas why?
Thank you!

Originally created by @kcholoren on GitHub (Feb 9, 2023). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/77 Hi, I found a problem that I think is new, because this configuration was already working, but yesterday I edited a Site and a problem appeared. My configuration has several **ifs** inside the _location_ part. For example: ``` location /XXXX/ { proxy_pass YYYY .... if ($allowed_country = no) { return 444; } } ``` But when I re-edit the site, in the editor it becomes: ``` location /XXXX/ { proxy_pass YYYY .... if ($allowed_country = no); return 444; } ``` And I get an error when I try to save: ``` Nginx Configuration Parse Error nginx: [emerg] directive "if" has no opening "{" in /etc/nginx/sites-enabled/tkl-default:83 nginx: configuration file /etc/nginx/nginx.conf test failed ``` Any ideas why? Thank you!

kerem

2026-03-01 15:33:31 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-01 15:33:32 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 9, 2023):

Thank you for your report. This problem should be fix in 6b9ebbf, and the fix will be released in next version.

@0xJacky commented on GitHub (Feb 9, 2023): Thank you for your report. This problem should be fix in 6b9ebbf, and the fix will be released in next version.

kerem commented

2026-03-01 15:33:32 +03:00

Author

Owner

@kcholoren commented on GitHub (Feb 9, 2023):

Thank you!

@kcholoren commented on GitHub (Feb 9, 2023): Thank you!