Closed sjclark closed 9 months ago
Thanks for reporting it; we're experiencing the same thing.
same here
experiencing the same on a few of our sites
Same 😬
100% this is Cloudflare protection. You can see the "Just a moment..." message
We're currently looking into this, sorry!
This should be resolved now.
Should be resolved now.
But while testing it, I didn't get a 500 error, the CP continued to work. I just got a "could not contact the outpost" banner, as expected. Odd.
We check for a RequestException
like you're seeing. I'm not sure why it's not being caught for you. 🤔
What versions of Statamic were you running?
@jasonvarga not OP, but we have a couple of sites running. FWIW the one on 4.44.0 got the outpost errror in the log as described but did not break. Other at 3.3.48 did fail (CP returning 500) with the error
This should be resolved now.
does indeed. thank you very much for the quick fix
Did anyone have sites >= v4.35.0 that went down?
Hiyo cheers, resolved for me Resolved at 2024-01-19 07:32:40
- away from computer currently - but don't think any of my sites would be beyond 4.35.0
atm
I've managed to figure out why some people were experiencing server errors, while others were seeing the expected "could not contact the outpost" message in the Control Panel.
From testing, it seems like sites running v4.12.0 and above didn't experience any server errors due to #8475 being included in v4.12.0 which made some improvements around Outpost error handling.
To avoid any potential statamic.com downtime causing server errors in the Control Panel, I'd recommend updating to v4.12.0 or higher.
To avoid any potential statamic.com downtime causing server errors in the Control Panel, I'd recommend updating to v4.12.0 or higher.
I'm sorry but I don't think this is a very good response. We have many sites that although deemed "legacy", are still operational and used by customers on a daily basis that don't necessarily NEED to be updated. Having the whole control panel crash because of an outpost issue seems a bit crazy. If older versions of Statamic are no longer being supported why not just remove this check?
Having the whole control panel crash because of an outpost issue seems a bit crazy.
This was never an intentional behavior, and was fixed once we discovered it happened.
I've just backported that same fix to the 3.4 line and have tagged 3.4.16 if updating all the way to 4.x is not an option for you.
Bug description
The Statamic Control Panels of all my licensed Statamic 3 & 4 sites are currently down as of ~5pm AEST.
Root cause: HTTP 500 - Internal Server Error
Incident started at 2024-01-19 05:47:38
Client error: POST https://outpost.statamic.com/v3/query resulted in a 403 Forbidden response
Seems to be others with the same issue in the Statamic Discord.
How to reproduce
Try use the Control Panel on any live site - results in a 500 Error - as per logs
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
Runtime (default)
Additional details
Sites are hosted on Ploi, php8.1 & 8.2, predominantly Lets Encrypt SSL. Some sites behind Cloudflare. Front-end of sites (if using Static Caching) works fine.
Occuring on sites with both current and expired licenses.
I've noticed the Statamic site itself seems to currently be behind interstitial Cloudflare checkers - may be related to that. Might need to whitelist/blacklist from Cloudflare.
Seems fairly fragile that the license server failing would pull down all sites? (but maybe I'm just 5pm friday grumpy) 😂