[Bug]: clients are displayed for a very long time on 0.6.6 after update

[PhaNtomBek]

🐛 Describe the Bug

After updating from 0.6.5 to 0.6.6, if you open any network, the clients are displayed for a very long time, you need to wait 5-30 seconds. If you open the "ZT Controller" menu, the data display takes just as long. When you reopen the same network (if you open the network immediately), all data is displayed well. But if you wait time, the whole problem repeats itself.

🔍 Steps to Reproduce

Wait time, the whole problem repeats itself

🔧 Deployment Type

• Docker
• Standalone

✨ Expected Behavior

No response

📋 ZTNET Logs

No response

🖼 Screenshots

No response

[sinamics]

I do not understand "IDs are displayed for a very long time". Could you explain further?

Out of curiosity, do you have many unlinked networks?

[PhaNtomBek]

I can show you via Discord if it's convenient for you.

[PhaNtomBek]

It would probably be correct to say that the list of clients that are connected to the network is not displayed. I dont have any unlinked networks.

[PhaNtomBek]

I need to wait about a minute for clients to appear on the list. I rolled back to version 0.6.5 - no such problem.

[Mhalkyo]

Hello, I allow myself to react to this problem I recently used version 0.6.6 and I do not encounter this problem. Could it be due to a performance problem on the machine side?

[PhaNtomBek]

Hello, I allow myself to react to this problem I recently used version 0.6.6 and I do not encounter this problem. Could it be due to a performance problem on the machine side?

Hello,
I use a lot of networks. If the network was created recently, then this problem does not arise. If the network was created a long time ago, then the problem appears. I cannot confirm this, this is my observation.
Also, this may be related if there are a lot of clients on the network (30+). The problem has been noticed on different computers.

[n9yty]

I had been building a local copy of ztnet. With 0.6.6 I tried to use the published image and I encountered this problem. I then built it myself again and the problem was not there. I don't know what was going on, but it wasn't the host system as I had rebooted it to be sure and the CPU was idling on it. I assumed it was me or related to using a local built copy.

[sinamics]

I've attempted to replicate the issue but have been unsuccessful so far.
It's unclear why version 0.6.5 works while 0.6.6 does not, given the minimal changes between versions.

v0.6.5...v0.6.6

I will continue testing.

[n9yty]

I downgraded here to the last "official" image and it seems to be when the page is loaded or refreshed. Once the page is up I can change between organizations and networks and they populate quickly. If I refresh the browser page I get the delays. It is not directly related to the number of hosts but it seems longer on the larger networks. And as mentioned, if I let it sit for a little bit, and then try to switch networks, the delay comes back even though I'm not refreshing the page. I switched back to my local build and the issue goes away. There may be a very small delay but it is nowhere near what I see if I pull the "official" docker image.

I am running behind that caddy proxy if that makes any difference.

[PhaNtomBek]

Hello, I am running behind nginx.

[PhaNtomBek]

At the moment, the problem began to appear on version 0.6.5. It’s not so critical, but you need to wait 5-20 seconds for clients to display.

[PhaNtomBek]

At the moment, the problem began to appear on version 0.6.5. It’s not so critical, but you need to wait 5-20 seconds for clients to display.

Good day.
We moved to another data center and changed addresses. A webhook was configured that tried to connect to an unavailable address. Because of this, the entire ZTNET did not work, everything was very slow. When I removed webhook, everything worked fine on version 0.6.5. On version 0.6.6 the problem persists.