Moving from Cloudflare and other services
A site can move without downtime. Protection starts as soon as the domain points to AegisX.
Before you move
Find your server address
You need the real address of your server, not the old protection service’s. Your hosting panel shows it.
Write down the old settings
Rules, redirects, exceptions and cache settings do not move by themselves. Note the ones you need to set them up again in the dashboard.
Lower the TTL
If your DNS is not at the old service, set the TTL to 300 seconds a day before. The switch then takes minutes.
Step by step
Add the site
Enter the domain and your server address. If the server speaks HTTPS, use https:// so traffic to the server is encrypted too.
Confirm the domain
Add the TXT record from the dashboard. The site starts working once it is checked; unconfirmed sites are removed after 3 days.
Let AegisX reach your server
If the server only accepts traffic from the old service, add the AegisX addresses. Keep the old ones for now.
Change the DNS
Point the domain and www to the record from the dashboard: a CNAME, or A records if your DNS does not allow a CNAME on the root domain. Remove other A, AAAA and CNAME records for those names.
Wait for the certificate
The SSL certificate is issued by itself on the first HTTPS visit after the switch. On the Business plan you can upload your own certificate beforehand.
Lock down the server
Once traffic goes through AegisX, remove the old service’s addresses. The dashboard has a ready script that lets only AegisX reach your server.
If the site was on Cloudflare
Your DNS can stay at Cloudflare
Turn off proxying (grey cloud, DNS only) for the site’s records and set the record from the AegisX dashboard. Or move the DNS to another provider.
Cloudflare Origin CA certificate
AegisX does not trust it, just like browsers. Put a regular certificate on the server, such as Let’s Encrypt, or turn off origin certificate checks in the site settings.
Visitor IP
AegisX sends it in X-Real-IP and X-Forwarded-For, not CF-Connecting-IP. If your site or nginx reads CF-Connecting-IP, switch them to X-Real-IP and trust it only from AegisX addresses.
Rules, Page Rules and Workers
They do not move by themselves. Recreate blocks and exceptions as rules in the dashboard; the HTTPS redirect is one switch. Workers code does not run on AegisX.
Authenticated Origin Pulls
AegisX has its own certificate for every site. Replace the Cloudflare certificate in your server settings with the AegisX root certificate from the dashboard and check the site name, as in the guides.
From other services
From DDoS-Guard, StormWall and other services the move is the same: the real server address, DNS to AegisX, then close the server to everyone but AegisX. If the domain was delegated to the old service by NS, first move the DNS zone to your own DNS provider.
We can help you move
Send us the domain and where it is now. We will tell you what to watch for in your case.