Troubleshooting Portal WebSockets
Occasionally the RackN Portal will have connectivity issues due to the self-signed certificates expiring.
When the socket loses connection, a megaphone icon button on the top left will flash red and say "Unable to access DRP"
Clicking this icon will yield the error code and status.
Solution¶
See additional information for a list of error codes.
The most common and hard to troubleshoot issue is the [1006 - CLOSE_ABNORMAL]{.title-ref} error. This usually happens when the browser does not show the accept certificate page when the websocket is getting TLS errors.
The easiest fix is to completely close and re-open the browser so the accept certificate dialog can be shown.
Additional Information¶
List of RFC6455 Web Socket status codes, most of which are never seen or are not used:
1000
-CLOSE_NORMAL
- Normal closure1001
-CLOSE_GOING_AWAY
- Server goes down or webpage is navigated away from1002
-CLOSE_PROTOCOL_ERROR
- Endpoint terminates connection due to protocol error1003
-CLOSE_UNSUPPORTED
- DRP or UX sends unsupported data (binary instead of text)1005
-CLOSED_NO_STATUS
- Should never get this, it means no status code was provided1006
-CLOSE_ABNORMAL
- Socket closed without a close control frame - likely due to TLS errors1007
-Unsupported payload
- Sending non-UTC-8 data1008
-Policy violation
- Should never get this, it means the message violates policy1009
-CLOSE_TOO_LARGE
- Happens when a message is too long, the portal should automatically reconnect1010
-Mandatory extension
- Not implemented1011
-Server error
- Server crashed1012
-Service restart
- Server is restarting1013
-Try again later
- Not implemented1014
-Bad gateway
- Not implemented1015
-TLS handshake fail
- Server certificate cannot be verified
See Also¶
- rs_portal
- Visit Stable Portal
- Visit Tip Portal
Versions¶
This document applies to all versions of Digital Rebar and RackN Portal v1.18+
Keywords¶
ux, portal, websocket, socket, tls, certificate, browser, faq, abnormal, close_abnormal, close