I'm having the following error when trying to authenticate using the Ignition IDP:
This appears immediately after clicking log in, before the IDP even asks for a username/password.
This is only happening on the master. The redundant is fine.
Any ideas on how to troubleshoot?
It's not exposed to the internet, but should probably redact that anyway
Additional info:
This doesn't appear to generator any info in the wrapper.log. I've replicated the issues a few times, with no new entries.
(Yes, the server has been rebooted)
Where are you logging into? Gateway Web Interface (Home/Status/Config)? Perspective? other (please specify)?
You mentioned a redundant setup... are you logging into the master? backup? Is your system currently failed over to the backup when you attempt login?
503 usually means the target gateway is not started (in the process of starting up, shutting down, or was unable to startup due to some error which should be clear from the gateway logs)
Check the host/port in the URL that you are getting a 503 back and make sure it is pointing to the Gateway you expect to be logging in at the time (for example: if you are failed over to the backup and backup is active, the host/port should be pointing to the backup).
Same result for Gateway web interface and Perspective sessions.
Logging in to the master fails in this fashion, both while it is active and after failing over to the redundant server.
The gateway itself is running when this error occurs, as I can see tags updating to the historian. Is there a component that is not started properly.
The host/port that I'm getting this 503 is the gateway:8043. That resolves properly. I don't really know what else to check.
I will send the logs to support.
Looks like Ignition will also return a 503 if too many requests are bombarding a specific URL concurrently. Is this a high traffic Gateway? Are lots of users logging in and out constantly?
By default, /data/federate/callback will accept 5 concurrent requests. Any additional requests will stand in line for about 2 seconds before giving up and throwing a 503 error. You can try increasing these values using these sysprops:
ignition.routes.defaultConcurrency (defaults to 5)
ignition.routes.defaultRequestTimeout (defaults to 2000 ms)