register / login screen fails on chrome

[malko]

To Reproduce

1. install dockploy on a personal network setting ADVERTISE_ADDR to local network address
2. open the register page on local network (http://myip:3000/register) using chrome browser
3. start filling the form and see the page totally freeze with a lot of websocket errors

What is weird is register can be achieved with no issue using firefox but login is still impossible using chrome browser.

Current vs. Expected behavior

Expecting to be able to register or login using chrome browser after a fresh install

Provide environment information

Operating system
  OS: ubuntu 22.04
  ARCH: i386
dockploy version:  v0.20.8

Which area(s) are affected? (Select all that apply)

Installation

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Maybe, need help

[malko]

Here's some screenshots of the console:

[Siumauricio]

I don't know how to reproduce this problem, using one of the providers we recommend in our list works fine https://docs.dokploy.com/docs/core/installation#providers

[SteadEXE]

I have the same issue aswell, it freeze after a few second after waiting on the login or TFA page. The whole tab crash, same behavior on Chrome/Brave/Chromium & Edge. I have to wait until browser ask to kill the unresponsive tab

I can only use Dokploy on Firefox at the moment

It crashes after sending a huge amount of request

[SteadEXE]

@malko are you using Linux as well? It spams on Windows aswell, but it looks like tab doesn't freeze.

[SteadEXE]

I can confirm, I have the exact same requests spam on https://app.dokploy.com/ (and same console error about web socket already in CLOSING state) I guess because of the high latency of the requests (~400ms), it takes way more time until tab dies, so you have enough time to login, but it still dies after a while. Once you are logged, it's fine, no more spam.

After performing extensive testing, when I try to log to a Dokploy instance with virtually no latency (hosted on same LAN), the spam on /drawer-logs kills my tab. Meanwhile I can safely login to an instance not on my LAN.

I manage two Dokploy instance, one in my home lab, one in my company's LAN. From my house I cannot login to my home lab instance while I can login to my company's instance.

And when I am at the headquarter, I cannot login on company's instance while I can log to my home lab. I really think the root cause of the issue is the glitchy websocket

[malko]

@SteadEXE yes using linux, juste installed a new dokploy instance on a new ugreen nas and same problem still arise. The only way to pass through the login screen was again to use firefox to create the admin account. The admin account is then setup in my chrome password manager and so i can login using chrome (must be fast enough before the tab hangs)

[malko]

@Siumauricio I think it works fine due to network latency as explained by @SteadEXE. Try to open the console i'm pretty sure you will see the same problems. Perhaps it is related to the fact that in my case at least it's not a HTTPS connection but a HTTP only as it is on local network. @SteadEXE are you experiencing the problem using HTTP or HTTPS on your side ?

[malko]

@SteadEXE your feedback helped me to find a workaround to finally be able to login with chrome => open chrome dev tools and then in network panel set throtling to slow network. This allow to give some time to finally get the login screen to work. Once logged in I can disable throtling and close dev tools.

[SteadEXE]

I have the issue with HTTPS, never tried with HTTP. I have the issue with either invalid or valid certificate. I also started to use network throttling to be able to log in with Brave. I saw a refactor of the web socket in a commit a few day ago, maybe @Siumauricio already fixed it. I am not experienced enough with the codebase to propose some changes

[SteadEXE]

Any update on this issue?

[malko]

it seems that it doesn't block the screen on latest version, but there's still heavy load with a ton of websocket failing. I think the problem is the websocket trying to connect to quickly but the user still not authentified. Probably the best way would be to avoid websocket at all on the login page.

[SteadEXE]

It still freeze the login page for me, if you logout, there is no spam, it only happen if you arrive on login page without being logged or redirected

[Naresh-Khatri]

Having the same issue with fresh install of latest dokploy in my homelab

[Naresh-Khatri]

A workaround for this is to throttle your network to 3G. It reduces this ws req fequency, so you get a while to register yourself.

[JhonatanPereira]

Any updates? I'm experiencing the same issue with a fresh installation.

[pompydev]

Encountered the same bug with:

• OS: NixOS
• Installation method: manual installation
• Browser: Brave Version 1.78.97 Chromium: 136.0.7103.93

[lucaspintos909]

Encountered the same bug with:

OS: NixOS Installation method: manual installation Browser: Brave Versión 1.77.101 Chromium: 135.0.7049.115

[SteadEXE]

I hate pinging but it feels like issue is stall, @Siumauricio do you think it could be fixed soon, it's impossible to login without setting any network throttle on the app? I just checked in 0.23.3 issue is still present

[Siumauricio]

Ok, it seems that the problem is solved in this PR, I see that infinite connections are not created, only 1 is created when using trpc subscriptions, so this problem should not happen anymore. #2139