Unable to Login To TeamCity With Pluggin
Can someone please tell me what I'm doing wrong? I've installed Rider 2019.2.2 and I'm running TeamCity 2019.1.
I've added the TeamCity plugin through the marketplace...but when prompted for my username and password, authentication fails. I can navigate to the same URL I have provided the plugin, enter the same username and password, and log in successfully.
http://localteamcity/
myname
mypassword
Works via web browser but not via the plugin. The error message is 'Authentication error: Check username and password'
Please sign in to leave a comment.
Hi,
Are you authenticating on the TeamCity server through Hub? If so, is two-factor authentication enabled?
If Token-Based Authentication is enabled on the TeamCity server, please try to use the TeamCity username and token to log in.
You can manage tokens in My Settings & Tools | Access Tokens.
-Anatoly
I have the same problem. After entering the username and password, the system prompts an authentication error. Any suggestions on how to fix this problem?
Hi Beetle. The error seems to be related to this issue (ongoing at the time of posting): https://youtrack.jetbrains.com/issue/TW-76024
To help investigate it, please specify which Rider version you are using.
Thanks a lot! After upgraded Android Studio to 2022.2.1, Teamcity was able to log in correctly.
Thanks a lot!
Either Plugin TeamCity via username&password or TeamCity (Experimental) via Access Token does not work.
http://localhost:8111 -→ Of course, I am testing localhost. But this should work anyways.
Thanks for your update.
To help us narrow down the issue, could you please provide a bit more information:
• The exact error message you see in the IDE when the login fails (a screenshot would also be helpful)
• Your Rider version
• The version of the TeamCity plugin installed in Rider
• Whether the issue occurs with both authentication methods (username/password and access token), and if the behavior differs between them
Additionally, if possible, please confirm whether the same credentials or token work when accessing the TeamCity REST API directly (for example, via `/app/rest/server`), as this helps us distinguish between server-side authentication issues and plugin-related problems.
With this information, we’ll be able to investigate further.
It worked for me only if I self-signed a certificate so that adding the host as https:localhost instead of http://localhost:8111. The error was:
Both authentication (password or token) methods did not work as http.
As self-signed https both teamcity pluggins worked the connection.
TeamCity pluggin: 2025.11.208130
Rider: 2025.3.4
Hi,
Could you please check the following setting on your TeamCity server:
Specifically, verify whether “Enable for all requests” is enabled under HTTPS Redirect.
If this option is enabled, then all HTTP requests are automatically redirected to HTTPS. In this case, connecting via `http://localhost:8111` may fail, while `https://<host>:<https-port>` will work as expected.
So if you are seeing that HTTP does not work but HTTPS does, this is expected behavior when this setting is enabled.
Please let us know what you find.
My TeamCity version is TeamCity Professional 2025.11.3
And the HTTPS Settings page looks like:
Those options to disable does not exist. Probably I would need only to update it.
Hi,
Thank you for the details and the screenshot.
From what we can see, HTTPS is not actually configured yet on your TeamCity server. The message:
Indicates that Let's Encrypt cannot be used with `localhost`, so no valid HTTPS endpoint is currently available.
Could you please check the following:
1. Server URL setting
Go to Administration | Global Settings and confirm what is configured as the server URL.
2. Reverse proxy usage
Are you running TeamCity behind a reverse proxy (such as Nginx, Apache, IIS, etc.) that provides HTTPS?
If so, please let us know the external URL you are using to access TeamCity.
Best Regards,
Tom