This file is actually needed even if you set things up on your web host, as they rely on the file as well.
What you could try is going to Dashboard > Updates, there’s a Re-install button (don’t worry, it only re-installs WordPress’ core files, it doesn’t touch your configurations, content and such).
]]>I already re-uploaded wp through FTP and loaded /wp-cron.php in the browser.
I also activated a free external cron service and it seems it got picked up now, but wp-cron is still seen as a 404.
If you visit the wp-cron.php file directly in your browser, you see the file as expected, but if WordPress tries to sue it, it fails?
]]>I’m wondering though what did trigger it, since all my crons now last run about a day ago instead of almost 6 months.
]]>I did notice it doesn’t go in error on my local install (which is identical in code), so it must be something server related.
]]>