I very recently upgraded to version 1.26.2. All seemed well at first, but I then noticed that my crons didn't seem to be working. The cron logs showed that they were running, but when I looked at my apache logs I noticed that any wget commands in the crons were routed to..
/var/www/html
whereas the actual web directory is..
/home/user/domains/website.com/public_html
Obviously the wget command then returns a 404. Strangely, as a client I can request the file and it works just fine, I get an HTTP status code 200. I tried setting up the crons to run on my other servers, but then I got a 302, so I tried using cURL on a different server, and I got a 302 again, thus it seems that client requests work fine, but server requests do not.
Does anyone know any reason as to why this would happen? I'm quite confident that it is caused by the update, as the logs indicate the problem started immediately after the udate.
/var/www/html
whereas the actual web directory is..
/home/user/domains/website.com/public_html
Obviously the wget command then returns a 404. Strangely, as a client I can request the file and it works just fine, I get an HTTP status code 200. I tried setting up the crons to run on my other servers, but then I got a 302, so I tried using cURL on a different server, and I got a 302 again, thus it seems that client requests work fine, but server requests do not.
Does anyone know any reason as to why this would happen? I'm quite confident that it is caused by the update, as the logs indicate the problem started immediately after the udate.