• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue We're sorry, but something went wrong.

Bqiami

New Pleskian
Hi everybody,

my website suddenly shows me We're sorry, but something went wrong error, i have checked most of the configuration files but couldn't find anything
suspicious.
I really appreciate any kind of help!
 

Attachments

  • phusion passenger(R).png
    phusion passenger(R).png
    47.8 KB · Views: 19
This is normally due to an access restriction in a .htaccess file or wrong directory permissions of the document root directory of the website (which needs to be group psaserv and mod 0750) or subdirectories (which ought to be group psacln and have read writes for all).
 
I did not mean the permission of the .htaccess file, I was referring to an instruction given to the web server in an .htaccess file. There can also be more than one .htaccess files, e.g. on the web space account level, the domain document root level and in any descending directories along that tree. If you pay close attention to what exactly is being blocked, which file or directory as that is mentioned in the log files, you'll probably find the reason for that restriction.
 
My node.js app was working before but suddenly after an upgrade, I saw the same error on my website.

Please what can I do?
 
Thank you. Could you please confirm if the application startup file in present in the document root? Also, can you double-check the passenger.log?
 
Back
Top