Issue with live browser session: blank screen after refresh

[justsanjit]

I’m currently using the hosted version of Steel Browser, and embedding the browser into my application using the debugUrl provided in response when initiating a new session.

On the initial load, everything works as expected — I can see the live browser session successfully within my app. However, after refreshing the page, the live browser no longer loads. Instead, I only see a blank white screen.

In the browser console, I see the following error:

Similarly, when I open the same session directly on steel.dev, I encounter the same issue — just a blank screen. Please refer to the screenshot below for reference:

I’m not sure if I’m missing something, or if this might be an issue on Steel Browser’s side. Any guidance or help in resolving this would be greatly appreciated!

[fukouda]

hey @justsanjit this is definitely not intended -- going to try and recreate this with steel cloud and see what might be causing this. Btw, what region are you accessing steel from (just for ideal network conditions to reproduce)

[justsanjit]

Sorry for delayed response. I was attempting to access steel from Western Canada

[fukouda]

hey @justsanjit , apologies for the delay here but I believe this should be fixed now! Let me know if you're still running into issues :)

[mustafaAwwal]

I don't see any error in the browser but I have the similar issue. It will get stuck in session connecting or the session would go offline in a minute or two.

[fukouda]

Hey @mustafaAwwal, the session viewer itself is pretty network intensive. Could you benchmark your internet speed and tell me what it says? Just to see if that might be the issue (and I can try to reproduce).

[mustafaAwwal]

Hey thanks @fukouda thanks for the help. It was due to my internet. I have shifted to a high speed internet connection and it is working fine.

[justsanjit]

The issue appears to be back. I believe it’s now caused by an incorrect WebSocket URL. Refer to the console logs below for details.

[keyanatmotorola]

Hey @fukouda This issue is everywhere and stucking the whole open source to not usable, can you provide the issue fix?