Ah I see, you have a proxy configured in Internet Explorer (hence the error in IE). But since curl (without proxy parameters) works, a proxyless connection works. For some reason the "No Proxy" option is not bypassing your IE Proxy. I will have to check up on that when everyone is back at work, which won't be before Tue (Australian time).
However, try adding the octopus server address to the list of addresses to bypass in your IE proxy configuration.
To tell the truth, I don't know so much about network configuration. I just know that proxy is required and auto-configurated, therefore I can't just change settings in the IE for a long time to solve it, because they are should be generated automatically (by the way, I mentioned in the previous message, that, unfortunately, it didn't solve this problem).
As we know, the port 10943 is open for all connections.
Ah, sorry I didn't realise you were on an older version. The WebSockets feature got introduced in 3.12. If possible, upgrading may help as we have fixed some proxy issues since 3.4.
So it looks like you cannot connect to the Octopus listening port using the proxy configured in IE, but bypassing it works.
I setup a proxy in IE that does not exist and that caused my register-with command not to work. However when I issues the following command, the register-with command worked:
.\Tentacle.exe proxy --proxyEnable=false
If that does not work, could you send me the commands that you are using to configure the tentacle?
There may be a problem if you need the proxy to connect to the API, but you must bypass it to access the listening port. The reason is that octopus only allows either the use of a proxy or not. Try issuing the following command to see if that is the case (insert the WebUI url of your site:
We've upgraded Octopus server to the latest version. After it I tried to configure Tentacle with the following commands, but I've got the same error (403 Forbidden) in command prompt on the last command:
Checking connectivity on the server web socket address wss://our-server-address/OctopusComms...
Error: The remote server returned an error: (503) Server Unavailable.
Full error details are available in the log files.
The remote server returned an error: (503) Server Unavailable.
at Octopus.Tentacle.Communications.OctopusServerChecker.<>c_DisplayClass2_0.<CheckServerCommunicationsIsOpen>b_1() in OctopusServerChecker.cs:line 70
at Octopus.Tentacle.Communications.OctopusServerChecker.Retry(Action action, Int32 retryCount, TimeSpan initalDelay, Double backOffFactor) in OctopusServerChecker.cs:line 93
at Octopus.Tentacle.Communications.OctopusServerChecker.CheckServerCommunicationsIsOpen(Uri serverAddress, IWebProxy proxyOverride) in OctopusServerChecker.cs:line 74
at Octopus.Tentacle.Commands.RegisterMachineCommand.StartAsync in RegisterMachineCommand.cs:line 95
at Octopus.Tentacle.Commands.RegisterMachineCommand.Start() in RegisterMachineCommand.cs:line 72
at Octopus.Shared.Startup.AbstractCommand.Octopus.Shared.Startup.ICommand.Start(String commandLineArguments, ICommandRuntime commandRuntime, OptionSet commonOptions, String displayName, String version, String informationalVersion, String environmentInformation, String instanceName) in AbstractCommand.cs:line 78
at Octopus.Shared.Startup.OctopusProgram.Start(ICommandRuntime commandRuntime) in OctopusProgram.cs:line 252
at Octopus.Shared.Startup.ConsoleHost.Run(Action`1 start, Action shutdown) in ConsoleHost.cs:line 77
at Octopus.Shared.Startup.OctopusProgram.Run() in OctopusProgram.cs:line 101
Looking at the steps you are running, you do not need to issue the poll-server command, that is designed for high availability to register the second machine. The register-with command you are running registers the machine as an listening tentacle, so if that succeeds, does the tentacle appear on the server? If you want a polling tentacle, use the --comms-style TentacleActive parameter with poll-server See this page for example scripts.
I'm wondering also whether the user for the API key you are using has permission to create machines.
Could you please restart the Octopus Service service, try again and check the server log for any errors. Also look at the startup log entries, it will let you know the listening ports.
When you issued the the command command, did it print Registering the tentacle with the server at before the 403? (this is a new message added in 3.11). If so that would indicate it connected to the the port correctly, connected the API and authenticated but the user did not have the right permissions.
If that still doesn't work, please send me the server log and the full output of the register-with command.