Hi, I can’t connect to the community library, while the network is perfectly functioning.
My env is a newly installed Octopus 3.12.1.
This is the error:
The Octopus server failed to connect to our community library. http://g.octopushq.com/CommunityContributedStepTemplatesTroubleshooting
An error occurred while sending the request.
System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 40.112.143.214:443
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
The funny thing is that this IP address is actually an empty Azure web site.
Any idea? Do I need to configure something specific?
Hi Luca,
Thanks for getting in touch! I just checked Community Library (https://library.octopus.com) stats and we’ve had 19 errors and 59000 successful requests in the last week. We also haven’t heard anything about connectivity problems from other customers.
Are there any firewalls or proxies between Octopus and the Internet?
Regards,
Pawel
Hello,
I’m having the same problem. We have a forward proxy that requires credentials & these have been entered. If I browse the library via Library | Step Templates & then click the ‘community library website’ link then I get to the library with no pop-ups requesting credentials.
If I execute the Configuration | Features | Sync Now task then I get the same error as the OP, although for me I get re-directed to https://octopus.com/docs/administration/octopus-community-step-templates-integration rather than being in an empty Azure site.
Regards,
Martin.
Hi Martin,
Thanks for getting in touch! You get redirected because the link in the error message is a shortlink.
Library integration uses the same proxy as the one that is configured in Octopus Server so technically speaking it should assuming the proxy allows calls to the internet. Can you check that for me?
Also, can you send me a screenshot of your Web Proxy Settings in Octopus?
Regards,
Pawel
Hello Pawel,
Thanks for the reply – I have got the library sync working now. I had the proxy set to use the IE proxy with custom credentials and, for whatever reason, this doesn’t work for me. But changing it to custom & actually entering the proxy details solves the problem.
Regards,
Martin.
Hi, same here! I had to manually enter my proxy configuration in Octopus to make it work. Use IE proxy option doesn’t work.
Hi,
I’m glad that both you managed to get the synchronisation working.
The only reason I can think of re why it did not work out of the box is that the user (possibly you) who runs IE is already authenticated against the proxy whereas the user used by the Octopus server is not.
The simplest test would be to temporarily use your user to run Octopus server and see whether the sync works out of the box.
Regards,
Pawel
Hello Pawel,
Although it’s working I think that there is a bug in there somewhere. There are four options on the web proxy page in the Octopus Manager, and the last two are relevant for me:
· Use the proxy server configured in Internet Explorer, with custom credentials
· Use a custom proxy server
I’ve tested both using the same credentials – the IE proxy with custom credentials fails, and explicitly entering the proxy IP & port succeeds.
One final piece of information – our network admins have locked down the IE settings from the desktop, they are set by GPO. The IE proxy settings call a pac script rather than define an IP.
Regards,
Martin.
Hi Martin,
Thanks for the details. I tested Octopus with proxy settings specified in a PAC file and it worked just fine. What is the account you are using to run Octopus Server? Are you in a position to perform the test I mentioned before?
Regards,
Pawel
Hello Pawel,
Sorry for the delay in replying to you.
Changing the Octopus Manager service to use my credentials does not resolve the problem. However I didn’t expect it to as we don’t use active directory accounts to authenticate on the proxy – it uses a separate ldap directory so running the server using an AD account has no bearing of proxy authentication.
The situation remains the same. If I set Octopus to use the IE settings plus custom credentials then the library sync fails; but if I explicitly enter the proxy details then the sync succeeds.
I think that the problem is still most likely to be that the IE settings specify a proxy.pac script which Octopus doesn’t know how to handle.
Regards,
Martin.
Hi Martin,
Thanks for coming back to me with the results.
Re Octopus and pac files, Octopus doesn’t explicitly handle them as we simply rely on .NET framework to do that for us. Also, I tested Octopus with a simple pac file and it worked as expected.
Are you ok with the current workaround as to be honest I’m running out of ideas what might be causing this problem in your environment.
Regards,
Pawel