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.
Both of your URLs are working fine from here. Do you still experience this issue?
I experiment the same issue and my .htaccess file wasn’t modified… can this message mean anything else ?
I just had the same error message on ALL of my subdomains, none of which have been updated in a while (and the .htaccess themselves had not been touched in years.)
I found this was caused by this line being present on any .htaccess file:
Options All -Indexes
Simply removing the line fixed the error for me, but replacing it with this version also works :
Options -Indexes
(Same deal with +Indexes)
Thanks for sharing that finding!
Server updates were performed in the last few days, and we’ve already seem that the configuration has been tightened by server side includes no longer being supported.
And the fact is that using All needs more .htaccess permissions than using -Indexes (because it affects all options, not just indexes).
So the fix is simple: if you use Options All anywhere in the .htaccess file, just remove that All keyword. Or even remove the line outright, because indexes are disabled on our hosting by default anyway unless explicitly enabled. But you can still keep it for portability of course.
I don’t have this option in my .htaccess file.
Are there other commands to modify ?
P.S. : Everything is ok today… It seems that something was done that made it work again…
I have pretty much the same problem.
I realised that my problem is not with
Options +Indexes
IndexOptions +FancyIndexing
but, despite the message, with
SetEnv expose_php = On
Question: at this point do I have to change almost all my php files?
Not sure what are you trying to do with this line. You don’t need to “expose php” to run PHP files. That line is not even a valid line from the beginning, expose_php is a php directive and does not have anything to do with SetEnv…
So yeah just remove that line if it is the culprit. It’s not doing anything useful back then either.
Same issue here, and I can confirm the cause on my side: any Options directive in a .htaccess file now seems to trigger this error page, even if the file hasn’t been touched in a long time.
In my case (Symfony project), the default .htaccess in the public/ folder contains Options -MultiViews and Options +SymLinksIfOwnerMatch. Commenting out both lines fixed it immediately, and URL rewriting still works fine without them.
Tip: if your root .htaccess redirects requests to a subfolder, don’t forget to check the .htaccess inside that subfolder too, since that’s where the problem was hiding for me.
My site jubiladosinsurgentes.org ca´t be accessed I get the message 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.
Additionally I can´t connect to the ftp server
As general information: the server configuration seems to have been hardened and the number of options you can configure with .htaccess files has been restricted. I don’t see any reason to suggest that this would cause a functional change for most websites. However, any .htaccess file that tries to set an option that it’s not allowed to set will trigger the “Something Went Wrong!” error.
Potentially. Other commands may stop working because of hardening too. But even just figuring out why the All option didn’t work was not obvious, so I cannot give you an exhaustive list of everything that no longer works.
If you know which exact directive triggered the error, I’d be happy to check it for you. If you’re not sure which directive is triggering the error, I suggest to try removing chunks from the .htaccess configuration to see if you can narrow it down.
The Options -Indexes and Options +Indexes still work because they are explicitly allowed.
But the MultiViews and SymLinksIfOwnerMatch options are now blocked, which is what causes the crash. Both options are also dead code (MultiViews should be disabled by default, and SymLinksIfOwnerMatch is moot because there is no way to create symlinks). So you can safely remove them.
But I do understand that having to change stock Symfony code is undesirable.
Going by the rest of the topic, that’s pretty likely.
Although I wouldn’t say it’s a code error as much as it probably uses an option that’s now disabled.
That’s unrelated to this issue, and that sentence alone is too vague to investigate. Please read the relevant KB article, and if the contents in it don’t solve your issue, then please open a new topic and describe the issue there. Help, I cannot connect to FTP