Lina Asenova

For faster reply, I recommend getting in touch with WooCommerce’s support about this via?https://woocommerce.com/my-account/create-a-ticket/?if you have any of their paid WooCommerce products or?https://www.ads-software.com/support/plugin/woocommerce/?if you do not.

The symbolic link error means that there’s an invalid link to an old index.html file. You can make a backup of your site and then, via FTP, delete any index.html.ovh.old files that may be conflicting with your WordPress setup. Also check for and remove any broken symbolic links. 

Generally, your hosting provider should be able to assist you with that.

Internal server errors (error 500) are often caused by conflicts between plugins or theme functions. If you can access your admin panel, try deactivating all plugins. If not, follow this guide to manually reset your plugins without Dashboard access. If deactivating plugins resolves the issue, reactivate them one by one to identify the cause.

If the issue persists, switch to the default theme for your WordPress version to rule out a theme-specific problem. Without admin panel access, use SFTP or FTP or your hosting control panel’s file manager. Navigate to /wp-content/themes/ and rename the directory of your active theme. This will activate the default theme and help identify if the theme is causing the issue.

If neither step resolves the error, a .htaccess rule might be the culprit. To check, access your server via SFTP, FTP, or your hosting control panel. Rename the .htaccess file. If you don’t see it, ensure your file viewer is set to display hidden files.

The reason for the error should also be visible in the error log. You can find it in your hosting area. If necessary, the support of your hosting can help you.

Alternatively, you could also enable debugging in WordPress. How to do this is described here:?https://www.ads-software.com/support/article/debugging-in-wordpress/?

You can disable all plugins to see if that resolves the issue, then enable them one by one to identify the incompatible one. If disabling the plugins doesn’t help, switch to a default theme to see if the issue persists.

I recommend getting in touch with Elementors’s support about this via?https://elementor.com/support/?if you have Elementor Pro or?https://www.ads-software.com/support/plugin/elementor/?if you do not.

To be honest, I haven’t tried a plugin for that. I find manual testing to be the most reliable method. This involves checking the error log, enabling debugging to identify any issues, or deactivating all plugins and reactivating them one by one to isolate the faulty one. Although it’s time-consuming, for me it’s the most effective way to pinpoint the exact issue.

There may be a?misconfiguration or a conflict in your WooCommerce setup. For the best assistance?I recommend getting in touch with WooCommerce’s support about this via?https://woocommerce.com/my-account/create-a-ticket/?if you have any of their paid WooCommerce products or?https://www.ads-software.com/support/plugin/woocommerce/?if you do not.

You can enable debugging to identify any specific errors. Use an FTP client or your hosting control panel to access your WordPress files. For full guidance and step-by-step instructions on enabling the debug log, refer to the WordPress developer documentation: Debugging in WordPress.  

A common cause of fatal errors is a problematic plugin, so you can temporarily disable all plugins. If that resolves the issue, enable them one by one to identify the conflicting one. Since you’re unable to access the wp-admin dashboard, follow this guide to deactivate plugins manually: How to Deactivate All Plugins When Not Able to Access the AdminMenus. 

Your theme could also be causing a conflict. Try switching to a default WordPress theme (like Twenty Twenty-One) to see if that helps. You can rename your active theme’s folder to “theme_old” to revert to a default theme.

If none of these steps resolve the issue, you can reach out to your hosting provider, as they can check for server-side issues that may be causing fatal errors.

I recommend getting in touch with WooCommerce’s support about this via?https://woocommerce.com/my-account/create-a-ticket/?if you have any of their paid WooCommerce products or?https://www.ads-software.com/support/plugin/woocommerce/?if you do not.

You can try enabling debugging in WordPress to identify any errors or warnings that occur while the site is running. This can be done by adding a couple of definitions to your wp-config.php file. For full guidance and step-by-step instructions on enabling the debug log, you can refer to the WordPress developer documentation: Debugging in WordPress. 

A plugin might also be causing the issue. Therefore, you can temporarily disable all plugins. If that resolves the issue, enable them one by one to identify the conflicting one. If you’re unable to access the wp-admin dashboard, follow this guide to deactivate plugins manually:  How to Deactivate All Plugins When Not Able to Access the AdminMenus. 

Sometimes themes can also conflict with new updates. Try switching to a default WordPress theme (like Twenty Twenty-One) to see if that helps.

Here you can see more information regarding the issue you are experiencing: https://developer.www.ads-software.com/advanced-administration/wordpress/common-errors/#the-white-screen-of-death?

• This reply was modified 1 week, 5 days ago by Lina Asenova.

For the most effective assistance, I recommend asking in Ocean WP’s support forum:?https://www.ads-software.com/support/theme/oceanwp/?

• This reply was modified 1 week, 6 days ago by Lina Asenova.

The error message you see when trying to open the site – “DNS_PROBE_FINISHED_NXDOMAIN” – indicates a DNS-related issue (usually meaning that the domain name isn’t resolving to an IP address). I suggest reaching out to your hosting provider to investigate further.

Looks like WooCommerce made changes only to the Twenty Twenty-Four theme. I tried to replicate the problem on a fresh installation, and after installing WooCommerce on the Twenty Twenty-Four theme and deleting it (without modifying the wp-config.php file first), I encountered a similar issue.

To troubleshoot, I took the following steps:

1. I deleted the WooCommerce-related entries from the database. You can do this by logging into phpMyAdmin, accessing your WP database, and looking for tables starting with “woo.” I deleted those.
2. Then, I deleted the theme directly from the wp-content/themes directory and reinstalled it.
3. If the theme still looks different after reinstalling, go to?Appearance > Editor > Templates?and change the template of the Twenty Twenty-Four theme to restore its original settings.

NOTE: Make sure to clear your cache if you are using any caching plugins

I also recommend making a backup of your site before attempting these changes, just in case something goes sideways.

I recommend getting in touch with Jetpack’s support about this via?https://jetpack.com/contact-support/?rel=support?if you have any of their paid Jetpack plans or?https://www.ads-software.com/support/plugin/jetpack/?if you do not.

You can check out this support topic: https://www.ads-software.com/support/topic/could-not-reach-wordpress-org-2/, as it covers the same issue and might be helpful.