I encountered this today and it was due to the server datetime being way off. The date was March 11, 2025 at the time of this screenshot:
Once I corrected this, it started working again