The reason for the error should 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://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ – also here the support of your hosting can help you if necessary to edit the file accordingly.
In both cases you should be able to see what the cause is in the logfile.
Thanks. I’ll check it out!
Be around if anything come up. ^^
Arrgh.
I did what you said, but I ran into some problems with my site: richardmin.com
HostGator is hosting provider.
https://photos.app.goo.gl/K7H7JJjuGLELKuBe8
-__-;;
I’m abroad (US passport), and the International support doesn’t work, at least, for me.
Knowledge base is useless.
so the only forum who takes my error message is the WordPress forum. lol
Help, please?
– R
None of these entries have anything to do with the error. They’re all entries about bots that are trying to access nonexistent files directly – nothing that’s causing your problem.
Try to trigger the error again and immediately check the error log a few seconds afterward. Assuming your host displays it promptly, you should be able to see it more clearly. If that doesn’t work, you can still use the WordPress debug mode mentioned above or try contacting your host’s support again.
