other8026 Probably9857 Are you still getting this error? I am not aware of anyone else reporting this.
RockHyrax other8026 I am also receiving this error message as of this morning. Tried fetching disconnected from VPN (Mullvad), and same error message.
other8026 RockHyrax Probably9857 Thanks for letting us know. You can try connecting to a server in another region and you may stop getting that error. There was a Vanadium update earlier. It's likely that there was an issue pushing data to the server you're connecting to (or that's my understanding of what can cause this error).
Probably9857 other8026 Thanks. If it's all the same to you, I'd rather be able to reproduce the error until there is a known cause. Let me know of there is anything I can do to help with troubleshooting.
GrapheneOS The issue was caused by a Python bug and has been worked around. https://blog.miguelgrinberg.com/post/it-s-time-for-a-change-datetime-utcnow-is-now-deprecated
PintOfGuinness I've encountered this issue today (started approx. 2-3 hours ago). Was getting java.security.GeneralSecurityException: repo downgrade when checking for updates. Anyone else?
fid02 PintOfGuinness I found this response from the GrapheneOS account on Discord to the error message: it's due to us trying to phase out 3.releases.grapheneos.org, the last repo update wasn't uploaded to it but you still got it via DNS we'll fix it