"There has been a critical error on this website."

Hosting Support
1

Website URL

https://nexusvisual.ro/

Error Message

There has been a critical error on this website.
Learn more about troubleshooting WordPress.

Other Information

I had this error for more than a week now, on both my main domain and on the subdomain (https://cookbook.nexusvisual.ro/).
However, the subdomain works now (without intervention from my part), but the main still doesn’t. Any suggestions?

2

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.
3

Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.

Could you turn on WordPress debug mode and post the error messages it shows? The “critical error” page only says that PHP crashed. The debug output names the plugin, theme or file that caused it, and that’s what anyone would need to go on.

I found an article that covers how to do this. The steps are:

  1. Open wp-config.php in the file manager or over FTP.
  2. In htdocs, change WP_DEBUG from false to true.
  3. Reload the site.

The article is about a failed plugin or theme install, which may not be what happened here. The debug steps and the way to read the output apply to any critical error, though.

The article says to look for wp-content/plugins/ or wp-content/themes/ in the messages. The folder name right after that is usually the broken plugin or theme. If one shows up, you can delete that plugin’s folder or switch themes by hand, and the article explains how. Set WP_DEBUG back to false afterwards, because it shouldn’t stay on for a live site.

It would also help to know whether anything changed on the main site around when the error started, such as an update, a new plugin or a theme change. That subdomain recovering by itself is odd, so it could also be useful to know if it runs a different WordPress install.