Swagger fails to load API definition

Octopus server 2023.1.9749

I have one https:// fqdn url bound in the server config, but Swagger wants to load from http://servername

Hi @seanl,

Thanks for reaching out to Octopus Support, and I’m sorry you’re experiencing this issue accessing Swagger UI on your instance.

After some testing, I was able to replicate what you see by setting the Octopus Server Uri to a URL that doesn’t have a matching binding in the Octopus Server Manager. When you browse to Configuration > Nodes in the Octopus UI, you’ll see Server Uri on the right. I’m assuming, in your case, that is set to http://utdep01hq, and there is no HTTP binding setup for that URL.

To fix this on my instance, I updated the Server Uri to match the https address and restarted the Octopus Server service. After that, my Swagger UI screen began loading normally again.

Please let me know if this helps or if you have any questions.


That’s what I was missing, thanks!


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