Webmail not loading

[tdot]

When I try to access webmail via example.com:2096 or directly through cpanel. It seems to timeout. I've tried it for all domains/accounts but still have the same issue.

 

[cPanelMichael]

Hello,

Is it possible your ISP or router rules are blocking outgoing connections to the server over port 2096? You could try accessing "webmail.domain.tld" to see if access to webmail works over port 80.

Thank you.

 

[tdot]

Port TCP 2096 is definitely open in my server firewall. I've not added a record for 'webmail.domain.tld' in my DNS so I cant check that. Nothing on my home connection is blocking it either.

 

[cPanelMichael]

Hello,

You can verify that ports 2095 and 2096 are listening for connections with a command like this on the cPanel server:

netstat -lnp | grep :209

The output should look like this:

# netstat -lnp | grep :209
tcp        0      0 0.0.0.0:2095            0.0.0.0:*               LISTEN      21002/cpsrvd (SSL)
tcp        0      0 0.0.0.0:2096            0.0.0.0:*               LISTEN      21002/cpsrvd (SSL)

Also, are you using a CDN such as CloudFlare for this domain name? Or, can you reproduce the issue when accessing the IP address directly (e.g. htxxs://$IP:2096)?

Thank you.

 

[Anupkum]

Hi, I am facing the same issue. attaching output of # netstat -lnp | grep :209 below.



Please help...

 

[cPRex]

@Anupkum - can you let me know what happens in the browser when you try to connect to webmail? Knowing that will allow me to give you better information.

 

[Anupkum]

Here is the error I get while opening mail from cPanel .

This site can’t be reached
xyz.com took too long to respond.


Try:

• Checking the connection
• Checking the proxy and the firewall
• Running Windows Network Diagnostics

ERR_CONNECTION_TIMED_OUT

 

[cPRex]

Thanks for the additional details. Even though the services may be listening on those ports it seems like they might be blocked either at the server itself or at a higher level outside the machine. Can you check the server's firewall to ensure the webmail ports are open for traffic?

 

[Anupkum]

Here is list of all open ports. Please have a look and let me know if you find anything wrong...

 

[cPRex]

I don't see 2096 on there, which is the secure webmail port. Can you make sure that gets added?

We have a full list of ports here, so you8'll want to make sure these are all in place as well so all services will work properly: How to Configure Your Firewall for cPanel & WHM Services | cPanel & WHM Documentation

 

[Anupkum]

Thank you for your help. webmail is now opening .

But, emails are not working. I am not receiving emails from people and If I send they don't get it from me. What would be some other reasons behind it?

Please help...

 

[cPRex]

I'm glad the webmail access is working well for you now.

In the port list you provided, I don't see that port 25 is open for traffic. You'd want to make sure that is open as that will allow you to both send and receive messages properly.

If the port is opened on your local firewall, it's possible that your hosting provider is blocking that port on their network, as many providers do. You can test that by running the following command:

telnet mx1.cpanel.net 25

That will tell you if you can reach an external mail server. If you can't, port 25 is likely blocked by your provider and you would need to use a third-party email service to send messages properly.

If you get an error that telnet is not installed, you can install it quickly with this command so you can perform the test.

yum install telnet

 

[Anupkum]

Hello,
thank you for your quick reply.

I am using EC2 instance on AWS and had port 465 for SMTP. After your suggestions I have opened port 25 as well in the security network.

I ran code you shared but seems none of them are going to work. Attaching screenshot or response received..



Please let me know what I can do to get it fixed.

I really appreciate your help...

 

[cPRex]

It seems there are some Yum issues separate from the mail issue as well on this machine.

For the email issue, you likely won't be able to send messages normally on an Amazon server. They block port 25 for outbound traffic, so you'll need to use a third-party tool to send messages. We have some additional details on this here:

Why can I receive, but not send, emails?

Question When trying to send mail from your server, messages never arrive, and you possibly receive bounce-back messages stating the message was undeliverable. You can typically receive mail and ...

support.cpanel.net

As far the Yum issue, there's a few different things that could cause that, such as missing operating system packages or bad data in the repository itself. If you are using CentOS 6 on that server, can you check the following thread and try the workaround there?

SOLVED - YumRepo Error and Cannot find valid baseurl

After updates ran last night, we got this error message: Maintenance ended; however, it did not exit cleanly (256). The following events were logged: “scripts/rpmup”. Review the update logs to determine why the update failed. and [2020-12-02 02:44:21 -0800] E [/usr/local/cpanel/scripts/rpmup]...

forums.cpanel.net

 

[Anupkum]

Hi,
A very happy new year to you and family.

I have successfully installed Telnet, but still when I run telnet mx1.cpanel.net 25 it is giving result as connection timeout.

Attaching screenshot for reference.

 

[kodeslogic]

The below link may help you with your EC2 instance:

Remove port 25 restriction from your EC2 instance

aws.amazon.com

.

 

[cPRex]

It does sound like port 25 is blocked as mentioned in those links provided. Were you able to speak with Amazon about that issue?

 

[Anupkum]

Hello,

I raise request to amazon to enable port 25 and now they are asking for a valid A valid email host name (Ex: "mail.yourdomain.com") .

But, when I open mine mail.mydomain.com or webmail.mydomain.com it is not opening in the browser. It is saying This site can’t be reached

DNS_PROBE_FINISHED_NXDOMAIN

Your help is much appriciated...

 

[cPRex]

That sounds like there is no DNS record for the mail or webmail subdomain. You'd need to make sure those DNS records exist before the page will work in a browser.