Server doesn't process requests when started as service, but does when started from command line

[adobeDan]

Problem: Customer plans to move to FRL Online Proxy. They have version 1.1.0 installed on a W2K16 Server Version 1607 / Build 14393.4467. The customer reports that the service is running but does not hand the request forward to our servers. In the proxy log there are no proxy server requests. When they manually execute the frl-proxy.exe in the command line then the request is handed through the proxy to Adobe correctly. The service runs in the local user account.

Customer deployed new script provided but still observes the same behaviour.

Result: No connection to Adobe Servers. No entries in error log

Expected: FRL Online Proxy functional

Logs and other: frl-online-files.zip

Logs with the new script is exactly the same as before. proxy-service-stderr.log and proxy-service-stdout.log are empty

[mrichter-adobe]

Hi @adobeDan there is the console output when stopping and restarting the service:

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. Alle Rechte vorbehalten.

PS Y:\> c:
PS C:\> cd .\frl-proxy\
PS C:\frl-proxy> .\service.ps1 remove
FRL Online Proxy: STOP: Der Vorgang wurde erfolgreich beendet. _(The process terminated successfully)_
Service "FRL Online Proxy" removed successfully!
PS C:\frl-proxy> .\service.ps1 start
Service "FRL Online Proxy" installed successfully!
Set parameter "AppStdout" for service "FRL Online Proxy".
Set parameter "AppStderr" for service "FRL Online Proxy".
FRL Online Proxy: START: Der Vorgang wurde erfolgreich beendet.  _(The process terminated successfully)_

[adobeDan]

Hi @mrichter-adobe, thanks for the console output. I need to do some testing on my side but I suspect the problem is that when running as a local service there is no access to the network so no incoming requests are being received. (This may also be an issue with the firewall on that machine blocking access.) I will have more for you when I've had a chance to test.

[mrichter-adobe]

Hi @adobeDan Thanks. Did you already had the chance to test it? We also checked that the local system account has access to the service and there is no GPO blocking this.

[adobeDan]

@mrichter-adobe So I'm only partially through my testing, but I believe that the problem may be the use of the hostname in the proxy's configuration file (for the IP to be listened on). There may be a bug in the proxy with that configuration. Can you try again, using 0.0.0.0 as the Host IP address to be listened on? (That means every address for the server box; if there is a specific IP that you want to listen on you can instead use that.)

If it doesn't work as a service with that configuration, try turning off SSL and using a browser to visit the host/port; see if that gets you a response. If it does, then the problem is with the SSL certificate setup.

If it still doesn't work as a service with SSL off, try using 127.0.0.1 as the server address (localhost), turn off SSL (so it listens on port 8080), and try using curl (or a browser) on the server machine to make a connection to http://127.0.0.1/status. That should at least get you something in the log when running as a service.

Sorry this is proving so tricky. Please let me know what you find.

[mrichter-adobe]

@adobeDan Thanks a lot. I go the message back that setting host to 0.0.0.0 resolves the issue and it is now up and running. The customer suggested to add this to the documentation for the future. Thanks for your help

[adobeDan]

Hi @mrichter-adobe: Great! Thanks for letting us know. We will definitely add to the docs, and probably we should have the proxy check this in the configuration step as well.

[adobeDan]

I've retired so I'm un-assigning myself from this issue.