TLS currently unavailable or error:1408F10B:SSL routines:ssl3_get_record:wrong version number

Pew Pew

New member
I was setting up the mail server and faced an issue. If I try connecting the mail server without TLS turned on, it says "TLS currently unavailable" and if I try it with TLS on(even if I set up the mail server with TLS CIPHERS) It yells at me saying "error:1408F10B: SSL routines:ssl3_get_record: wrong version number". I think it is because the server has an old version of SSL

SSL version of cURL: OpenSSL/3.0.8
OpenSSL version: OpenSSL 1.1.1t FIPS 7 Feb 2023

But, I'm trying to work it out on shared hosting. Does anyone know the reason and fix to the issue?

Also, I tried the same from my local env and it worked so it is neither Xenforo's issue nor the mail server's one (I think)

Server config:
  • PHP 8.3.9
  • MariaDB 10.6.18
  • SMTP port: 25 or 587 depending on TLS status
 
Last edited:
Solution
Please uncheck or disable TLS and try

i had the same issue,
I am using cloudflare TLS 1.2 (minimum) and enforced same from hosting server-side (1.2) .

When both were active on same version and AWS SSL/TLS was checked , it was throwing the same error and no email was being sent, unchecking the box solved the error.
It is your VPS so you probably know more about the setup than we do, but usually port 25 is not used to send (relay) emails but to receive emails.

Port 587 is usually used to receive email for submission (by clients like XenForo). It usually does not have TLS enabled but does support StartTLS.

Tl;Dr Try port 587 without enabling the TLS checkbox.
 
Yes, port 25 is not a standard. But the port works fine for the Xenforo hosted on a VPS rather than a shared hosted XF.

Also, I've tried both the ports, it didn't work.

Tl;Dr Try port 587 without enabling the TLS checkbox.
I think I've tried this, but I'll try it once again and send you the results.
 
The postmark app worked, but our own SMTP didn't. But if I use the same SMTP server on a different Xenforo forum hosted on a VPS, it works perfectly fine.
 
Please uncheck or disable TLS and try

i had the same issue,
I am using cloudflare TLS 1.2 (minimum) and enforced same from hosting server-side (1.2) .

When both were active on same version and AWS SSL/TLS was checked , it was throwing the same error and no email was being sent, unchecking the box solved the error.
 
Solution
i had the same issue,
I am using cloudflare TLS 1.2 (minimum) and enforced same from hosting server-side (1.2) .

When both were active on same version and AWS SSL/TLS was checked , it was throwing the same error and no email was being sent, unchecking the box solved the error.

In my case, may be I will have to take a look at what TLS version my AWS SES is set it on , so may be setting the same 1.2 on AWS side too will work with the checkbox ticked.
 
Thank you, @JasonBrody. It worked

The problem was similar to yours, my hosting provider also provided a TLS record while I was also using Caddy to generate TLS... That's why both of those clashed or something. Thank you very much.
 
Back
Top Bottom