Account stuck in processing
Affected: Hosting Platform
Other Information
Hello Infinity Admin,
I’m a mid-level web and application developer. While making changes to my stylesheet, I noticed that the website was not reflecting any of the updates. To rule out a path or file-reference issue, I temporarily deleted the entire .css file, but the website continued displaying the previous styling.
This suggests that the site may be serving a cached version of the stylesheet or that the hosting platform has not processed the latest file changes.
Account status: Stuck on “Processing”
Affected service: Hosting Platform
Please investigate and advise on how to resolve this issue.
Welcome to the InfinityFree community forum! Good to have you here.
Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
Solving an issue is a joint effort. Try the suggestions you get and report back what happened.
We don’t cache static files on the server. After all, cache is just files on disk, so there is no benefit in caching static files: it’s just reading a file from the server, just in a different location, but now we’re storing the same data multiple times and providing a worse experience for the website owner in the process. So that would be a bad idea.
The issue of CSS files not updating is usually caused by one of a few things:
Browser cache: we enforce strong browser cache by default for static assets, meaning we instruct your browser to cache static files, like CSS files. To rule out this option, you can try opening your website in Incognito Mode in your browser, which bypasses all caches.
CDN cache: if you’re using a CDN like Cloudflare, they also cache your static files. You can clear Cloudflare’s cache or enable Development Mode to temporarily disable caching. Not an issue for you since you’re not using Cloudflare (that’s not possible with a free subdomain), but listing it here for the sake of completeness.
Files uploaded to the wrong location: a common issue when people have copied their website from one domain to another. Pay close attention to which folder on your account your domain name is linked to, and make sure to upload your website files to that folder. Accidentally uploading the files to the wrong folder (like the main htdocs folder when you should be uploading it to a domain specific folder) is a common mistake.
Don’t Insult my craftsman ship my good sir, I might be a noob, but I know what am talking about
Hello,
Thank you for the clarification. I understand that the “Account status: Stuck on Processing” notice only relates to account actions such as suspension, deactivation, unsuspension, or reactivation, and is therefore unrelated to the stylesheet issue.
I also understand the caching explanation. However, I tested the issue by deleting the entire .css file, and the website continued displaying the previous styling. This occurred even after checking from another browser/device, which makes ordinary browser caching unlikely. I also do not have a caching plugin enabled.
Could you please confirm whether any server-side caching, CDN caching, or other platform-level caching may be serving the old stylesheet? If not, kindly advise whether there is another hosting-related explanation or a recommended cache purge method.
I appreciate your assistance—and I promise I’m not trying to make the server remember CSS that no longer exists; I’m simply trying to understand why it does
I did read it—and I agree that volunteers cannot see my account or website.
That is precisely why I described the observable behavior rather than claiming to have identified the root cause.
The observation was specific: after deleting the .css file, the site continued rendering the old styling, even when checked from another browser/device. The conclusion was not “the server is definitely broken”; it was that ordinary browser caching was unlikely and that further investigation was needed.
In fact, InfinityFree’s own forum guidance acknowledges that static files such as CSS may be cached, even though there is no general server-side page cache. So the issue is not necessarily a “theory”—it is a reproducible symptom that can be tested by opening the direct stylesheet URL, checking the response headers, or appending a version query such as style.css?v=2.
I’m happy to provide the URL, exact error message, screenshots, and reproduction steps. I only ask that we distinguish between “the cause has not yet been proven” and “the symptom is imaginary.” CSS may be cached, but thankfully my reading comprehension is not.
, I might be a noob, but I know what am talking about
