Reverb error handling in application level

[ShashankInsnapsys]

Reverb Version

1.5

Laravel Version

11

PHP Version

8

Description

I'm trying to handle the following error at the application level:

Connection from tcp://127.0.0.1:40278 failed during TLS handshake: Unable to set private key file `'

Initially, I tried overriding the Server class, but this doesn't seem like a stable or future-proof solution, especially with potential updates to Reverb. Is there a recommended or reliable way to catch and handle TLS/SSL handshake errors within the application itself, without modifying the core server logic?

Steps To Reproduce

• Install Reverb in your application.
• Intentionally trigger an SSL handshake error (e.g., by omitting the private key file path).
• Given this setup, how can we catch or handle such SSL/TLS handshake errors at the application level? I want to log these errors separately, outside of the default logging mechanism.

[crynobone]

Intentionally trigger an SSL handshake error (e.g., by omitting the private key file path).

Shouldn't the file always be available?

[ShashankInsnapsys]

Shouldn't the file always be available?

It's just an example; there are multiple possibilities of SSL handshake errors (like file may not be available, file may not have permissions, etc.). So I just want to know, how we get this error on the application level?

Now, I'm able to get the react/socket level errors on reverb but is there any other way I can emit an event from reverb and listen that event in my application? or is there any inbulit event in reverb that I can directly listen in my application? so I don't need perform any changes in my vendor folder.

[github-actions]

Thank you for reporting this issue!

As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub.

If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team.

Thank you!