Something Went Wrong!
Our apologies, but the website has encountered an error and cannot display this page at the moment.
The issue is likely due to a code error within the .htaccess file, which controls important server configurations. This error is not related to any PHP files or other website code.
I’m not pasting entire error it showed me when i opened the page, as it take huge space here, error is about .htaccess file
Other Information
Last modified code was in Feb 2026, and it worked fine i use it generally, no issues, for some reason i couldn’t able to use it or open it for past a month or something, so i can’t predict when did this error started occurring, is that may be after new PHP version upgrade or not, i’m not sure but, i wrote .htaccess code intentionally to block direct user paths, and want to make as much as possible secure way, and it wasn’t been a problem before too.
But i got new errors now, before this error wasn’t showed up to me, i have set application in a way to work for our hosting methods only and secure way, but i didn’t see any new policy rules in our announcements now i couldn’t able to login into my application. due to content security policy it getting internal error, and my auth file couldn’t able to load. Please if any rules added into our hosting systems try to mention in new announcements so developers can able to work on it.
The free hosting changes are made by iFastNet, who manage the free hosting platform, and they don’t publish announcements regarding their changes. The announcements we write are based on our observations, which are triggered by user reports, so I cannot guarantee that they are exhaustive.
I know that several changes have been made to server configuration to improve security, and I think that the .htaccess options being restricted are part of that, based on my own analysis of the issues that people report. But I don’t have official confirmation that this has been done, let alone have
So, all in all, I’m just surprised by this as you are.
And knowing iFastNet, they might be too. Keeping everyone’s website running as well as possible is a top priority, and I suspect that they might not have anticipated that restricting unsupported .htaccess fields would break websites. I definitely wouldn’t have guess that tightening the .htaccess features would have this effect.
I completely agree that it would be better to have a clear announcement beforehand that explains what changes, when it changes and what you need to do. But that’s just not an option right now.
Yes, I knew that iFastNet always updates and changes everything, atleast if they would give a small announcement notice towards any security changes to you, you would be posting for information. They should be doing it at first place. I think now i have to completely try debug and re-change the application code, i used auth in my application something looks like api, but it wasn’t though that’s why it worked before, now i need to replace few files to work again. Thank you admin. It’s been so long I think almost 8, 9 years been using the Infinityfree and continues…
and continues…