Fixed now. For what it it's worth, it seems fixing some of the issue was a mixture of :following steps fixed the issue:
changing change the IP adress address of the ask.sagemath.org Ask Sage server on google sidethe Google side
after its recent move from Ohio State University to Laboratoire d'informatique de Paris Nord updating update other things on google the Google side (i do not manage the google Google account so i can not cannot tell) setting set up automatic https automatic redirection on asksage the Ask Sage server - extend the timeout of the
asksage Ask Sage server so that there is to give authentication checks enough time for checkingto complete