Loving v3, but HTTPS bindings is not working. It seems to work properly as far for the configuration, but then when I browse to the URL it just sits there until I have a timeout error after a good minute.
Any help that you can provide would be fantastic.
By the way, I had a look at the server logs and I couldn’t see anything
helpful there.
Cheers,
Alex
Hi Alex,
Thanks for getting in touch.
Do you mean the HTTPS binding of the Octopus Server itself ? Or doing IIS deployments with HTTPS ?
Regards
Damian
Hi Damian,
Thanks for the prompt response.
OD’s own bindings.
Cheers, Alex
Hi Alex
I’m just doing some searching because we’ve had one other recent report of something like that.
What do you have your bindings set to in Octopus Manager ?
Regards
Damian
Hi Damien,
I had to undo the bindings now, but I tried all of the following
scenarios. The
common theme is that whenever HTTPS is enabled, the Octopus Admin Portal no
longer responds
- Installed my own certificate on the server and added a HTTPS binding
of the same URL as the HTTP binding -> Octopus Admin Portal no longer
responds
- Removed the HTTPS binding that was added in step 1 and added a HTTPS
binding of the same URL but using Octopus’s self signed certificate
-> Octopus
Admin Portal still does not respond
- Removed the HTTPS binding that was added in step 2 -> Octopus Admin
Portal responds as normal again
- Added a HTTPS binding of the same URL as the HTTP binding using my
own certificate but disabled HTTP to HTTPS re-direction -> Octopus Admin
Portal no longer responds
- Removed the HTTP binding -> Octopus Admin Portal still does not
respond
- Removed the HTTPS binding that was added in step 4 and added a HTTP
binding of the same URL -> Octopus Admin Portal responds as normal again
- Ran out of options and sent you the original email for heeelp
Cheers,
Alex
Hi Alex
Can you send me a screenshot of the bindings (just so we’re on the same page) ?
(You can make the post private if you like).
Also, have you checked the Windows Firewall to make sure the port is open ?
Regards
Damian
Hi Damien,
Sorry about the late response, I had a massive week.
Mate, I had a blond moment, it was the firewall
The https://domain.com: 10943 test confused me… I made a big assumption that port 443 was configured in our firewalls because of the https part of that test… like I said, a blond moment.
Cheers, Alex
Awesome new Alex, glad it’s working!
Damian