# [Bug] SignalR Connection Error Displayed Without Login #1147

New Issue

2026-09-23T04:33:13Z

enjin2310 commented

2026-09-23 04:33:13 +00:00

Summary

When accessing SpikerSoft Learn → Coding → Languages → C# (or any other language) without logging in, the Console Output panel incorrectly displays a SignalR connection error. This message should not appear to unauthenticated users, as it exposes internal server details and creates confusion.

Issue Description

Upon opening the playground without logging in, the right-hand panel shows:

Error: Failed to connect to SignalR: WebSocket failed to connect...

This error indicates that the system is attempting to establish a SignalR connection before authentication, which should be deferred until the user session is active. The message is unnecessary for guest users and should be suppressed or replaced with a neutral placeholder.

Environment

Property	Value
Application	SpikerSoft Learn
Module	Coding → Languages → C#
Environment	Production
Browser	Firefox
Operating System	Windows 11
Version	v2026.09.23b
Device	Desktop

Preconditions

User is not logged in.

Steps to Reproduce

Open SpikerSoft Learn.
Navigate to Coding → Languages → C# (or any other language).
Observe the Console Output panel on the right.
The SignalR connection error appears immediately.

Expected Result

The Console Output panel should remain empty or display a neutral message such as “Log in to run code.”
No server or connection error should be visible to unauthenticated users.

Actual Result

The Console Output panel shows a detailed SignalR WebSocket error.
The message exposes internal connection details and creates confusion.

Evidence

The screenshot shows the SignalR connection error displayed in red on the right panel while the user is not logged in.

Impact

Reduces user experience quality for new or unauthenticated users.
Exposes unnecessary technical details.
May lead users to believe the platform is malfunctioning.

Frequency

Always

Reproducibility

100%

Severity

Medium

Suggested Fix

Suppress SignalR initialization until user authentication is confirmed.
Replace error display with a neutral placeholder message (e.g., “Please log in to run code”).
Ensure the Console Output panel initializes only after a valid session is established.

## Summary When accessing **SpikerSoft Learn → Coding → Languages → C#** (or any other language) without logging in, the **Console Output** panel incorrectly displays a **SignalR connection error**. This message should not appear to unauthenticated users, as it exposes internal server details and creates confusion. ## Issue Description Upon opening the playground without logging in, the right-hand panel shows: > *Error: Failed to connect to SignalR: WebSocket failed to connect...* This error indicates that the system is attempting to establish a SignalR connection before authentication, which should be deferred until the user session is active. The message is unnecessary for guest users and should be suppressed or replaced with a neutral placeholder. ## Environment | Property | Value | |-----------|--------| | Application | SpikerSoft Learn | | Module | Coding → Languages → C# | | Environment | Production | | Browser | Firefox | | Operating System | Windows 11 | | Version | v2026.09.23b | | Device | Desktop | ## Preconditions User is **not logged in**. ## Steps to Reproduce 1. Open **SpikerSoft Learn**. 2. Navigate to **Coding → Languages → C#** (or any other language). 3. Observe the **Console Output** panel on the right. 4. The SignalR connection error appears immediately. ## Expected Result - The **Console Output** panel should remain empty or display a neutral message such as “Log in to run code.” - No server or connection error should be visible to unauthenticated users. ## Actual Result - The **Console Output** panel shows a detailed SignalR WebSocket error. - The message exposes internal connection details and creates confusion. ## Evidence - The screenshot shows the **SignalR connection error** displayed in red on the right panel while the user is not logged in. ## Impact - Reduces user experience quality for new or unauthenticated users. - Exposes unnecessary technical details. - May lead users to believe the platform is malfunctioning. ## Frequency Always ## Reproducibility 100% ## Severity Medium ## Suggested Fix - Suppress SignalR initialization until user authentication is confirmed. - Replace error display with a neutral placeholder message (e.g., “Please log in to run code”). - Ensure the **Console Output** panel initializes only after a valid session is established.

Screenshot 2026-09-23 002706.png

180 KiB

spikerj commented

2026-09-27 05:07:00 +00:00

Closing in the 2026-09-27 tracker sweep — already implemented.

Fixed by spikerj/spikersoft-angular#1276: the playgrounds no longer dial the authenticated code hub for signed-out visitors, so the SignalR WebSocket error is gone; running server-side code while signed out now shows 'Sign in to run code on SpikerSoft's servers.' instead.

Reopen if this still needs work.

Closing in the 2026-09-27 tracker sweep — already implemented. Fixed by spikerj/spikersoft-angular#1276: the playgrounds no longer dial the authenticated code hub for signed-out visitors, so the SignalR WebSocket error is gone; running server-side code while signed out now shows 'Sign in to run code on SpikerSoft's servers.' instead. Reopen if this still needs work.

spikerj closed this issue

2026-09-27 05:07:00 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#1147