Add new Plugin error, site experiencing technical difficulties

Hello @ttran18

I’m happy to hear that your site is still functioning. Some common troubleshooting options you can follow these steps:

1. Check the inbox of the email address for your WordPress administrator account for a message: “Your Site is Experiencing a Technical Issue.” If you don’t see the message, check the spam/junk folder.
2. In the email text, find the link to the WordPress recovery mode sign in page.
3. Enter your WordPress admin username and password and then select Log In.
4. In the WordPress dashboard, at the top, there’s a notification about what went wrong.
   • If the error is caused by a plugin, you’ll see the following notification: One or more plugins failed to load properly. Then, from the left-side menu, select Plugins and deactivate the faulty plugin.
   • If the error is caused by the active theme, you’ll see the following notification: One or more themes failed to load properly. In this case, from the left-side menu, select Themes and activate a different theme.

If the above steps don’t resolve the issue, you can try the following:

1. Connect to your hosting with FTP.
2. In the wp-content folder, rename the plugins folder to plugins.renamed.
3. Visit your site in a private browsing mode. If it loads correctly, the issue is caused by one of your plugins. If the error persists, something else is causing it.
4. Rename the folder with plugins back to?plugins?and continue investigating the issue.
   • If it’s caused by plugins, start disabling individual plugins to figure out which one is causing the error.
   • If it’s not caused by plugins, skip to the “Switch to a default WordPress theme” section.

To switch to a default WordPress theme:

5. If you’re using the Chrome, Firefox, or Edge browsers, you can enable incognito or private browsing to check if your site is working properly.
6. If the issue is resolved, go back to the WordPress dashboard, and in the top-right corner, select Exit recovery mode.

Remember to always back up your site before performing any troubleshooting.

Additionally, it may be that your WordPress core version is out of date (we are currently on version 6.3) and that will be an update that I recommend.

Hi @jwilde4

I’m having a similar issue, getting the same message, but do not have access to the email you’re referencing. Is there a way to trigger a new issue alert to be sent? Also, how do I access the DNS records in the new version of 6.3? TIA!

Your WordPress core version should not change or have anything to do with your DNS records.

You update the WordPress core version from within the wp-admin dashboard on the update -> https://%%DOMAIN%%/wp-admin/update-core.php

If you are not receiving the email, manually setup the debug mode.

Hello @jwilde4,

Thank you for your kind support. I have tried the plugin activate/deactivate method, however I have not yet found any problem.

Regarding other methods, similar to @ndmohame, I have not received any emails from WordPress indicating the detailed error log, thus I could not enter the dashboard in recovery mode to check the error notifications as you mentioned.
I have also turned on debug mode but the same announcement: “The site is experiencing technical difficulties. Please check your site admin email inbox for instructions.” appears, and no other information for further reference.

As mentioned above, I could login as admin to dashboard normally via %%domain%%/wp-admin or %%domain%%/wp-login.php. All the functions and sections work normally when I navigate around the dashboard.

I can also access the Plugins page and see and deactivate/reactivate the installed plugins normally. Only when I press “Add new” to install a new plugin, it leads to the above mentioned announcement.
So I have to download the folder of that new plugin, and go to my host portal to manually upload it to plugins folder, then go back to Plugins page on dashboard and click “Activate”, for the plugin to run.

Alongside with @ndmohame, I have seen some others reported the same issue, with their page and dashboard running normally.
So would it be the problem related to the Plugins page that list all available plugins for browsing and installing, etc… provided and administrated by WordPress team, not from our own websites? If so then where do we find the contact info for support?

Regarding updating WordPress core version to 6.3, I have seen a number of plugins have not yet tested up to this version, so would it be safe to update to 6.3 as I fear there would be conflicts? I am currently not having a staging server to test the update.

Thank you once again for your kind help. Look forward to hearing from you soon.

Update:

I have checked the Site Health tool and found some more detailed indications:

• The REST API request failed due to an error.
  Error: [] cURL error 60: Peer’s Certificate issuer is not recognized.
• The loopback request to your site failed, this means features relying on them are not currently working as expected. Error: [] cURL error 60: Peer’s Certificate issuer is not recognized.

Some other errors and log:

• Could not confirm that the wp_version_check() filter is available.
• The optional module, imagick, is not installed, or has been disabled.
• Deprecated: Array and string offset access syntax with curly braces is deprecated in /home/user/domains/%%domain%%/public_html/wp-includes/script-loader.php on line 757
• Deprecated: Array and string offset access syntax with curly braces is deprecated in /home/user/domains/%%domain%%/public_html/wp-includes/script-loader.php on line 758

So, could it be that the above listed errors and logs and the “Add new” function error under Plugins page are resulted from “[] cURL error 60: Peer’s Certificate issuer is not recognized.”? If yes, then what action should I proceed to solve this?

Moreover, I have both PHP 7.4 and PHP 5.5, could these versions (especially 5.5) not support or conflict with my current WordPress version 5.2.18?

Thank you once again for your time and effort. I truly appreciate all of your kind support.

• This reply was modified 1 year, 6 months ago by ttran18.