-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
SSL3_GET_RECORD:wrong version number sending any emails since upgrading past 0.37 #5182
Comments
Does your server have a valid SSL certificate chain? |
It's an internal server running rocket without SSL. Also the SMTP relay is running none SSL/TLS on port 25 |
Just to update. I have upgraded the server to 0.48.1 to fix the integration/webhook issue. problem still persists.
|
Hello there, I'm experiencing the same error, 1408F10B:SSL. Is there any news regarding this problem ? |
new error I just spotted registering a new user:
|
this issue was closed via #6940 in 0.56.0 FOR ME Go to Administation->E-Mail->SMTP->Protocol (smtps) |
There is not Protocol option for me in the admin. Edit. |
Update, still not working whatever I set. It's an internal smtp relay with no credential. I'm at a loss of why this doesn't work |
Had a chat with my server admin colleague and he had the awesome idea to setup postfix to relay to the relay. Sending the rocket to localhost works fine now. Don't know what the issue is but I have worked around it. Feel free to close this if I am the only person with the issue remaining. |
Your Rocket.Chat version: 0.47
We've had this issue for a while and I've done a lot of searching.
Since we upgraded past 0.37 we get the error sending any email. Registration, notification and the admin "test" button all produce the error.
We're inside of a corporate LAN with an SMTP relay that requires no authentication.
I experimented with changing the user and password which only produced an invalid login error.
Below is the log file from the most recent upgrade till now.
The text was updated successfully, but these errors were encountered: