I encountered the same issue, and it turned out to be caused by an incorrect date setting on the device. After syncing the time and date to the correct values, everything worked fine again. It seems the error handling for this scenario could be improved, as the actual cause wasn’t clearly indicated.