FATAL Unhandled AppDomain exception occurred: Failed to listen on prefix 'https://xxxx.com:443/' because it conflicts with an existing registration on the machine

Legacy Uncategorised
1

Any ideas what is happening? I just upgraded from Octopus Server version 3.3.10 to 3.3.27. The Octopus Server also has a Tentacle on it. Not sure how to resolve this.

2016-10-21 11:31:24.7887 7 FATAL Unhandled AppDomain exception occurred: Failed to listen on prefix ‘https://octopus-deploy.xxx.com:443/’ because it conflicts with an existing registration on the machine.
System.Net.HttpListenerException (0x80004005): Failed to listen on prefix ‘https://octopus-deploy.xxx.com:443/’ because it conflicts with an existing registration on the machine.
at System.Net.HttpListener.AddAllPrefixes()
at System.Net.HttpListener.Start()
at Octopus.Server.Web.OctopusNancyHost.TryStartListener() in Y:\Work\refs\tags\3.3.27\source\Octopus.Server\Web\OctopusNancyHost.cs:line 203
at Octopus.Server.Web.OctopusNancyHost.StartListener() in Y:\Work\refs\tags\3.3.27\source\Octopus.Server\Web\OctopusNancyHost.cs:line 155
at Octopus.Server.Web.OctopusNancyHost.Start() in Y:\Work\refs\tags\3.3.27\source\Octopus.Server\Web\OctopusNancyHost.cs:line 139
at Octopus.Server.Web.WebServerInitializer.Start() in Y:\Work\refs\tags\3.3.27\source\Octopus.Server\Web\WebServerInitializer.cs:line 57
at Octopus.Server.OctopusServerEngine.Start() in Y:\Work\refs\tags\3.3.27\source\Octopus.Server\OctopusServerEngine.cs:line 48
at Octopus.Server.Commands.RunCommand.Start() in Y:\Work\refs\tags\3.3.27\source\Octopus.Server\Commands\RunCommand.cs:line 37
at Octopus.Shared.Startup.AbstractCommand.Octopus.Shared.Startup.ICommand.Start(String[] commandLineArguments, ICommandRuntime commandRuntime, OptionSet commonOptions) in Y:\Work\refs\tags\3.3.27\source\Octopus.Shared\Startup\AbstractCommand.cs:line 57
at Octopus.Shared.Startup.OctopusProgram.Start(ICommandRuntime commandRuntime) in Y:\Work\refs\tags\3.3.27\source\Octopus.Shared\Startup\OctopusProgram.cs:line 221
at Octopus.Shared.Startup.WindowsServiceHost.<>c__DisplayClass1_0.b__0() in Y:\Work\refs\tags\3.3.27\source\Octopus.Shared\Startup\WindowsServiceHost.cs:line 19
at Octopus.Shared.Startup.WindowsServiceAdapter.RunService() in Y:\Work\refs\tags\3.3.27\source\Octopus.Shared\Startup\WindowsServiceAdapter.cs:line 64
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

2

Hi Joe,

Thanks for reaching out! The problem seems to be that you have both the Octopus Server publishing the web portal, and the Octopus Tentacle listening on the same port 443. You cannot have both services using the same port at the same time.

Changing the port they use should solve this issue right away.

Thanks!
Dalmiro