TC9 - Cannot connect to Issue Tracker behind proxy

I've been unable to get Teamcity to connect to JIRA. Teamcity is behind a proxy, our Jira instance is internet-accessible.

I've confirmed that with a local instance of TeamCity (via Docker), I can connect to our Jira instance.

Teamcity is running on Centos7. (real proxy server renamed to proxy.mydomain.net)

Here is the Java Configuration as listed at /admin/admin.html?item=diagnostics&tab=dumps

Java version: 1.8.0_60

Java VM info: Java HotSpot(TM) 64-Bit Server VM

Java Home path: /usr/java/jdk1.8.0_60/jre

Server: Apache Tomcat/7.0.59

JVM arguments:

...

-Dproxyset=true

-Dhttp.proxyHost=proxy.mydomain.net

-Dhttp.proxyPort=3128

-Dhttp.nonProxyHosts=*.mydomain.net|localhost

-Dhttps.proxyHost=proxy.mydomain.net

-Dhttps.proxyPort=3128

-Dhttps.nonProxyHosts=*.mydomain.net|localhost

...

I've confirmed I'm able to connect to a Github VCS root (so internet access works).

The way I verified this is an issue with the proxy (and not Jira) was using ngrok.  https://ngrok.com/

Setting up an NGROK tunnel, it tells me when requests come in, and what the URL is of the request (even if that request ultimately goes nowhere)

I've confirmed that the request never gets in NGROK which means that it's not using the proxy settings. I can't seem to figure out what's going on.

4 comments
Comment actions Permalink

Hi Weston,

Could you please try to add quotes and to escape "|" symbol in nonProxyHosts properties: Dhttp.nonProxyHosts="*.mydomain.net\|localhost" ?

0
Comment actions Permalink

This isn't an issue with nonProxyHosts. The host is on the OTHER side of the proxy, so I need to use the proxy to access JIRA. That's why I mentioned that access to Github works through the VCS root configuration.

What I'm trying to say is that it seems as though Teamcity is using the proxy variables correctly to access Github, but the "Issue Tracker" functionality does not use the proxy information. At least this is my speculation right now.

The snippet provided isn't what I'm putting into the command line, it's what is reported by Teamcity on the page: /admin/admin.html?item=diagnostics&tab=dumps

The exact commands I'm using to start teamcity are documented here (my docker repo for teamcity server):


https://github.com/ghostsquad/docker-teamcity/blob/master/entrypoint.sh


0
Comment actions Permalink

And as I said previously, the TC server is behind a proxy, and cannot access the internet without using the proxy. The fact that I can get to Github (or an NGROK endpoint), means that the proxy is working for the VCS configuration. But again, I get no connection attempt through NGROK when attempting to configure an Issue Tracker.

0
Comment actions Permalink

Yep. This has been verified by Jetbrains as a bug.

https://youtrack.jetbrains.com/issue/TW-8876

I really hope this gets fixed soon, as it is preventing our Company from considering Teamcity as a solution.

0

Please sign in to leave a comment.