-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.x] Fix the issue for connecting if the SSL is not verified peer #85
Conversation
If the certificate does not need local_pk, then it won't load local_cert at the moment. I think part of the tls content should be commented out. |
I want to sit on this one a little while as I'm not convinced it's needed. |
This fixed my problem during local development with Laravel Valet. Thanks :) |
I wouldn't sit on this. I've had nothing but trouble trying to get reverb working locally on MacOS with Herd secured sites. The most frustrating part is it will work one day and be broken the next. The changes to the Factory.php with this config entry resolves my problems: 'options' => [
'tls' => [
'verify_peer' => false,
],
], I would suggest adding verify_peer as it's own env variable. |
Really, the problem has solved, please @joedixon merge this, If you want, I can make another more detailed PR. |
Pushed some updates here which will resolve #93, #105 and possibly #106. I opted not to include config by default for all of the SSL context options, but instead allow users to configure it manually. Now, the check for Valet and Herd certificates will only be carried out if both Additionally, |
This update broken forge applications running with ssl |
Hi @lsdevelop, can you elaborate on what was broken? Are you running your Reverb server directly from the |
Hi, yeah, I have a chat app with deprecated websockets, after launching reverb, I up stating environment in forge for testing using @beta of reverb, After merge this commit in next deployment the connection has return error for tls. Solved after downgrade for beta4, I'm trying again now. |
@lsdevelop you would have only seen this update if you explicitly used Can you confirm the steps you took and verify the error you saw? |
See: #78