2.1.17 => 2.2.1 (After update, no longer possible via nginx-ui web to send requests to /api/config)

[dennisoderwald]

Describe the bug
Since updating to the latest version, I can no longer edit, enable, or disable any pages. The request is constantly pending, and nothing is visible in the debug log. A timeout does not seem to be taking effect.

When I duplicate a new page from an existing one, it works until I try to enable it.

Under “Dashboard” -> “Sites,” it says “No sites found”—but there are 39 sites. Interestingly, under the other node there, a page of 39 is displayed.

Log Output:

:29 ingress-fsn nginx-ui[2795091]: 2025-12-03 16:43:29.524        DEBUG        github.com/0xJacky/Nginx-UI/internal/sitecheck/service.go:208        Started sitecheck refresh goroutine
Dez 03 16:43:29 ingress-fsn nginx-ui[2795091]: 2025-12-03 16:43:29.524        DEBUG        github.com/0xJacky/Nginx-UI/internal/sitecheck/checker.go:97        Found 40 indexed sites
Dez 03 16:43:29 ingress-fsn nginx-ui[2795091]: 2025-12-03 16:43:29.524        DEBUG        github.com/0xJacky/Nginx-UI/internal/sitecheck/checker.go:138        Collected 0 enabled sites for checking
Dez 03 16:43:29 ingress-fsn nginx-ui[2795091]: 2025-12-03 16:43:29.524        DEBUG        github.com/0xJacky/Nginx-UI/internal/sitecheck/service.go:211        Sitecheck refresh goroutine completed

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Manage sites'
2. Click on 'Enable'
3. Wait...

Screenshots
If applicable, add screenshots to help explain your problem.

Info (please complete the following information):

• Server OS: NixOS
• Server Arch: amd64
• Nginx UI Version: 2.2.1
• Your Browser: Chrome

Additional context
I use Nginx-UI with the cluster function and also synchronize another node that is on the same version.

[dennisoderwald]

I have the feeling that, for whatever reason, the nodes are no longer 100% in sync, regardless of the error. Is there a way to synchronize them completely?

[dennisoderwald]

The “Manage Configs” section also loads indefinitely... but only if a previous request was still pending...

[0xJacky]

I will try to solve it in the development version tomorrow. Could you please take a screenshot of the F12 network request interface when it shows infinite loading? Also, when synchronizing nodes, use the command "journalctl -f nginx-ui" in the terminal to check the logs.

[dennisoderwald]

@0xJacky I just tested it, and although the number in the dashboard is still incorrect in the “dev” branch, saving is working again.

So something between version 2.2.1 and dev definitely solved the main problem with saving for me.

[dennisoderwald]

In the other node, I always get the following error:

Dez 03 17:05:00 ingress-nbg nginx-ui[2065837]: [0.148ms] [rows:0] SELECT * FROM `nodes` WHERE `nodes`.`id` = 3 AND `nodes`.`deleted_at` IS NULL ORDER BY `nodes`.`id` LIMIT 1
Dez 03 17:03:23 ingress-nbg nginx-ui[2065837]: 2025-12-03 17:03:23.582        ERROR        github.com/0xJacky/Nginx-UI/internal/middleware/proxy.go:35        record not found

Node ID 3 is its own

[0xJacky]

Thank you for the information you provided. I'll take a look at this issue.

[0xJacky]

In the other node, I always get the following error:

Dez 03 17:05:00 ingress-nbg nginx-ui[2065837]: [0.148ms] [rows:0] SELECT * FROM `nodes` WHERE `nodes`.`id` = 3 AND `nodes`.`deleted_at` IS NULL ORDER BY `nodes`.`id` LIMIT 1
Dez 03 17:03:23 ingress-nbg nginx-ui[2065837]: 2025-12-03 17:03:23.582        ERROR        github.com/0xJacky/Nginx-UI/internal/middleware/proxy.go:35        record not found

Node ID 3 is its own

I'm not quite sure if this issue has been fixed in the previous version. Will it still occur after all the nodes have been upgraded to the dev version?

[0xJacky]

Are you sure that when accessing from the main node, the Dashboard of the site shows 0 records?

[dennisoderwald]

@0xJacky Sorry for the late reply. Yes, I'm 100% sure.