BAD_DECRYPT Error when connecting to a WebSocket
moayadalismail
TRIALOP

a year ago

I'm trying to deploy a web app similar to Kahoot where users can join into a shared game room. However, when the client is trying to request a WebSocket connection, it fails (i.e no response headers are sent back)

On postman, when I try to connect to the socket (wss://XXX.up.railway.app/socket.io/?EIO=4&transport=websocket), I get this error:

1322850779968:error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT:../../../../src/third_party/boringssl/src/crypto/fipsmodule/cipher/e_aes.c:1082:

I made sure to use HTTPS and WSS in my code, but I keep getting this BAD_DECRYPT error. Any solutions?

I'm using NodeJS, Express, Socket IO, and deploying my frontend in Vercel.

My website is www.balibalik.com

My repo is here https://github.com/MoayadAlismail/bali-balik

3 Replies

a year ago

Hello,

To me it looks like /server/index.js is not being ran, since I don't see the logs that would print from lines 433-436 of that index.js file in your deploy logs, instead I see the standard logs from next start

/server/index.js is where you setup socket.io, if that file isn't being ran, WebSockets isn't going to work.


moayadalismail
TRIALOP

a year ago

Hello,

To me it looks like /server/index.js is not being ran, since I don't see the logs that would print from lines 433-436 of that index.js file in your deploy logs, instead I see the standard logs from next start

/server/index.js is where you setup socket.io, if that file isn't being ran, WebSockets isn't going to work.

Ahh! You're right. Works perfectly now. Thanks Brody.


a year ago

No problem!


Loading...