SOLVED

HTTP ERROR 500 • to-do.office.com/tasks • Web app down for anyone else?

Copper Contributor

Hi, we just started using to-do and we cannot share lists because the sharing links are not working.

 

When trying to open a sharing link like https://to-do.microsoft.com/sharing?InvitationToken=px7Tnbu.... which will redirect to https://to-do.office.com/tasks/sharing?InvitationToken=px7Tnbu.... we only ever get HTTP ERROR 500.

 

Actually, the base URL https://to-do.office.com/tasks/ already does not work, and we can't access to-do web-app. We tried different browsers, devices and Internet access points. 

 

We use the free to-do version, and do not have an office365 subscription. Is this related?

 

Windows and Android apps are working fine.

Does anyone else have this problem and/or a solution to this?

Kind Regards.
(none native englisch speaker)

 

AmitabK_0-1725262497921.png

AmitabK_1-1725263118845.png

 

 

 

7 Replies

We have E5 Business Licence and experience the same issue since friday Morning. 

 

- Desktop App is working

- Web App via Outlook App or directly via office.com does not work 

Error message: HTTP 500 Error

 

 

That's good news, then. If this is a generalized problem, then hopefully we can get somebodys attention at Microsoft soon.

same here.
seems there is an issue with the certificate:

Gordon_nomatter_1-1725285108105.png

 

 

@Gordon_nomatter what worked for me after I got the same error is that I pressed CTRL+F5 once, then when the URL changes I did it a second time and it fixed the issue, after that you can open the page normally.

@AmitabK my problem is that i cant redeem microsoft rewards

@Ferdaus510 thanks, but already tried that and didn't work for me.

now it seems ms fixed the problem and everything works again.

best response confirmed by AmitabK (Copper Contributor)
Solution
It appears that Microsoft did solve this. It’s working for me now too.
1 best response

Accepted Solutions
best response confirmed by AmitabK (Copper Contributor)
Solution
It appears that Microsoft did solve this. It’s working for me now too.

View solution in original post