• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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: 21
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?
 
After I changed the application mode to development, I saw this
 

Attachments

  • Screenshot (10).png
    Screenshot (10).png
    153.4 KB · Views: 10
  • Screenshot (9).png
    Screenshot (9).png
    98 KB · Views: 10
Back
Top