The Octopus Service is currently stopped

Legacy Uncategorised
1

Windows Server 2012 R2. Server is not in domain.I try to run a service under a local account. Service stops immediately.
If I add the account in local administrators group it can start. But it’s not a workaround because I need to start a service with least privileges.

Application log errors:

2015-10-30 14:44:12.8022 7 FATAL The HTTP server could not start because namespace reservations have not been made. Ensure that the current user has access to listen on these prefixes by running the following command(s):
netsh http add urlacl url=https://+:443/ user=server\user

System.Exception: The HTTP server could not start because namespace reservations have not been made. Ensure that the current user has access to listen on these prefixes by running the following command(s):
netsh http add urlacl url=https://+:443/ user=server\user

2015-10-30 14:44:12.8272 7 FATAL Unhandled AppDomain exception occurred: The HTTP server could not start because namespace reservations have not been made. Ensure that the current user has access to listen on these prefixes by running the following command(s):
netsh http add urlacl url=https://+:443/ user=server\user

System.Exception: The HTTP server could not start because namespace reservations have not been made. Ensure that the current user has access to listen on these prefixes by running the following command(s):
netsh http add urlacl url=https://+:443/ user=server\user

There is no other services on server that listen 443 port.

“netsh http add urlacl url=https://+:443/ user=server\user” command works correctly with administrator’s privileges.

What should I do?

2

Hi,

Thanks for getting in touch. When you say you are running this service under a “Local account” do you mean the “Local system account”? (see attached screenshot). If its not and its a Local account you created yourself, what permissions does this account have?

Regards,

Dalmiro

3

Hi, Dalmiro.

No. Local account is not a Local System account. It’s a local user.

This user has a full control on a service folders and “Log on as a service” permissions.

4

The issue has been solved.

I’ve registered manually "url=https://server.domain.com:443 " instead of "url=https://+:443 ". The service has started.

Do you have any ideas what is the reason of this behavior?