Blank pages after coming back to a session

Blank pages after coming back to a session

avatar
Dynamic66

This is from a Blank PSU app that I had open while shutting down my PC for the day. After coming back this morning, my browser automatically opens my last pages, and all PSU apps recently have returned completely blank.

The setup includes 2 PSU servers with a Postgres database on version 2026.2.3. A load balancer/reverse proxy is in place with sticky sessions enabled. (ip hashing)

There seems to be an error indicating that sticky sessions are not enabled. I request this scenario to be handled properly or that the page would auto-reload when an old WebSocket connection can't be established.

[2026-08-22T09:15:04.232Z] Information: Normalizing '/dashboardhub?dashboardid=6&pageid=1...' to 'https://domain.com/dashboardhub?dashboardid=...
3f0d01ed210f9fa93137.bundle.js:60 WebSocket connection to 'wss://domain.com/dashboardhub?dashboardid=...' failed: 
(anonymous) @ 3f0d01ed210f9fa93137.bundle.js:60
3f0d01ed210f9fa93137.bundle.js:60 [2026-08-22T09:15:04.355Z] Information: (WebSockets transport) There was an error with the transport.
3f0d01ed210f9fa93137.bundle.js:60 [2026-08-22T09:15:04.355Z] Error: Failed to start the transport 'WebSockets': Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled.
log @ 3f0d01ed210f9fa93137.bundle.js:60
APPNAME:1 EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection.
3f0d01ed210f9fa93137.bundle.js:60 [2026-08-22T09:15:04.450Z] Error: Failed to start the transport 'ServerSentEvents': Error: EventSource failed to connect. The connection could not be found on the server, either the connection ID is not present on the server, or a proxy is refusing/buffering the connection. If you have multiple servers check that sticky sessions are enabled.
log @ 3f0d01ed210f9fa93137.bundle.js:60
3f0d01ed210f9fa93137.bundle.js:60 [2026-08-22T09:15:04.606Z] Error: Error parsing handshake response: Error: Message is incomplete.
log @ 3f0d01ed210f9fa93137.bundle.js:60
3f0d01ed210f9fa93137.bundle.js:60 [2026-08-22T09:15:04.606Z] Error: Connection disconnected with error 'Error: Error parsing handshake response: Error: Message is incomplete.'.
log @ 3f0d01ed210f9fa93137.bundle.js:60
3f0d01ed210f9fa93137.bundle.js:60 Uncaught (in promise) Error: Error parsing handshake response: Error: Message is incomplete.
    at X._processHandshakeResponse (3f0d01ed210f9fa93137.bundle.js:60:97903)
    at X._processIncomingData (3f0d01ed210f9fa93137.bundle.js:60:96893)
    at N.onreceive (3f0d01ed210f9fa93137.bundle.js:60:91400)
    at N._poll (3f0d01ed210f9fa93137.bundle.js:60:70873)
3f0d01ed210f9fa93137.bundle.js:60 [2026-08-22T09:15:04.643Z] Information: Using HubProtocol 'json'.
3f0d01ed210f9fa93137.bundle.js:60 Uncaught (in promise) Error: Error parsing handshake response: Error: Message is incomplete.
    at X._processHandshakeResponse (3f0d01ed210f9fa93137.bundle.js:60:97903)
    at X._processIncomingData (3f0d01ed210f9fa93137.bundle.js:60:96893)
    at N.onreceive (3f0d01ed210f9fa93137.bundle.js:60:91400)
    at N._poll (3f0d01ed210f9fa93137.bundle.js:60:70873)

All Comments (3)

avatar
Dynamic66

here is how it looks like to come back to a old session. 🙃

1a3e1e68-6203-43ec-ba18-1cf2375b45c9.png

avatar
rubentapia

Hello Dynamic66,

Thank you for the detailed report and screenshots.

The console output shows the connection first failing over WebSockets, then failing again with ServerSentEvents, followed by an incomplete SignalR handshake. The message about sticky sessions lists them as one possible cause, but it does not by itself confirm that session affinity is disabled.

To help isolate whether this is related to restoring an old browser session, the load balancer path, or how the PSU App handles the failed reconnection, could you please confirm the following?

* When the page is blank, does a normal refresh or hard refresh restore the App?
* Does opening the same App in a new tab work immediately?
* Which browser and browser version are you using?
* Which load balancer/reverse proxy product is in front of the two PSU nodes?
* If possible, can you reproduce the same stale-session scenario while connecting directly to a single PSU node and bypassing the load balancer?
* Did either PSU node restart or recycle while the browser was offline?

At this stage, I do not want to assume that the load balancer is the root cause. The blank page itself after the connection failure is also something we need to account for.

Best regards,
Ruben Tapia

avatar
Dynamic66
  • A normal refresh is enough to reestablish the webpage.
  • Yes, the app works immediately in a new tab. The issue occurs only when an old tab is reopened.
  • I am running the latest version of the Brave browser(chromium), but I have observed this issue on other Chromium and Firefox browsers as well.
  • My reverse proxy is Caddy. I observed a similar issue in setups without a reverse proxy. In my local testen env for example


I found an old issue of mine that occurred on non-blank pages. I'm not sure if it's the same issue, but it looks similar.
https://github.com/ironmansoftware/powershell-universal/issues/5287

i have not encountered this issue on mobile yet