This message was deleted.
# atlantis-community
s
This message was deleted.
j
It usually means that your load balancer or ingress is not configured to allow websocket connections
p
Ι am hitting the public IP of the VM directly
nothing in-between
j
I had this issue (AWS ALB -> nginx container in ECS Fargate -> atlantis container in fargate) It was the headers not being set correctly for me between nginx and atlantis. If you look at the debug console in chrome or whatever browser you should see more information about what is happening.
p
Copy code
Mixed Content: The page at '<https://11.22.33.44:1122/jobs/job-id>' was loaded over HTTPS, but requested an insecure element '<https://11.22.33.44:1122/static/images/atlantis-icon_512.png>'. This request was not upgraded to HTTPS because its URL's host is an IP address.
I see this error in Chrome Console
Where
11.22.33.44
is the IP of the VM and
1122
the custom port I am using for
atlantis
Αnd this
Copy code
Canvas2D: Multiple readback operations using getImageData are faster with the willReadFrequently attribute set to true. See: <https://html.spec.whatwg.org/multipage/canvas.html#concept-canvas-will-read-frequently>
those are the only errors (warnings to be precise)
j
I see from the previous thread that you have already set the ATLANTIS_ATLANTIS_URL. Is the url in the link to the logs what you would expect it to be?
p
yes it is. The
Details
link in GH works
it gets me to the right page with the right logs
they are just not real-time/streamed