elmo3 There's something wrong with the SSL configuration / certificate on the GrapheneOS connectivity check server. https://connectivitycheck.grapheneos.network/generate_204 It probably should be falling back to HTTP in this case, but perhaps the nature of this certificate problem is unanticipated. (edit: though I guess we should be considering networks that have bad HTTPS connections to have "limited connectivity")
ShaaxGU BooleanImpression simple toggle your connectivity check server to "Disabled" or Google. In your Settings, Network, Internet Connectivity Check
patienttruth99 Same here, troubleshot for a bit. ISP is good - internet works despite phone reporting "limited connectivity". Warning goes away after switching to Google's connectivity check server.
BooleanImpression ShaaxGU Thanks, yes, it works if I select Google. Just wondering what that does. Am I now sending more information to Google?
dregrinfuces So, does this thread get noticed by the Powers That Be? Or should we formally report an issue with their server somewhere?
[deleted] dregrinfuces They are active on here but the best method to let them know is through this link: https://grapheneos.org/contact#reporting-issues
PatzEdi W1zardK1ng I am so glad others were having the same issue as me! I was really worried lol. Thank you for the quick feedback on the fix! Will the GrapheneOS server be up and running again? Thanks!
[deleted] PatzEdi Will the GrapheneOS server be up and running again? That entirely depends on the developers and what exactly is causing the issue.
Eirikr70 All this happened while I was tinkering with my home network and servers 😂. I thought I had broken seven my mobile connexion ...
spiral Same issue, starting today. wifi says "limited connection" or something and has an exclamation point, mobile data also shows an exclamation point - however, data in both instances works well.
dregrinfuces Yep. Changed mine back to the GrapheneOS attestation server, rebooted, signed out and signed back in (just to be sure), and everything's working correctly again. Yay!
Titan_M2 The grapheneos.network certificate was due for renewal on september 2 but certbot failed due to an incorrect path in its service file.