I'm running into an issue where the Hub integration in YouTrack seems to be changing automatically, from the SSL-secured version behind the proxy to the base url within Hub itself.
Basically, I've got YouTrack running with its base URL in the software being http://youtrack.mydomain.com:85, then I'm using an IIS reverse proxy and having people access it via https://youtrack.mydomain.com. That seems to work fine- we can get to YouTrack no problem at the SSL-secured address.
For authentication, I've got Hub setup with its URL configured as http://hub.mydomain.com:8080, then I've got another IIS reverse proxy setup, and everyone is just supposed to be accessing it via https://hub.mydomain.com. Again, this seems to work fine.
So yesterday, I've got YouTrack pointed to https://hub.mydomain.com in Hub Integration, and on the Hub side I've got the YouTrack service using https://youtrack.mydomain.com, and everything is working fine. However, when I come in today, both sides have reverted to using the non-SSL secured URLs. I go to Hub Integration in YouTrack, and the url is listed as http://hub.mydomain.com:8080, and the YouTrack service in Hub is pointed to http://youtrack.mydomain.com.
I feel like there's a configuration step I've missed here. Does anybody have any guidance?