I’ve just installed Octopus Server 2.0.8.977 on a test server, before we commit to a production server. The server is a Win7 machine (yes I know, but there it is). Chose AD authentication.
Initialialy the install failed because of a bug in Win7 (see https://github.com/OctopusDeploy/Issues/issues/193). I installed the hotfix KB2683913-x64 and the installation went ok. Created the first user using my AD admin account.
I can enter the portal from the local server eg. http://localhost:8080/Octopus where I have to enter my credentials, but I cannot access the site from my local machine using http://servername:8080/Octopus. I get a 502 “No connection could be made because the target machine actively refused it 127.0.0.1:8080”.
I have added rules to the firewall to enable traffic inbound and outbound on port 10931 on TCP and UDP. I still cannot connect to the portal.
This worked in version 1.6, though I had to change the app pool identity in IIS to use ‘Network service’ instead of ‘ApplicationPoolIdentity’. Then I could just access the site without having to enter credentials.
Why is ver 2.0 giving me such a hard time? Any ideas appreciated.
Thanks
Hi Jens - sounds a bit tricky, I don’t think we’ve tested Win7 as a server so it is possible there’s a limitation we’re not aware of. Would you mind checking a couple of things for me please?
First, can you please send the ListenPrefixes setting from OctopusServer.config, e.g. from C:\Octopus\OctopusServer? Something like:
There’s some UI support for this coming - it is possible that Octopus needs a second binding with the server name specified. Can you please try changing the bindings to:
(Hi Jens - just realised your first reply went directly to the support forum rather than me personally, but was held up because of the different email address used.)
Hi Nick,
Added servername binding, but still cannot access from outside.
Then I tried going back to port 80, and then it worked. I could open the portal site from my machine as well as locally on the server.
I think however that our server/net team would prefer the use of another port than the default, so getting port 8080 to work would be great.
Also the portal site keeps asking for credentials every time. That would also be great if we could skip this, as the AD already is authenticated.
Hi Jens- is the login screen being presented even after the “remember me” checkbox is ticked? If so I’ll raise a bug, just let me know which browser you’re testing with, thanks.
Just looking back to your original message:
I get a 502 “No connection could be made because the target machine actively refused it 127.0.0.1:8080”.
I have added rules to the firewall to enable traffic inbound and outbound on port 10931 on TCP and UDP. I still cannot connect to the portal.
Guessing it is just a typo, but the port you mention opening in the firewall (10931) isn’t the one you’re using to connect to Octopus (8080).
Hi Nick,
Finally got it working Opened the firewall for port 8080, not 10931.
Also the little checkbox had eluded me. Now it doesn’t ask me for credentials every time.
Opened the firewall for port 8080, not 10931.