Tentacle installation problem - unable to 'browse' locally

I have problems getting a tentacle to work on a machine in a DMZ.

  • It’s configured in listening mode, port 10933, firewall off locally.
  • Check for publisher’s certificate is unchecked
  • Service is started
  • When I try to browse the service locally on https://localhost:10933, I first get the certificate warning and upon confirmation that I really want to view this page, I just get a default error page. Note this machine has no internet access or similar.
  • Not really relevant, due to local error, Octopus server is hosted locally, tentacle is installed on a remote location over a MPLS connection and ops on both sides, confirm that 10933 traffic is allowed.

We have been trouble shooting this for a while without any success. I could really use some input here. I’ve attached the log.

octopuslog.log (5 KB)

Hi Jasper,

When you browse to the server locally (https://localhost:10933) the certificate warning/error page is expected (it’s a security measure provided by your web browser). After you click “Proceed”, you should see a page saying:

Octopus Tentacle configured successfully

If you’re seeing anything else, can you send me screenshots?

If you remote into your Octopus server and open a web browser, and navigate to https://your-tentacle:10933, what do you see?

Paul

Hi Paul

I do not get that message on this machine. I’ve attached 2 screenshots.

Hi Jasper,

Is the second screenshot what you see after clicking “Continue to this website”? Are you able to try using a different web browser?

Paul

Hi Paul.

With Chrome it actually works. So back to the theory that it’s one of the firewalls.

Thanks.
/Jasper

Hi Jasper,

What happens if you use Chrome on your Octopus server to browse to the Tentacle that way? Once you can make that work from the Octopus server then Octopus should have no trouble talking to the Tentacle.

Paul

We cannot reach the tentacle from the octopus server via https://localhost:10933. Since I couldn’t get it to work locally, I initially thought it would be some kind of local configuration problem. However, we tried to port scan from the octopus server to the tentacle, and 10933 it not open. We can reach the tentacle from another machine on the same vlan, without any problems. So it must be firewall issue.