Open
Description
Is there an existing issue for this?
- I have searched the existing issues
What is the current behavior?
The web interface listens only to HTTPS at 443
What is the expected behavior?
In many enterprise deployments SSL termination is usually done at a reverse proxy - nginx notably, and also there the real URL is configured. Testsigma should expose a plain HTTP listener, and should not try to guess what the URL of the server is, but rather expose it as a configurable env var.
Steps To Reproduce
- Installation.
Version
Testsigma Community Edition