Bug: time to time goes to :8443 behind aws lb -> nginx ingress -> vectr

[marcispauls]

Describe the bug
Time to time we face that running VECTR behind nginx as ingress in AWS it tries to load assets/js/apis on :8443 even we have configured:

VECTR_HOSTNAME = vectr.example.com
VECTR_PORT              = 8443
VECTR_EXTERNAL_HOSTNAME = vectr.example.com
VECTR_EXTERNAL_PORT     = 443

To Reproduce
Steps to reproduce the behavior:

1. setup k8s with nginx ingress
2. create service in k8s which points to caddy-gateway:8443
3. create ingress on 443 which points to that service
4. Some assets tries to load from 8443 like /static/icons/ /static/ /sra-purpletools-webui/app/ /sra-purpletools-rest/ etc

Expected behavior
Should respect everywhere whats in VECTR_EXTERNAL_HOSTNAME and VECTR_EXTERNAL_PORT

User Platform(please complete the following information):

• OS: windows
• Browser: Chrome
• Version: 130

VECTR Host(please complete the following information):

• Linux Distro: Docker
• Linux Version: Docker
• VECTR Version 9.4.0

[p-b--]

We don't offer support Kubernetes for VECTR community edition. We know users have successfully deployed VECTR to such environments and others are welcome to comment if they have suggestions if they would like. I will mark support for such deployments as a feature request.

[p-b--]

If you do find that you can replicate this issue in our supported set up (via the docker compose), please let us know and we can investigate further.

What would also help would be a list of the exact requests that get made against the other port (you don't need to include credential info).

[marcispauls]

I will replicate the issue with docker-compose, but that will be next week