Domain that you have provided is not configured as rDNS for your server IP. [404]

I’ve tried to reproduce your situation and these are my logs

[02.13.2024_18-25-13] Postfix Hostname: cl.cyberpanel.net. Server IP 95.217.248.69. rDNS: cl.cyberpanel.net, rDNS check 1
Hostname is already set, the same hostname is also used with mail service and rDNS. Let see if valid SSL also exists for this hostname..,10
[02.13.2024_18-25-13] Hostname is already set, the same hostname is also used with mail service and rDNS. Let see if valid SSL also exists for this hostname..,10
It looks like your current hostname is already the mail server hostname and rDNS is also set and there is a valid SSL, nothing needed to do.
[02.13.2024_18-25-13] It looks like your current hostname is already the mail server hostname and rDNS is also set and there is a valid SSL, nothing needed to do.
[02.13.2024_18-25-15] sudo -u root systemctl restart postfix && systemctl restart dovecot && postmap -F hash:/etc/postfix/vmail_ssl.map

It does not update my existing SSL.

You can run on cli

/usr/local/CyberCP/bin/python /usr/local/CyberCP/plogical/IncScheduler.py Daily

Then run

cat /home/cyberpanel/error-logs.txt

then share logs of this log command.

[02.07.2024_18-00-05] SSL exists for mail.example.com and is not ready to renew, skipping…
[02.07.2024_18-00-05] Checking SSL for mail.exm.example.com.
[02.07.2024_18-00-05] SSL exists for mail.exm.example.com. Checking if SSL will expire in 15 days…
[02.07.2024_18-00-05] SSL exists for mail.exm.example.com and is not ready to renew, skipping…
[02.07.2024_18-00-05] Restarting mail services for them to see new SSL.
[02.07.2024_18-00-05] [Errno 2] No such file or directory: ‘postmap’: ‘postmap’. [ProcessUtilities.normalExecutioner.Base]
[02.07.2024_18-00-17] [Errno 2] No such file or directory: ‘/home/cyberpanel/git’. [IncScheduler.git:90]
[02.07.2024_18-00-20] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.07.2024_21-05-20] Expecting value: line 1 column 1 (char 0)
[02.07.2024_23-23-37] https://api.github.com/repos/usmannasir/cyberpanel/commits?sha=v2.3.5
[02.08.2024_18-00-16] [Errno 2] No such file or directory: ‘/home/cyberpanel/git’. [IncScheduler.git:90]
[02.08.2024_18-00-19] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.08.2024_20-35-51] https://api.github.com/repos/usmannasir/cyberpanel/commits?sha=v2.3.5
[02.09.2024_18-00-16] [Errno 2] No such file or directory: ‘/home/cyberpanel/git’. [IncScheduler.git:90]
[02.09.2024_18-00-19] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.10.2024_18-00-16] [Errno 2] No such file or directory: ‘/home/cyberpanel/git’. [IncScheduler.git:90]
[02.10.2024_18-00-16] [Errno 2] No such file or directory: ‘/home/cyberpanel/git’. [IncScheduler.git:90]
[02.10.2024_18-00-19] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.10.2024_18-00-19] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_18-00-16] [Errno 2] No such file or directory: ‘/home/cyberpanel/git’. [IncScheduler.git:90]
[02.11.2024_18-00-19] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_22-25-53] https://api.github.com/repos/usmannasir/cyberpanel/commits?sha=v2.3.5
[02.11.2024_22-34-27] https://api.github.com/repos/usmannasir/cyberpanel/commits?sha=v2.3.5
[02.11.2024_22-34-52] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_22-36-01] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_22-36-10] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_22-45-02] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_22-46-14] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_22-49-13] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_22-50-39] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_22-51-15] https://api.github.com/repos/usmannasir/cyberpanel/commits?sha=v2.3.5
[02.11.2024_22-58-46] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.11.2024_23-00-26] Covered domains: [‘exm.example.com’]
[02.11.2024_23-00-26] Status Code: Unknown for: http://www.exm.example.com/.well-known/acme-challenge/exm.example.com. Error: HTTPConnectionPool(host=‘www.exm.example.com’, port=80): Max retries exceeded with url: /.well-known/acme-challenge/exm.example.com (Caused by NewConnectionError(‘<urllib3.connection.HTTPConnection object at 0x7fcb71feeb38>: Failed to establish a new connection: [Errno -2] Name or service not known’,))
[02.11.2024_23-00-26] Status Code: Unkown for: http://exm.example.com/.well-known/acme-challenge/exm.example.com. Error: Exceeded 30 redirects.
[02.11.2024_23-00-29] /root/.acme.sh/acme.sh --issue -d exm.example.com -d www.exm.example.com --cert-file /etc/letsencrypt/live/exm.example.com/cert.pem --key-file /etc/letsencrypt/live/exm.example.com/privkey.pem --fullchain-file /etc/letsencrypt/live/exm.example.com/fullchain.pem -w /usr/local/lsws/Example/html -k ec-256 --force --server letsencrypt
[02.11.2024_23-00-38] Failed to obtain SSL for: exm.example.com and: www.exm.example.com
[02.11.2024_23-00-38] Trying to obtain SSL for: exm.example.com
[02.11.2024_23-00-38] /root/.acme.sh/acme.sh --issue -d exm.example.com --cert-file /etc/letsencrypt/live/exm.example.com/cert.pem --key-file /etc/letsencrypt/live/exm.example.com/privkey.pem --fullchain-file /etc/letsencrypt/live/exm.example.com/fullchain.pem -w /usr/local/lsws/Example/html -k ec-256 --force --server letsencrypt
[02.11.2024_23-00-44] Successfully obtained SSL for: exm.example.com
[02.11.2024_23-00-44] [Errno 111] Connection refused
[02.11.2024_23-16-50] https://api.github.com/repos/usmannasir/cyberpanel/commits?sha=v2.3.5
[02.12.2024_18-00-17] [Errno 2] No such file or directory: ‘/home/cyberpanel/git’. [IncScheduler.git:90]
[02.12.2024_18-00-20] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.13.2024_11-15-27] https://api.github.com/repos/usmannasir/cyberpanel/commits?sha=v2.3.5
[02.13.2024_11-21-40] https://api.github.com/repos/usmannasir/cyberpanel/commits?sha=v2.3.5
[02.13.2024_18-00-16] [Errno 2] No such file or directory: ‘/home/cyberpanel/git’. [IncScheduler.git:90]
[02.13.2024_18-00-19] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.13.2024_18-55-12] [Errno 2] No such file or directory: ‘/home/cyberpanel/git’. [IncScheduler.git:90]
[02.13.2024_18-55-15] Domain that you have provided is not configured as rDNS for your server IP. [404]

**host name musked

So I keep seeing this error, can you open a ticket here with server logins: https://platform.cyberpersons.com/

then mention ticket id here.

To create ticket in support departments you can purchase CyberPanel Cloud Support plans.

I cant create ticket. Is it Paid? My all server have same issue.

I have skipped Additional Features “Skip rDNS/PTR Check (If you don’t want to use email service on this server)” then logs showing like…

[02.14.2024_10-07-21] Domain that you have provided is not configured as rDNS for your server IP. [404]
[02.14.2024_10-07-31] Hostname is already set, the same hostname is also used with mail service and rDNS. Let see if valid SSL also exists for this hostname…,10
[02.14.2024_10-07-31] It looks like your current hostname is already the mail server hostname and rDNS is also set and there is a valid SSL, nothing needed to do.
[02.14.2024_10-07-53] https://api.github.com/repos/usmannasir/cyberpanel/commits?sha=v2.3.5

Create ticket in any department if it is a bug, we don’t charge anything.

@usmannasir i face the same issues with rdns…
The rdns is setup correctly, and i also check with ‘dig -x’, but in the setup page from cypberpanel it always return 404( Domain that you have provided is not configured as rDNS for your server IP. [404] )

What should i do?

Panel Version: 2.3.5 (c97df70156acd8d6a005d7b10e9f6a0aaf900c23)

Thank you!

I am still having the same problem. But I have adopted some trick to solve it. Completed setup by skipping Mailserver. Later I did separate mailserver ssl issue. But the problem is that every time I reboot the server, the mailserver ssl is lost. As a result, every time after rebooting the server, doing a separate postfix restart (systemctl restart postfix), then everything works fine.

Also noticed after 2.3.5 version upgrade no error log is coming in admin profile default mail.

Well if the problem is only at reboot, will not be much trouble, but does the ssl autorenew itself?

For example, i do as you said, and skip mailserver then issuse ssl, the ssl have 3 month lifetime, does it after 3rd month get renewed? or i have to issuse again ssl?

Thanks for tip, but i’m already use Cypberpanel for like 2 years, and everything went smooth till last update.

Good question. I also faced this problem on upgrade to 2.3.5 version. Since it hasn’t been 3 months, I can’t tell you exactly. But I hope that connected ssl will autorenew normally.

Hi,
Me too, I’m facing the same issue with my server. I was able to upgrade some VPS before without any issue, but this time I got that rDNS error even thought I’m sure it is setup correctly, the only difference here it is a dedicated server not a VPS (I use Hetzner). Could you please fix this?

Update (Resolved):
I was able to fix the issue by editing the /etc/hosts file and adding the correct hostname to it. This was on a dedicated server running CentOS 7.
I observed that after running the command:
ping example.com
I noticed that the hostname was incorrect because the output appeared like this:

PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.026 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=2 ttl=64 time=0.023 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=3 ttl=64 time=0.024 ms

The problem was with the localhost.localdomain section (which may vary in your situation), but this is supposed to be the hostname, so I modified the ipv4 part like this (example.com should be substituted with your hostname):

# IPv4
127.0.0.1 example.com example
127.0.0.1 localhost.localdomain localhost example.com
127.0.0.1 localhost4.localdomain4 localhost4 example.com

After saving the hosts file and restarting the server, I used the ping command to verify everything was working correctly. When I reran the setup wizard, it completed successfully!
I hope this can help you.

1 Like

Did you added “127.0.0.1 example.com example” above or edit an existing line?
Because I tried by modifying the existing line. Then the server became very slow and was about to shut down. There is no section called IPv4 on VPS server in this file.

Can you copy & paste the content of your /etc/hosts file? Just to clarify: My server is an old one using CentOS 7, from Hetzner, maybe things are different for you. I think I should mention the OS in my previous post.

No, edited with my host name. I have tried before your post. My OS is AlmaLinux 8.

I’ve read @hadi060 advices and modify the /etc/hosts
so the line will be in the following order
127.0.0.1 example.com
127.0.0.1 localhost localhost.local
::1 example.com
::1 localhost localhost.local

after i do those modification i tried to rerun setup wizard and everything works.

My server is running ubuntu 20.04 and is hosted at Hetzner

I didn’t try Almalinux 8, but it should be similar to CentOS 7, maybe the difference comes from the server provider.
Try to look in your hosts file for the ipv4 section and make the change I posted. Before that, you can check using ping command to see if everything is ok as described in my post. If you can post the output of ping your-domain.com, it will be helpful to understand better your issue.

Glade that my post helped you! Hope the same for others.
Good luck!

1 Like

I think both of you didn’t reboot the server after setting the hostname. Reboot the server and see if mail can be sent from the mail server to Gmail.

note: I followed your steps. In my case 127.0.0.1 didn’t work. I added a new line above 0.0.0.0 host.example.com with server ip instead of 127.0.0.1. ssl issues are done. But after rebooting the server the mail could not be sent.

I’ve reboot the sever and then send mail from server to gmail, yahoo and outlook.
Each mail arrived without any issue, i’ve also check if the mail pass tests, and yes it pass all tests.

Maybe it is because of OS. Have you used a subdomain?