Issue creating Release from TeamCity but not from octo.exe directly

I’ve removed the API key from the latter. Team City is running v4.38.0 of the Plugin It was also an issue for me in v4.34.0

Hi Ben,

That error is characteristic of octo.exe receiving an HTML response rather than the expected JSON. I’ve seen this behaviour with some Proxy configurations, which throw up an HTML login page when trying to connect to some endpoints, and I’ve also seen it when DNS is incorrectly resolved, sending the tool off to a website instead of the API.

Is the second screenshot taken from the exact same machine as the first, or a different machine?



different. I’ll jump onto the build agent and try on there.

Different behavior from the Build agent. Looks like a DNS issue. Thanks for the help !

No worries!


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.