Issue with Listening to Laravel Reverb WebSocket Events in Postman

[Emoumo-coder]

Hello Laravel Team,

I'm currently using Laravel Reverb for real-time WebSocket events in my application, following all steps outlined in the official documentation. However, I’m encountering an issue:

When I connect to the WebSocket via the browser using Laravel Echo, events are received as expected. However, using Postman's WebSocket client with the same Reverb WebSocket URL (ws://localhost:8080/app/{reverb_api_key}), the connection establishes successfully, but no events are received when messages are dispatched.

Setup Details

• Reverb Configuration:
  • REVERB_APP_ID, REVERB_APP_KEY, and REVERB_APP_SECRET are all set correctly in the .env file.
  • WebSocket connections are directed to /app as per the documentation.
• URL Used:
  • In the browser: ws://localhost:8080/app/{reverb_api_key} (works with Laravel Echo).
  • In Postman: ws://localhost:8080/app/{reverb_api_key} (connects but does not receive events).

Observed Behavior

• In the browser: Events are received on the WebSocket as expected.
• In Postman: The WebSocket connection opens, but no events are triggered or received.

It seems that the Laravel Echo client might be handling Reverb’s WebSocket events differently than Postman’s WebSocket implementation. Could this be an issue with Reverb’s handling of WebSocket events outside Laravel Echo, or is there additional configuration needed when working with non-browser clients like Postman?

Any guidance or clarification on using Reverb WebSocket with other WebSocket clients would be greatly appreciated.

Thank you!

[haziq-se]

I am also facing the same issue. I tried various configurations, but nothing worked. Did you find a solution?

[Emoumo-coder]

I couldn't get it to work, I had to switch to PUSHER.

[ozanuzer]

Maybe somebody look that page in time :)

You should send message after connection.

{
"event":"pusher:subscribe",
"data":{
"auth":"",
"channel":"allTasks"
}
}

write that and push send button. You will see public events after that.

[Emoumo-coder]

Yes, I have observed that, but it only works for public channels. Moreover, it's not ideal to have to send a message before I can trigger events.