This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 77%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Hello,
I work with several developers, and our company recently moved to Teams. Many of us are linux users and we all (Windows users included) connect to our organization through a corporate proxy. We all use the Teams desktop app, and the linux users are either Redhat or CentOS users.
All the Windows users and a few Linux users have no problems connecting to Teams. However, some Linux users will try to log in, but are unable to. When they try to log in, they are prompted to enter their work email. When they click Next, they get a message saying "Taking you to your organization's sign-in page" and then a new window opens up. This window is blank. For Linux users that are able to log in, this would normally be our organization's login page.
For the people that can't connect to Teams in Linux, we have verified the following:
Any ideas? Unfortunately we are unable to test without using a proxy server. SELINUX is disabled, Firewalls are disabled. Certificates are needed to see the organization's login page, but people who had certificate issues experienced a completely different error, which we were able to resolve.
In any case, we are a bit stumped.
I've attached the logs of someone that was unable to connect. 96340-logs.txt
@Lisa ,
Are there any differences between the affected users and unaffected users?
The proxy server seems to be a factor. I checked you log file and found this error message - Error occurred while saving env_config.json. It seems related to the network connection.
Currently, we have no more efficient solutions to your scenario. We will do more research and any update I will share with you here.
Thanks for your understanding. Have a nice day!
Thanks. We pretty much summed up that it was a network/proxy error. I appreciate you confirming it. I guess I will further investigate the settings between the affected users and the unaffected users. If you can think of anything we can do to troubleshoot, please let me know.
@Lisa ,
From the log file, we didn’t get much information for authentication issues. The network trace is needed.
So, we recommend you open a Request Service through IT Admin to get more efficient support. The support engineer will collect your backend log file and analyze this problem exactly.
Thanks for your understanding.
Hello again! We were able to resolve the issue.
It turns out it was a certificate issue. The affected users had outdated certificates on their machines. We updated their certificates and all is working now. I wish I could give you the nitty-gritty details, but this is all I have.
In any case, thank you for your help.
I'm glad to hear that. Thanks for your sharing.
For helping more people with the same problem, we recommend you accept your answer.
Have a nice day!