By chance, is the TeamCity service behind a proxy? If so, would it be possible to bypass the proxy temporarily to test? Also, it looks like the URL may be pointing to a V1 endpoint. You could try changing this to V2 to make sure that isn’t the culprit.
I’m able to use the exact same URL on the windows server to retrieve nuget package information from Teamcity. It seems only Octopus Server can’t retrieve information from teamcity.
And the situation is that before upgrading to 2021.1.7638, in version 2019.3.4 on the same windows server, we are able to retrieve nuget package information from the same teamcity URL.
are there any particular requirements for version 2021.1.7638 ?
It looks like this may be a V2 feed despite the V1 endpoint/URL. Assuming that is the case, have you tried replacing the DNS name with the IP address of machine TeamCity is installed on?
Also, can you confirm if there is anything between the Octopus Server and the TeamCity server such as a proxy or load balancer?
Look like there is proxy setting on the windows server, we are trying to disable it.
However, it is weird that when running Octopus Server 2019.3.4 on the windows server , it works fine.
Only not working after upgrade to 2021.1.7638 on the exact same windows server.
After we removed proxy settings from windows server, somehow Octopus Server’s teamcity http request still goes to our proxy server. Wondering whether there are anywhere in octopus config files , registry or db saved the proxy setting ?
From Network Monitor, we could see internet explorer it going directly to the teamcity server - first six lines. However, Octopus server is going to our proxy server - the last line in the screenshot.
Just stepping in for Donny as he’s signed off for the day.
Is your Octopus Server configured to use a custom proxy? I’ve linked our documentation which outlines how to configure a ‘Web Request’ Proxy for Octopus here. This will modify the XML file stored in the Octopus directory where the configuration is stored.
Release 2021.1.7638 should have resolved a known issue with proxies seen here, but it’s possible that this change has outlines another issue. I’ll run some tests on my end to see if I can reproduce this and figure out what’s going on!
I beleive Teamcity is not an issue here, the traffic hasn’t reached to teamcity.
What we observed is Octopus Server using proxy to connect to http://teamcity although setting Octopus not to use proxy server.
and the windows server is configured not to use proxy.
from Network monitor , we could see Internet explorer is accessing the same url directly .
But the http request from Octopus Server is going to proxy server first.
on “A” windows server 2016 , install Octopus Server 2019.3.4, everything went smoothly
try create release, and successfully retrieved nuget package information from teamcity
here is a screenshot of network activity captured. from Frame# 2019 to 2034 , octopus server made
queries to the sql server, and retrieve values for feeds-team-city , after that made http request to teamcity directly without using proxy.
on “A” windows server 2016, upgraded Octopus Server from 2019.3.4 to 2021.1.7638, everything went smoothly
try create release, and now Octopus server is not able to communicate with teamcity
here is a screenshot of network activity captured.
from Frame#231 to 247 are SQL Query, and at the end retrieved values for feeds-team-city.
From Frame#249 to 250, it is a request to query proxy server.
From Frame#254, Octopus Server is using proxy to make http request to http://teamcity
In upgrading from 2019 to 2021, Octopus moves from .NET Framework to .NET Core. It may be worth a quick check to see if the machine that Octopus Server is installed on has any http_proxy environmental variables set that could be getting respected by .NET Core. This could explain why something different is happening versus the proxy settings in Octopus and Internet Explorer.
There were http_proxy and https_proxy system environment variables.
was able to create release and retrieve nuget package information from http://teamcity after removed those env variables.