You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 7, 2024. It is now read-only.
we already have added a private key path with correct permissions, but it still shows this when the web socket client tries to connect to the web socket server.
This discussion was converted from issue #800 on July 19, 2021 10:19.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to access with WSS. Set certificate & private key file path in .env file. but getting below error
we already have added a private key path with correct permissions, but it still shows this when the web socket client tries to connect to the web socket server.
Beta Was this translation helpful? Give feedback.
All reactions