How did I investigate Admin and Seq are not working?
Knowledge shared by Oren
Wanted to share with you an issue I had with 19.5.1 installation, how I investigated, and what was the solution.
So we installed today Wyndham server.
Hosted on our AWS (separate network), outside domain, user password authentication, local DB.
DNS name is defined as a global DNS record: WyndhamAWS1.KryonSystems.com .
All Services are up and running.
First symptom: Admin shows error on launch (same error like the Aerobase service is down).
Second symptom: SEQ it not accessible through http:///Seq but it is accessible through http://localhost:5341 (internal port).
So it feels like something is wrong with nginx, which is the front line for both SEQ and Aerobase. If nginx is down, Admin will behave like Aerobase is down.
Checking: Nginx service is up and running.
I tried to stop the nginx service, and run the nginx.exe manually, hopefully to get some exception information. Nothing. All is working.
I get out from the server machine, and try to browse to SEQ from my own private machine: http:///Seq . does not work. Same result as from within the server.
I try to ping the FQDN from my machine – the DNS record translated correctly to the correct IP address. So it is not a problem with DNS record.
So maybe port 80 is not opened in the AWS firewall?? I checked with Devops – it is open.
So what's left..?
Aha! Windows Firewall is turned on. Blocking all ports. Way to go Microsoft.
Turned off Windows firewall – all is working.
