mricardi Posted Monday at 12:09 AM Posted Monday at 12:09 AM Hi guys, how are you? I've been having issues with email sending I've been running local tests on my app, including email sending To configure my SMTP connection, I retrieved the details from: Mail -> Configure Email Clients -> Manual Setup user: [Filtered] password: [Filtered] host: covireus-api.helioho.st ssl: true port: 465 I ran my first email sending test and found this error: Connection encountered an error (Hostname/IP does not match certificate's altnames: Host: covireus-api.helioho.st. is not in the cert's altnames: DNS:morty.heliohost.org) To fix this, I replaced the host with: Host: morty.heliohost.org With that change, everything worked perfectly for my local tests the next stepw as to upload everything to the server (covireus-api.helioho.st) and run tests directly from there After the first test on the server, I found this error: Connection encountered an error (connect EHOSTUNREACH 66.220.18.186:465) I’m not sure why it's resolving to 66.220.18.186. As far as I understand, morty ip should be 65.19.154.94 do you have any idea what might be happening guys? Quote
wolstech Posted Monday at 12:57 AM Posted Monday at 12:57 AM Try using localhost for the mail hostname when code is running on the server. The .186 is an old IP (may have been the one used to configure the server base image when we made it). I'll bet it was left in a host file or something. Quote
mricardi Posted Monday at 01:27 AM Author Posted Monday at 01:27 AM Hi @wolstech I tried but in this case the error is: connection encountered an error (Hostname/IP does not match certificate's altnames: Host: localhost. is not in the cert's altnames: DNS:morty.heliohost.org) 🥲 Quote
wolstech Posted Monday at 10:13 AM Posted Monday at 10:13 AM Try port 25 with no encryption. SSL isn't really required for a connection to localhost since it never leaves the server. I'm going to have Krydos a look at this anyway, because I am not sure where the other IP is coming from. 1 Quote
Krydos Posted Monday at 04:00 PM Posted Monday at 04:00 PM 5 hours ago, wolstech said: I'm going to have Krydos a look at this anyway, because I am not sure where the other IP is coming from. This should be fixed, and I added it to the checklist for future Plesk clones. Quote
mricardi Posted Monday at 06:45 PM Author Posted Monday at 06:45 PM Hi guys!! I ran a new test and it works perfectly! thanks a lot!! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.