All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Solidseovps.com and problems with mail ports 25, 465, 587
I apologize for my English, I'm just learning this language.
But I have to open this topic.
About half a year ago, I rented a VPS from Solidseovps (https://www.solidseovps.com/).
EPYC- 24GB for $60 for half a year, the offer for this server was on this page: https://lowendtalk.com/discussion/192644/64-95-m-ryzen-dedicated-server-8gb-epyc-deals-starting -60 years
The VPS is hosted in a data center in the Netherlands.
The server was set up after purchase and everything worked perfectly. Including mail. Everything worked without errors and no changes were made. Six months have passed, I am satisfied with the uptime and service and decided to extend the server lease. On October 2, I made a new rent payment of $60.
Everything worked until October 5, in the evening problems with sending mail began. I noticed this from the client, which cannot connect to the server for sending.
I started looking for the problem and saw that all smtp ports were not accessible from the network.
Moreover, on the server itself, the ports are open and the status is listening, there are no prohibitions for these ports in ip-tables. If I connect to the ports in the terminal on this server, everything is fine. As soon as I try from outside the server - there is no connection.
Incoming mail ports are working and not closed.
I contacted technical support several times, everything is fine with them and these ports are open. They say that this type of problem may be in the firewall or other server settings.
sudo netstat -tuln | grep -E '25|465|587'
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN
tcp6 0 0 :::25 :::* LISTEN
tcp6 0 0 :::465 :::* LISTEN
lsof -i -n -P | grep :25
master 3448 root 13u IPv4 33506 0t0 TCP *:25 (LISTEN)
master 3448 root 14u IPv6 33507 0t0 TCP *:25 (LISTEN)
sudo ufw status
Status: active
To Action From
-- ------ ----
587 ALLOW Anywhere
20/tcp ALLOW Anywhere
80/tcp ALLOW Anywhere
443/tcp ALLOW Anywhere
39000:40000/tcp ALLOW Anywhere
15286/tcp ALLOW Anywhere
629/tcp ALLOW Anywhere
629/udp ALLOW Anywhere
2372/tcp ALLOW Anywhere
21/tcp DENY Anywhere
22/tcp DENY Anywhere
7800 DENY Anywhere
110/tcp ALLOW Anywhere
110/udp ALLOW Anywhere
143/tcp ALLOW Anywhere
143/udp ALLOW Anywhere
465/tcp ALLOW Anywhere
465/udp ALLOW Anywhere
995/tcp ALLOW Anywhere
995/udp ALLOW Anywhere
993/tcp ALLOW Anywhere
993/udp ALLOW Anywhere
3389 ALLOW Anywhere
4000 ALLOW Anywhere
8649/tcp ALLOW Anywhere
878/tcp ALLOW Anywhere
878/udp ALLOW Anywhere
587/udp ALLOW Anywhere
773/tcp ALLOW Anywhere
773/udp ALLOW Anywhere
25/tcp ALLOW Anywhere
587/tcp ALLOW Anywhere
25 ALLOW Anywhere
587 (v6) ALLOW Anywhere (v6)
20/tcp (v6) ALLOW Anywhere (v6)
80/tcp (v6) ALLOW Anywhere (v6)
443/tcp (v6) ALLOW Anywhere (v6)
39000:40000/tcp (v6) ALLOW Anywhere (v6)
15286/tcp (v6) ALLOW Anywhere (v6)
629/tcp (v6) ALLOW Anywhere (v6)
629/udp (v6) ALLOW Anywhere (v6)
2372/tcp (v6) ALLOW Anywhere (v6)
21/tcp (v6) DENY Anywhere (v6)
22/tcp (v6) DENY Anywhere (v6)
7800 (v6) DENY Anywhere (v6)
110/tcp (v6) ALLOW Anywhere (v6)
110/udp (v6) ALLOW Anywhere (v6)
143/tcp (v6) ALLOW Anywhere (v6)
143/udp (v6) ALLOW Anywhere (v6)
465/tcp (v6) ALLOW Anywhere (v6)
465/udp (v6) ALLOW Anywhere (v6)
995/tcp (v6) ALLOW Anywhere (v6)
995/udp (v6) ALLOW Anywhere (v6)
993/tcp (v6) ALLOW Anywhere (v6)
993/udp (v6) ALLOW Anywhere (v6)
3389 (v6) ALLOW Anywhere (v6)
4000 (v6) ALLOW Anywhere (v6)
8649/tcp (v6) ALLOW Anywhere (v6)
878/tcp (v6) ALLOW Anywhere (v6)
878/udp (v6) ALLOW Anywhere (v6)
587/udp (v6) ALLOW Anywhere (v6)
773/tcp (v6) ALLOW Anywhere (v6)
773/udp (v6) ALLOW Anywhere (v6)
25/tcp (v6) ALLOW Anywhere (v6)
587/tcp (v6) ALLOW Anywhere (v6)
25 (v6) ALLOW Anywhere (v6)
The firewall was disabled using the command 'sudo ufw disable', but this did not bring any results, ports 25 and 465 remained unavailable.
I execute the command in the terminal - "tcpdump -n -i eth0 port 25" after which I access port 25 via telnet (telnet 130.117.79.183 25). As a result, I do not receive any packets to the server and port 25.
Watch the first video with the name 25.
All the videos i upload to google drive
https://drive.google.com/file/d/1iZIoJTGot3xWPe_XS3JFa2KsGdX5CpdC/view?usp=drive_link
After that, I do everything the same, but for port 995. Packets reach this port. Watch the video titled 995.
https://drive.google.com/file/d/1EZCdgPpZ0Lz_iymenIplObLmQBvHfuev/view?usp=sharing
To exclude problems with my Internet provider, I repeat the same commands for port 25 from the terminal of my other vps server, which is also located in the Netherlands. As a result, the packets also do not reach the server hosted by Solidseo.
Watch the video titled vps-ND.
https://drive.google.com/file/d/1SoeF7h_lWpBeBh8kZFglPoP-qF2TewEB/view?usp=sharing
Temporarily solved the problem by opening a different smtp port. Sending works.
But there is a problem with receiving incoming mail, I understand that port 25 is needed by many services for system communication. Because of this, mail from gmail is not sent to my server, but returns with errors.
I contacted technical support three times in a week. Each time they had an answer that their ports were open. But why I do not see receiving any packets when executing the tcpdump command for port 25, no one has ever explained. Although if the problem was precisely in the server configuration, then tcpdump would have detected the arrival of packets on port 25 in any case, and now everything looks like the ports are blocked somewhere in the network infrastructure on the way to the server.
Mail was used only to inform customers about their orders. There has never been any mass mailings or spam.
Here is the information for those who plan to buy servers from solidseovps.
I will be glad if you prove that I am wrong and this is a problem in the server settings.
Comments
Sounds like you might have multiple firewall scripts running on the server, antispam software that is misconfigured, or firewall rules in your provider's control panel.
What software are you using?
open a ticket with SolidSeoVPS and ask them to enable these ports for you.
Someone in the thread you posted asked if port 25 was open and the provider said for that person to put in a request and they would open it.
did you not read the whole first message? there I wrote that I opened a ticket and wrote about the problem, I was answered that these ports are not blocked for me
There are no any firewall rules in provider's control panel.
I use one firewall on the server - ufw. these ports are open in firewall. dovecot and postfix work as a mail server. I use aapanel as a server control panel. from the moment of installing the server and its configuration until the moment of problems with the ports - no additional settings were performed. I also use cloudflare for domains. but there the settings are standard and recommended for cloudflare.
ya I did read it, it looks like they are blocking you despite telling you otherwise.
Checking my VPS, I never asked for the port to be open. I ran tcpdump on one VPS and telnet from another VPS (both from solid). It received packets but telnet said connecting. After remembering to add it to ufw port 25, received packets and telnet said connection refused. Trying from other providers talnet is forever connecting. So looks blocked for output for me.
If you think it's you and not Solid try adding a bootable Linux ISO and boot from it on the VPS, see if a fresh start works.
And tagging solid. @SolidSeoVPS
I use virtualmin as a panel, everything is fine. I have the same plan as you and everything works fine. aapanel always has problems with emails. I had several problems and that's why I changed to virtualmin.
I use aapanel on about 4 different servers in different countries and have never had a problem with mail. the problem is only on the solidseovps server. if the problem is precisely in aapanel, then why is the new smtp port that I opened now and which is working correctly at the moment working. but the problem is that a working port 25 is required for the correct operation of the mail server and receiving mail from other servers.
If it's a basic aaPanel installation, you should not have these issues.
You can see active firewall rules with
iptables -L | grep 25. There should not be any when UFW is disabled.You can try to replicate the issue on another VPS. If you don't have an idle one, there are two affiliate links with free credit for new customers in my signature. Vultr doesn't block mail ports. Hetzner does, but they can be opened with a support ticket.
You can also move (backup/restore) everything to a temporary VPS, change DNS in Cloudflare, and reinstall the Solidseovps when everything is moved. If port 25 is blocked in a fresh Linux installation, it can only be the provider causing the issue.
@SolidSeoVPS
I think colocrossing did this to me! The cheeky so and sos, told me ports are opened on 2 servers yet every single test email still marked as deffered. Not interested in them anymore.
And @trialon77 you are not running this all on cpanel are you? I just had one break on me out of nowhere, webmail interface wasn't working at all, also emails werent. Tried resinstalling a load of services, turning off firewall etc and connection still refused on all the ports relating to mail. So I thought all my mail ports were blocked or something as everything else seemed to be ok and running but nothing coming back to life.
Complete reinstall fixed it in the end.
>
Unfortunately, in my case, reinstalling mail does not help. I did it twice
Hi, we remember you! We’ve confirmed that all the mentioned ports are open on our end, and we’ve also shared a snapshot showing them open from our side. Unfortunately, a port can only be open or closed—there’s no middle ground. If the issue persists despite being open on our side, we recommend reviewing your setup to ensure everything is configured correctly.
interesting, interesting And strangely everything worked after your reply today.
Are you having a hard time admitting that the ports were closed after all and you found the problem and fixed it today?
Maybe it's not your fault, maybe there was a failure somewhere in the network infrastructure of the data center.
At the moment, everything is working, I have not made any changes to the settings on the server.
Thank you
@trialon77 glad to hear it's working. We've been saying the same for the past few weeks and haven't made any changes on our end either.
it's not funny anymore, yesterday around 5pm all these ports stopped working again! it's terrible, in 10 years of renting different VPS servers, I have never seen such a thing!!!
Again, nothing changed in the settings during this time!
Some kind of mystery, after your first answer the ports worked, after the second - they don't work again!
Terrible service and lack of desire to understand the problem!
Honestly, not the first time I've seen something, especially if/when dealing with APIs, showing one thing but doing another.. Then giving a 'kick' while not making any changes, correcting the issue.
Doesn't usually return though, but have seen stranger things happen.
Best of luck to both sides.
I bought the same server and I use it as a mail server and website. I've had it for almost 8 months and I haven't had any problems with the ports.