Bad request on update or connect to space

I have Teamcity installed and encounter a strange problem. Everything works expect two things

- Update from the interface

- Using the committer to report to Space

Both give me 400 Bad Request errors. I checked the logs and they basically show the bad request response but no other issues. 


For example the catalina.out gives:

 

TeamCity initialized, server UUID: 67cf7251-89b3-4f8a-bb93-db66386a3305, URL: https://[host]
TeamCity is running in professional mode
[TeamCity] Super user authentication token: 6319808286716609771 (use empty username with the token as the password to access the server)
[2023-06-14 14:00:06,391]   WARN [th id=11; http-nio-8111-exec-2] -   jetbrains.buildServer.UPDATE - Unable to check for TeamCity updates via URL "https://www.jetbrains.com/teamcity/update.xml": got response status 400 with response text "<html> <head><title>400 Bad Request</title></head> <body> <center><h1>400 Bad Request</h1></center> <hr><center>nginx</center> </body> </html>" (truncated at 1024 symbols)
[2023-06-14 14:00:06,394]   WARN [th id=11; http-nio-8111-exec-2] -   jetbrains.buildServer.UPDATE - Error while checking new TeamCity version: jetbrains.buildServer.updates.ServerUpdateException: Unable to check for updates via URL "https://www.jetbrains.com/teamcity/update.xml": got response status "400" (enable debug to see stacktrace)

Directly accessing the url works for me. I disabled the firewall as test without avail. In what direction should I be looking?

0
2 comments

Sorry, I forgot. Running TeamCity Professional 2023.05 (build 129203)

0
Hi! Can you log into the TeamCity server, run this command (or an equivalent) locally on the server: `curl -i https://www.jetbrains.com/teamcity/update.xml`, and share the output?
0

Please sign in to leave a comment.