My site is hosted on IP 185.27.134.24. Since at least 15:12 UTC today (Sept 21), it’s showing the same failure pattern as the incidents posted today for .119, .120, .135, and .136 — but .24 isn’t listed on the status page.
Account details in InfinityFree control panel look normal — SSL certificate shows correctly installed (Cloudflare Origin CA cert, issued, not expired), so this doesn’t appear to be a config issue on my end.
Could someone check server 185.27.134.24? Thanks.
Other Information
Symptoms:
Visiting the site directly (both the free subdomain and the custom domain) returns a generic static “DNS Resolution Error / domain not added to hosting account” fallback page, served by plain nginx, regardless of which hostname is requested.
For comparison, a working InfinityFree account I also host (different server, 185.27.134.97) correctly returns Server: openresty — the normal routing layer — so this looks like the account-routing layer is down specifically on .24.
Because the origin can’t route/match the right certificate, Cloudflare (in Full-strict SSL mode) fails the handshake and returns error 525 to visitors.
My site has been down for many hours now, is IF actively working on resolving my issue? I realize that I’m not the only one experiencing issues, the forum is spicy, but I’d like to know what is being done, please.
Infinity free is limited in what they can do. Most the time when there’s a housing problem is IFastNet who are actually working on it, as they prove the back end infrastructure.
If your sure is hosted on one of the affected ip’s from the status page you can be certain it’s being looked into
The .24 IP is not a website IP, it’s a fixed IP address that only displays that DNS Resolution Error page. It’s also not listed as the Website IP of your account in the members area.
If I had to guess, I’d say you used Cloudflare’s record scanning tool and didn’t check the output. Cloudflare imported the placeholder IP because the DNS record wasn’t fully set up on our end yet, and now your domain is pointing to the placeholder IP instead of to your hosting account.
To fix this, please update your DNS records at Cloudflare to point to the Website IP of your account as shown in the members area.
Thanks for the update. I’ve confirmed a few things on my end:
DNS is correct - my Cloudflare A record for jrjdigitaldesigns.com already points to the correct Website IP shown in my account (185.27.134.137).
My SSL certificate was properly installed yesterday - I checked at several points throughout the day while the site was already down. Today, before I touched anything, the control panel showed “No SSL certificate is installed.”
I reinstalled it as suggested. The control panel now shows “SSL certificate is installed” (CloudFlare Inc, expires 2041-09-15).
The site is still down. Testing directly against my server (185.27.134.137), it’s not actually serving that certificate - it’s presenting a generic, unrelated self-signed certificate instead, and returns an empty response after that. Cloudflare reports this as error 526 (invalid SSL certificate at the origin).
This matches your open incident (“SSL Certificates on custom domains not taking effect”) exactly - it looks like something on your end may have reset or removed the certificate install between yesterday and today, and my server hasn’t received the fix yet even though the account now shows the certificate as reinstalled. Is there anything else I can do on my end, or does this just need to wait for the rollout to reach my specific server?