do you think we should lock this thread ?
and possibly split this after the guide into its own thread to keep the guide clean ?
While locking this Topic/Thread would help with keeping the Topic/Thread clean, if in the future an edit needs to be made [If somebody spots that an edit is needed] itâs better to keep the Topic/Thread open then clutter the Topics section with (a) Topic(s) that ask that an edit be made.
This is a community guide, so anyone that has been on the forum long enough can edit it. We generally keep community guide topics open to allow users to ask related questions, ask for more details on a step, etc.
If a users posts an entirely new question and it creates a kinda-off-topic thread within a thread, we merge it away to a new topic.
If these posts begin to get too messy, the auto-close rules will be put in place, but as of now leaving them open seems to be working pretty well.
thanks ![]()
A post was split to a new topic: Domain Not Working
Thank you for this, very helpful. The recent threads about Cloudflare made me curious to try. Like the guide says, CF seems to do the records automatically. I just need to re-add the subdomains. Iâm also surprised I did not need to do the SSL part. Maybe times has changed? It is still issued by Google but the date has changed. Thanks for your hard work.
Can this guide remove/disable ?i=1 on free hosting? I have a custom domain name on Cloudflare.
It no longer can, unfortunately.
Why is that no longer possible now?
Well, loophole has been closed
it was a historical reason that the security system simply not working with cloudflare IPs, and it took ifastnet a few years to finally fix it, and both free subdomain and custom domain users are treated equally ![]()
Our own browser validation system initially did not work with Cloudflare, and so traffic from Cloudflare was granted an exception under the assumption that Cloudlflare provides adequate protection.
But it turns out that Cloudflareâs protection is not good enough and many attacks were punching right through. So the browser validation system was fixed so it could also work with Cloudflare.
So now we have effective protection for all websites.
This can be shortened to âClick on the âFullâ settingâ nowadays, eh?
âuse Cloudflareâs Origin CA,â which doesnât work on here because vpanel only checks for Common Name, not Subject Alt Name for (i bet) weird reasons ![]()
If a subjectAltName extension of type dNSName is present, that MUST
be used as the identity. Otherwise, the (most specific) Common Name
field in the Subject field of the certificate MUST be used. Although
the use of the Common Name is existing practice, it is deprecated and
Certification Authorities are encouraged to use the dNSName instead.
Update: Full(strict) mode is now supported on free hosting.
It is now possible to use origin cert from CloudFlare
is there anyway I can use my own domain on infinity free bc my domain is registered on cloudflare
If you can set up Cname records, you can use the CName validation to add an account
