Removing cprapid things completely.
Answered
Some how my installations always start with the cprapid things, i am currently checking why is that.
In the meantime i am removing it by doing the following steps.
1.- Change the hostname to example.domain.com
2.- Terminal - nano /etc/hosts
In the last line i delete everything exept example.domain.com so it is like this
********
127.0.0.1 localhost
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
169.254.169.254 metadata.google.internal metadata
10.2.0.2 server.example.com <<<<----- THIS LINE
********
3.- SSL/TLS / ---> SSL Storage Manager
Here i delete every certificate.
4.- Terminal
/usr/local/cpanel/bin/checkallsslcerts
So certificates are renewed.
But somehow i still get the cprapid things, its very annoying, could somebody tell me if my steps will compromise my server, and also, what i am missing to completly remove this?
Thank you in advance.
-
cprapid.com is sort of the "default" domain used by new cPanel installations to allow for automatic SSL provisioning on the server hostname ( https://support.cpanel.net/hc/en-us/articles/360052632174-What-is-the-cprapid-com-DNS-zone-I-see-on-my-server and https://docs.cpanel.net/knowledge-base/dns/automatically-issued-hostnames/ ). Once you've changed the hostname in WHM a restart should ensure it takes effect server wide (as long as the hostname you have entered resolves to that server - if it doesn't, or you've recently changed it and it is still propagating - then the server may "fallback" to the cprapid domain)
If you remove all the other listings in /etc/hosts you will find your server will take more time resolving certain "local" things (such as when it is checking MySQL/MariaSQL connections, Spamassassin connections from Exim and many more). It's advisable to leave /etc/hosts "as provisioned" with perhaps only adding additional hostnames/aliases if needed. Removing the google.internal/metadata one may also mean some Google Cloud related things stop working over time (as the DNS entries time out)
When you are running checkallsslcerts it is probably recreating the cprapid entry to ensure your server can be accessed via HTTPS.
1 -
Make sure your hostname (example: server.example.com) points to the public IP address of your gcloud instance.
Kodeslogic Web Solutions - cPanel Certified Partner
Submit a ticket ★ Server Management Support ★ Outsourced Web Hosting Support
Skype - live:kodeslogic1 -
Hi, thank you both for the answers....... Well the thing is my registar only admit two stuffs, one is the NS address and the other is the IP. Like this: ns1.example.com 1.2.3.4
Nothing else, so.. server.domain.com will never resolve at first and i am stuck with the cprapid thing.
I am going crazy here trying to remove this thing.0 -
Case 1.) If you are using the domain provider nameservers
Use the same interface were you create NS address to create the hostname. Like this: server.example.com 1.2.3.4Case 2.) If you are using your own nameservers (private nameserver like: ns1.example.com and ns2.example.com) then add hostname A record at your DNS server (This may be your own server where you manage DNS records for your domain)
1 -
Thank you guys for all the time to answer my question.. Well i have news for what i was doing wrong and always got the cprapid thing in my server.
I was pointing my registar directly to the IP of my server. I found the correct way is to point the registar to a DNS service first, in this case Cloud DNS and then to the IP of my machine....
in the Cloud DNS i created an A record to point "server.domain.com" which is the hostname... and now i have a clean fresh good cPanel installation, thanks!!0 -
I'm glad you were able to get the DNS properly configured to get things working!
0
Please sign in to leave a comment.
Comments
6 comments