For two weeks now, the errors were no longer displayed in Cpanel/errors (where there is the little red Error icon) so I contacted the support department of my host, and each operator who answered gave me a different version and each one made changes either in my .htaccess file or on the server, so much so that I found myself with 50,000 503 errors and others in my administration panel, 500 errors, site not available, etc., until I got shocked and threatened to change my host. They apologized and transferred my support request to a higher level programmer, but the problem is still not resolved.
I finally did a full restore of my site to a date prior to their changes and everything was back to normal, except that the errors were still not showing up in Cpane/error.
Now they told me that they had contacted their supplier (probably Cpanel or Lightspeed) and they still tell me that it's probably a rule in my .htaccess that's causing the problem, however the errors have suddenly started to show up in Cpanel/error but they are all errors like the following and there is plenty of them:
Code: Select all
2021-04-26 19:07:19.207196 [INFO]  [T0] [22.214.171.124:23447#APVH_image.lesbricollesdecleo.com:443] File not found [/home/xxxxxx/public_html/image/error_404.php] 2021-04-26 19:07:19.207172 [INFO]  [T0] [126.96.36.199:23447#APVH_image.lesbricollesdecleo.com:443] File not found [/home/xxxxxx/public_html/image/index.php]
Now they advised me to put a .htaccess with less rules to see if it is one of the rules in it that would cause the errors. I've had the same .htaccess for at least 3 years and never had these problems, so why would it suddenly happen? I haven't added or changed anything, I haven't added any extensions and I haven't changed any files, so it doesn't make sense to me.
And they tell me that if I want to keep my .htaccess intact to create an error.log file, but I don't see how an error.log file would solve the problem?
Does anyone have any idea what is causing all these 443 errors, I may be wrong but I have a feeling it's because my /image directory is not https anymore, am I right?