Description of the issue:
Cloudflare returning 502 (Bad Gateway) for pealim.com since today.
Browser: Brave Linux 1.71.118, private mode, shields off.
Reproducible with Brave Android both on local WiFi and cell network.
Working with no errors with Chrome.
Also broken with Firefox: same symptoms.
Worked yesterday; this started today. No system updates/changes or anything like that since yesterday.
Ideas? Advice? Additional data?
Thanks!
NVM: Chrome brings up the home page (presumably, from cache), but fails in the same way for any lookup/link on the site.
I used Firefox and its Developer Tools window, in order to observe what happens:
The text of the output (bottom of the window):
GET
https://www.pealim.com/
[HTTP/2 502 Bad Gateway 3138ms]
Cookie “cf_use_ob” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts.
If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite
Thanks for investigating; much appreciated that someone else is taking a look at this.
That output only shows the response from the Cloudflare server, I am not sure I understand how that conveys any information about the problem between Cloudflare and the target site.
Moreover, the message in Firefox console is just a warning - you can see the cookie being provided in subsequent requests, so it is set. The linked MDN doc is also a bit confusing: it states that SameSite is optional and I did not see that this is subject to change (“soon”, according to the message).
Found:
Troubleshooting Cloudflare 5XX errors
Error 502 bad gateway or error 504 gateway timeout
An HTTP 502 or 504 error occurs when Cloudflare is unable to establish contact with your origin web server.
There are two possible causes:
(Most common cause) 502/504 from your origin web server
You may also see 504 status codes in logs or analytics caused by cache MISS responses from Early Hints.
502/504 from your origin web server
Cloudflare returns a Cloudflare-branded HTTP 502 or 504 error when your origin web server responds with a standard HTTP 502 bad gateway or 504 gateway timeout error:
Resolution
Contact your hosting provider to troubleshoot these common causes at your origin web server:
Ensure the origin server responds to requests for the hostname and domain within the visitor’s URL that generated the 502 or 504 error.
Investigate excessive server loads, crashes, or network failures.
Identify applications or services that timed out or were blocked.
Thanks for the info. This clearly explains that the 502 is forwarded from the source site and NOT generated by Cloudflare.
The source site is now fixed - and everything is back to normal.
Yes - glad to learn that, here; thanks to your OP and study.
