This server could not prove that it is beta.thetechguy.cf; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.
You login to CloudFlare dashboard.
Then, add your subdomain on DNS menu. Usually using A record & same IP with your main domain.
Don’t forget to switch on its proxy on your subdomain record (cloud orange icon).
This is the example:
hi @Kamdroid,
It involves changing your nameservers. If i change the nameservers to cloudflare’s than infinityfree don’t have control over my domain anymore.
So how do i make it that cloudflare is on my subdomain but im still using infinity free’s nameservers?
If you already add your domain from addon domain menu on hosting panel, then it’s no problem.
InfinityFree still have control over your domain eventhough you use CloudFlare nameserver.
Just pointing your domain/subdomain to your hosting IP.
How to find your hosting IP, see this article: https://infinityfree.net/support/find-your-ip/
If you still want to use InfinityFree nameserver, then you can’t use HTTPS feature without warning message (not secure).
To force your visitors to the HTTPS version of your website now go to your Cloudflare dashboard, then click on your domain, on “SSL/TLS” click on “Edge Certificates” and turn on “Always Use HTTPS”, and after that go on “DNS” and enable all grey clouds.
I checked, and the record for your domain has the grey cloud. Enable it.
I also suggest to add a CNAME record with name www and value @, so it would be also accessible with www. before the domain.
A - thetechguy.cf - (keep its IP) - Proxied
CNAME - www - thetechguy.cf - Proxied
A - beta - (same IP with main domain) - Proxied
MX - thetechguy.cf - mx.epizy.com - 0 - DNS only
ftp & mx name keep like that (A records with grey cloud). Or you can remove them if unused. beta & * CNAME record can be removed safely. Maybe you must remove beta CNAME first, before add beta A record.
@adisp007, I think the record for mx points to the same IP of the webmail, which I think is not correct, and ftp should point to 185.27.134.11 instead of the IP there was before.
@thetechguy, so you should remove the mx A record, put a MX record for your domain that points to mx.epizy.com with priority 10, not 0, and correct the ftp record value with the IP address 185.27.134.11 instead of the one there was before.