I had this issue the day before yesterday and I thought it was caused by Wp Super Cache. The plugin author made an update to his code yesterday and then it worked again, until this morning when everything started all over again.
It’s not the plugin anymore, so it must be something from the core settings. Any ideas?