Run time issue with the Otter Web Service

ben

Ah, sorry, I misread. The web service is what's having problems starting, so this would be the command instead:

cd "C:\Program Files\Otter\Service"
.\Otter.Service.exe run --mode=webonly

Guest

Attempting to execute - it is taking a while and only showing me a blinking cursor...

ben

Are you able to access the Otter web UI while it's running?

Guest

No I am not. I am shown this page:

This page can’t be displayed

Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://localhost:8626 again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4 (link for the details), which is not considered secure. Please contact your site administrator.

atripp

Does it work with http://localhost:8626? I don't think the standalone web server does its own TLS.

Guest

Yes! That worked. However, the Otter Web Server service still is not running.

ben

Ok, that means that the web service is able to run with the permissions you have when you elevate.

If the web service is running with restricted permissions, it might not be able to access something it needs to start up.

As far as I know, it needs read/write access to C:\ProgramData\Otter, read access to C:\Program Files\Otter, and the ability to communicate over the named pipe otter-ctrl.

Guest

Thanks. I would have thought Local System would have all of those. I will double check.

Guest

Ok, I have to punt here. I am not able to check the permissions on the otter-ctrl named pipe as I am not able to find it. Perhaps it is just ignorance on my part. I have attempted to run it as Network Service as well as creating a new local Admin account. No joy there either. I feel like there is a solution but it is eluding me. If there is anything else I can try, I am all ears.

Guest

Are you saying, that you can access the Otter Web UI, but the Otter Web service isn't working?

In this case, I think you must have Otter Web running through IIS. Which, is ok, so you don't need to worry about the web Service.

Guest

Alana - appreciate it. I am going to verify that. It would make sense I supposed, I just was expecting it run since it was present. I guess I missed that in the documentation. Anyhow, thanks again and I will let you know what I find out (may be next week though).

Guest

Ok, when I install IIS and run Otter in this manner, this is what I receive:
HTTP Error 403.14 - Forbidden. The Web server is configured to not list the contents of this directory.
Most likely causes: A default document is not configured for the requested URL, and directory browsing is not enabled on the server.

I can enable directory browsing and browse, however, I do not see the GUI.

This is the case on both Windows 2012 R2 as well as Windows 2016. I also upgraded from Otter 2.0.5 to 2.0.6. Working on uninstalling everything and making sure to reinstall everything as administrator (even though I am logged in as an admin) to see if that makes a difference.

atripp

It sounds like you don't have ASP.NET enabled as a role on your Windows server. The installer should detect it, but that checkmay have failed. Hard to say.

In the Server Manager feature of Windows, make sure to select ASP.NET 4.5 (or whatever the latest version is), by expanding the Application Development node.

Guest

Doubled checked and verified that ASP.NET 4.5 (or later) is already installed.