ClosedServer Initial Configurations rDNS Dramas

Hi all,

I’ve installed a new CyberPanel installation on Ubuntu 22.04, and I’m having troubles at the initial configurations onboarding page - it keeps throwing this error:

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

Digging the IP and domain from within the server itself shows the IP → Domain and Domain → IP, I also have a PTR record set, and the dedi.domain.me is correctly setup, as per rDNS checkup tools.

I have also changed public DNS nameservers to 1.1.1.1 and also 8.8.8.8, to no avail.

I have deleted the domain from CyberPanel → Websites → Delete Website.

I have ran the onboarding script many times, and to no avail, haven’t been able to get it to work.

Confirming via nslookup <ip> confirms that the IP is pointing to the correct domain.

Confirming the Reverse DNS entry on my dedicated server is set to the correct domain.

https://dnschecker.org/ - Shows the correct server IP address.

After all this, it still says that the domain I’ve provided is not configured as rDNS, when it indeed has.

CU1Bhj1378×582 27.5 KB

QVyPaz950×1005 35.1 KB

I’ve ensured there are no typo’s, which leads me to believe there may be some issue with CyberPanel, or perhaps there’s a cache somewhere in CyberPanel which is causing this rDNS issue. I’ve rebooted the server multiple times, and modified my netplan to ensure DNS is serving from Google, then tried with CF, and same issue.

Here’s some info from the error-logs.txt:

[04.10.2024_17-31-08] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.10.2024_17-36-30] [CheckIfSSLNeedsToBeIssued] We will issue SSL for domain.me
[04.10.2024_17-36-30] Status Code: 200 for: http://www.domain.me/.well-known/acme-challenge/domain.me
[04.10.2024_17-36-31] Status Code: 200 for: http://domain.me/.well-known/acme-challenge/domain.me
[04.10.2024_17-36-32] /root/.acme.sh/acme.sh --issue -d domain.me -d www.domain.me --cert-file /etc/letsencrypt/live/domain.me/cert.pem --key-file /etc/letsencrypt/live/domain.me/privkey.pem --fullchain-file /etc/letsencrypt/live/domain.me/fullchain.pem -w /usr/local/lsws/Example/html -k ec-256 --force --server letsencrypt
[04.10.2024_17-36-40] Failed to obtain SSL for: domain.me and: www.domain.me
[04.10.2024_17-36-40] Trying to obtain SSL for: domain.me
[04.10.2024_17-36-40] /root/.acme.sh/acme.sh --issue -d domain.me --cert-file /etc/letsencrypt/live/domain.me/cert.pem --key-file /etc/letsencrypt/live/domain.me/privkey.pem --fullchain-file /etc/letsencrypt/live/domain.me/fullchain.pem -w /usr/local/lsws/Example/html -k ec-256 --force --server letsencrypt
[04.10.2024_17-36-46] Failed to obtain SSL, issuing self-signed SSL for: domain.me
[04.10.2024_17-36-49] Self signed SSL issued for domain.me.
[04.10.2024_17-36-59] [CheckIfSSLNeedsToBeIssued] We will issue SSL for mail.domain.me
[04.10.2024_17-36-59] Status Code: Unknown for: http://www.mail.domain.me/.well-known/acme-challenge/mail.domain.me. Error: HTTPConnectionPool(host='www.mail.domain.me', port=80): Max retries exceeded with url: /.well-known/acme-challenge/mail.domain.me (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f09eff52f20>: Failed to establish a new connection: [Errno -2] Name or service not known'))
[04.10.2024_17-37-00] Status Code: 200 for: http://mail.domain.me/.well-known/acme-challenge/mail.domain.me
[04.10.2024_17-37-01] /root/.acme.sh/acme.sh --issue -d mail.domain.me -d www.mail.domain.me --cert-file /etc/letsencrypt/live/mail.domain.me/cert.pem --key-file /etc/letsencrypt/live/mail.domain.me/privkey.pem --fullchain-file /etc/letsencrypt/live/mail.domain.me/fullchain.pem -w /usr/local/lsws/Example/html -k ec-256 --force --server letsencrypt
[04.10.2024_17-37-09] Failed to obtain SSL for: mail.domain.me and: www.mail.domain.me
[04.10.2024_17-37-09] Trying to obtain SSL for: mail.domain.me
[04.10.2024_17-37-09] /root/.acme.sh/acme.sh --issue -d mail.domain.me --cert-file /etc/letsencrypt/live/mail.domain.me/cert.pem --key-file /etc/letsencrypt/live/mail.domain.me/privkey.pem --fullchain-file /etc/letsencrypt/live/mail.domain.me/fullchain.pem -w /usr/local/lsws/Example/html -k ec-256 --force --server letsencrypt
[04.10.2024_17-37-15] Failed to obtain SSL, issuing self-signed SSL for: mail.domain.me
[04.10.2024_17-37-19] Websites matching query does not exist. [installSSLForDomain:72]
[04.10.2024_17-37-19] Self signed SSL issued for mail.domain.me.
[04.10.2024_17-38-05] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.10.2024_17-45-13] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.10.2024_17-45-59] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.10.2024_17-47-11] (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '.me' at line 1")[createDatabase]
[04.10.2024_17-47-11] 0
[04.10.2024_17-48-39] Expecting value: line 1 column 1 (char 0)
[04.10.2024_17-50-39] Expecting value: line 1 column 1 (char 0)
[04.10.2024_18-01-01] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.10.2024_18-06-41] Config path: /etc/apache2/sites-enabled/domain.me.conf
[04.10.2024_18-15-23] Config path: /etc/apache2/sites-enabled/domain.me.conf
[04.10.2024_18-21-58] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.10.2024_22-00-01] Running SSL Renew Utility
[04.10.2024_22-00-01] Cannot resolve keyword 'status' into field. Choices are: BackupLock, admin, adminEmail, admin_id, aliasdomains, backups, backupsv2, childdomains, config, containerlimits, databases, dockersites, domain, domains, emaillists, externalApp, gitlogs, id, incjob, normalbackupsites, package, package_id, phpSelection, ssl, state, trash, users, wpdeployments, wpsites. Renew.SSLObtainer
[04.10.2024_22-00-03] [Errno 2] No such file or directory: '/home/cyberpanel/git'. [IncScheduler.git:90]
[04.10.2024_22-00-06] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_02-08-50] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_02-14-22] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_02-15-02] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_02-17-31] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_02-29-49] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_02-37-31] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_02-42-54] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_03-00-56] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_03-10-36] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_03-29-34] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_03-36-41] Creating website result....{'status': 1, 'createWebSiteStatus': 1, 'error_message': 'None', 'tempStatusPath': '/home/cyberpanel/1082', 'LinuxUser': 'dedih4014'}
[04.11.2024_03-36-44] Covered domains: ['dedi.domain.me']
[04.11.2024_03-36-44] Status Code: Unknown for: http://www.dedi.domain.me/.well-known/acme-challenge/dedi.domain.me. Error: HTTPConnectionPool(host='www.dedi.domain.me', port=80): Max retries exceeded with url: /.well-known/acme-challenge/dedi.domain.me (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f556a991600>: Failed to establish a new connection: [Errno -2] Name or service not known'))
[04.11.2024_03-36-44] Status Code: 200 for: http://dedi.domain.me/.well-known/acme-challenge/dedi.domain.me
[04.11.2024_03-36-45] /root/.acme.sh/acme.sh --issue -d dedi.domain.me -d www.dedi.domain.me --cert-file /etc/letsencrypt/live/dedi.domain.me/cert.pem --key-file /etc/letsencrypt/live/dedi.domain.me/privkey.pem --fullchain-file /etc/letsencrypt/live/dedi.domain.me/fullchain.pem -w /usr/local/lsws/Example/html -k ec-256 --force --server letsencrypt
[04.11.2024_03-36-52] Failed to obtain SSL for: dedi.domain.me and: www.dedi.domain.me
[04.11.2024_03-36-52] Trying to obtain SSL for: dedi.domain.me
[04.11.2024_03-36-52] /root/.acme.sh/acme.sh --issue -d dedi.domain.me --cert-file /etc/letsencrypt/live/dedi.domain.me/cert.pem --key-file /etc/letsencrypt/live/dedi.domain.me/privkey.pem --fullchain-file /etc/letsencrypt/live/dedi.domain.me/fullchain.pem -w /usr/local/lsws/Example/html -k ec-256 --force --server letsencrypt
[04.11.2024_03-36-58] Successfully obtained SSL for: dedi.domain.me
[04.11.2024_03-37-03] Domain that you have provided is not configured as rDNS for your server IP. [404]
[04.11.2024_03-51-48] Domain that you have provided is not configured as rDNS for your server IP. [404]

I have a similar rDNS problem, cyberpanel is complaining about rDNS not beeing properly configured but im pretty sure it is.

I’m following this topic to watch out for solutions.

Sorry to hear.
Hopefully this can help you out. I fixed the issue.

After extensive investigations, it appears my particular issue may have been due to the hosts file. I am not sure entirely why this has caused any issues, as it’s not explained in the CyberPanel onboarding page;

https://cyberpanel.net/KnowledgeBase/home/onboarding-and-initial-cyberpanel-configurations

From what I gathered, I was able to resolve my issue by editing the /etc/hosts file.

Here’s my hosts file:

127.0.0.1 dedi.website.com website-dedi
127.0.0.1 localhost.localdomain localhost dedi.website.com
14x.xxx.xxx.x44 dedi.website.com
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
2a01:4f8:272:280a::2 website-dedi

I’ll explain:

dedi.website.com is the sub-domain I’ve allocated to this server.
website-dedi is the hostname my server is setup on (refer to /etc/hostname)
14x.xxx.xxx.x44 is the IP address of my dedicated server

Let me know how you go, @computerman - if an admin could explain why this is an issue, that’d be great. Perhaps you can also add this to the Onboarding and Initial CyberPanel Configurations website.

Thanks for this find, I’ve update the original doc and also added link to this thread.