6

I'm currently setting up my work system and totally lost at getting Microsoft Teams running. Other Microsoft Office products (like Excel, Office, Word) are working seamlessly for both native and web version, and for now only Teams seems to not work (also for both native and web).

Whenever I try to sign into Teams there's a redirection loop:

↱ https://teams.microsoft.com/go#
↳ https://teams.microsoft.com/go#id_token=xxx&session_state=xxx

... until being redirected back to the login page after about 10 seconds with the vacuous message:

We couldn't sign you in. Please try again.

It's working on a colleague's system, so it's not an account or licence issue.

I googled it, tried Chromium, Firefox, Opera, several packages like the widely-used teams-for-linux and even the official client for Insiders, ms-teams, tried both AUR and Snapcraft packages, and even built them myself - nothing worked. It's always the same behavior as described above.

I'm using the i3 community edition of Manjaro (freshly installed).

I'd be very thankful for any kind of ideas.

2
  • 5
    Try re-syncing the time with an internet time server. Question: Did you change the password just before this started?
    – harrymc
    Commented Dec 16, 2019 at 20:05
  • 1
    Oh my... yes indeed, I always use UTC on my devices and usually leave other things default. I set them equal and everything works now. Man! I would have NEVER guessed that without your input. Please write it as an answer so I can accept it. :) Thank you! Commented Dec 19, 2019 at 9:33

3 Answers 3

10
+50

The difference between your computer and that of your colleague is most likely that of the clock.

I suggest to re-sync the time on your computer with an internet time server.

3
  • thanks, same issue ubuntu , pity this question is not more available to the error phrase 'Teams: "We couldn't sign you in. Please try again.' redirect . I had it in connection with superuser.com/questions/1470765/… from the error logs on background
    – FantomX1
    Commented Nov 18, 2020 at 21:48
  • 1
    As this issue is gaining more attention, I updated the title to a more fitting one. Hopefully users will find their way to this thread sooner now. Commented Nov 19, 2020 at 9:40
  • Wow, it really was! When my laptop ran out of battery it apparently started running 3000 seconds fast of NTP. A quick chronyc makestep to cancel the slew and force the clock to the right time solved the problem.
    – kqr
    Commented Feb 18, 2022 at 12:00
2

I have same issue, you can execute these commands (Tested on ArchLinux):

We will activate the service, to activate synchronization between the computer and the servers on the internet:

sudo systemctl enable systemd-timesyncd.service

We start the service :

timedatectl set-ntp true
1
  • 1
    @MMM Sorry, I updated the comment ^^
    – Bensuperpc
    Commented Mar 17, 2020 at 14:36
0

Had the same issue on Ubuntu 20.04 LTS. Tried resetting TZ, spoofing my browser user-agent to seem like it came from a Windows PC etc etc.

None of these fixes worked and I continued having the issue on both web and desktop app.

I finally fixed it by resetting my DNS Nameserver. Here is a link to doing this on the more recent Ubuntu releases. Maybe it helps someone...

I used an OpenDNS server address i.e. 208.67.222.222

Alternatively 8.8.8.8

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .