[GH-ISSUE #132] Cant enable/save files due to a warning derived from using nginx-ultimate-bad-bot-blocker #68

New issue

Closed

opened 2026-02-26 12:07:10 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 12:07:10 +03:00

Owner

Originally created by @FlurryNight on GitHub (Jun 2, 2023).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/132

Describe the bug
First, thank you for this project, This is the best UI I've found for NGINX since i remember, I've been using it several times flawlessly.

However i started using nginx-ultimate-bad-bot-blocker and since its has several rules and checks, nginx -t thinks the configuration is incorrect giving the following output in the screenshot

But it's not https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/issues/516,

To Reproduce
Add nginx-ultimate-bad-bot-blocker to a NGINX server and try to enable/disable sites in Nginx UI

Expected behavior
This behavior is expected as it its a good measure to check before applying changes, however if its was possible to override it in the UI, like a toggle: Allow to continue if warn?: on/off, or other better way

Screenshots

Info (please complete the following information):

Server OS: Ubuntu 22.04
Server Arch: amd64
Nginx UI Version: v1.9.9
Your Browser: Firefox

Additional
Also, but not related, it was nice that the custom templates could be loaded from a folder like /etc/nginx/templates, instead of the bundled ones, It would be easier to manage them instead of needing to compile it whenever i need to change the template or update nginx-ui, also it helps not "bloat" the server or other machine with build tools.

I would appreciate, Thanks again.
Waiting for feedback on how to solve this

Originally created by @FlurryNight on GitHub (Jun 2, 2023). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/132 **Describe the bug** First, thank you for this project, This is the best UI I've found for NGINX since i remember, I've been using it several times flawlessly. However i started using [nginx-ultimate-bad-bot-blocker](https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker) and since its has several rules and checks, `nginx -t` thinks the configuration is incorrect giving the following output in the screenshot But it's not https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/issues/516, **To Reproduce** Add nginx-ultimate-bad-bot-blocker to a NGINX server and try to enable/disable sites in Nginx UI **Expected behavior** This behavior is expected as it its a good measure to check before applying changes, however if its was possible to override it in the UI, like a toggle: Allow to continue if warn?: on/off, or other better way **Screenshots** ![image](https://github.com/0xJacky/nginx-ui/assets/47457170/e27c31c0-30c9-490f-9365-221f2faa4a34) **Info (please complete the following information):** - Server OS: Ubuntu 22.04 - Server Arch: amd64 - Nginx UI Version: v1.9.9 - Your Browser: Firefox **Additional** Also, but not related, it was nice that the custom templates could be loaded from a folder like /etc/nginx/templates, instead of the bundled ones, It would be easier to manage them instead of needing to compile it whenever i need to change the template or update nginx-ui, also it helps not "bloat" the server or other machine with build tools. I would appreciate, Thanks again. Waiting for feedback on how to solve this

kerem

2026-02-26 12:07:10 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:07:10 +03:00

Author

Owner

@0xJacky commented on GitHub (Jun 3, 2023):

Hello, this issue has been resolved in v2.0.0, and you can upgrade the nginx-ui via the upgrader in web ui.

@0xJacky commented on GitHub (Jun 3, 2023): Hello, this issue has been resolved in v2.0.0, and you can upgrade the nginx-ui via the upgrader in web ui.

kerem commented

2026-02-26 12:07:11 +03:00

Author

Owner

@FlurryNight commented on GitHub (Jun 3, 2023):

Hello, this issue has been resolved in v2.0.0, and you can upgrade the nginx-ui via the upgrader in web ui.

Oh okay, thank you !

@FlurryNight commented on GitHub (Jun 3, 2023): > Hello, this issue has been resolved in v2.0.0, and you can upgrade the nginx-ui via the upgrader in web ui. Oh okay, thank you !

kerem referenced this issue

2026-02-27 12:10:12 +03:00

[GH-ISSUE #68] Suggestion: Be able to change the root directory #1381

kerem referenced this issue

2026-02-28 11:54:43 +03:00

[GH-ISSUE #68] Suggestion: Be able to change the root directory #3142

kerem referenced this issue

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

[GH-ISSUE #68] Suggestion: Be able to change the root directory #4469

kerem referenced this issue

2026-03-01 17:07:10 +03:00

[GH-ISSUE #68] Suggestion: Be able to change the root directory #5815