First thing you can do is to try checking in your root directory of the WordPress instance if there’s a file called “error_log“. You can open it with any editor and see if there’s any error, especially marked as Fatal error. This maybe the cause of some problems.
Simply edit wp-config.php file in your root directory of the WordPress instance and locate
define('WP_DEBUG', false); eg: https://d.pr/i/AguD4C and replace with these lines:
define('WP_DEBUG', true); define('WP_DEBUG_LOG', true);
After doing this, in the /wp-content/ folder, there should be a new file called debug.log .You can monitor this file to see if there are any fatal errors inside.
If you want to have the errors displayed on the site, add this constant
define('WP_DEBUG_DISPLAY', true); next to the other ones.
You can use File Manager Pro – Filester plugin in case you need to access the root files of your site, even though ideally is through FTP.
Make sure to DISABLE after you’re done debugging!
Read more about Debugging in WordPress .
A good way of debugging conflict problems is by deactivating plugins one by one, until you identify the one that’s causing a problem or conflict.
When the site is live though, this can become a problem and the alternatives are either to put the site in Maintenance Mode (with a dedicated plugin), or better, use the Health Check & Troubleshooting plugin.
After you install & activate, try accessing the Troubleshooting tab and enable Troubleshooting mode. This will deactivate all plugins only while logged in with your account. So you don’t have to worry that visitors see what you see.
A video tutorial can be found here https://www.youtube.com/watch?v=nO1nP1gBstM .