Atlantis terraform live logs are not showing

[Abhilash-sandupatla]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Hai, I can able to plan and apply atlantis, working fine. But, i want to see terraform live logs, when it is planning/applying.
I know, that when we click on builds in bitbucket pr, it directs to browser, where it shows terraform logs. But, in my case, I see a page with blank. I am attaching the screenshot of the blank page.

VCS I am using - bitbukcet.
deployed through:- helm charts in eks

Reproduction Steps

Logs

Environment details

Additional Context

[cheddarBiscuit]

I also saw the blank screen for live logs. I noticed an error like writing to ws <id>: upgrading websocket connection: websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header. Once I migrated our load balancer from an AWS Classic Load Balancer to an AWS Application Load Balancer, the live logs appeared. Hope this helps!

[tomharrisonjr]

Issue for us was that we were using a custom workflow ... and the reason we were doing that was that we use the .terraform.lck.hcl file to ensure the versions we commit locally are the ones used when we build remotely. Except that we code on macos and build on linux, and default workflow observes the values in the lockfile.

**Solution: **

• Remove custom workflows, and
• as per https://www.terraform.io/cli/commands/providers/lock

terraform providers lock \
  -platform=darwin_arm64 \ # 64-bit macOS silicon / M1
  -platform=darwin_amd64 \  # 64-bit macOS intel
  -platform=linux_amd64 \    # 64-bit Linux
  -platform=linux_arm64      # 64-bit Linux "graviton"

[Abhilash-sandupatla]

I also saw the blank screen for live logs. I noticed an error like writing to ws <id>: upgrading websocket connection: websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header. Once I migrated our load balancer from an AWS Classic Load Balancer to an AWS Application Load Balancer, the live logs appeared. Hope this helps!

I also saw the blank screen for live logs. I noticed an error like writing to ws <id>: upgrading websocket connection: websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header. Once I migrated our load balancer from an AWS Classic Load Balancer to an AWS Application Load Balancer, the live logs appeared. Hope this helps!

This worked. When we changed atlantis from clb to alb. Atlantis shows live logs on UI.
Thanks @cheddarBiscuit cheddarBiscu

[omotoso78]

I also experience a blank detail screen for my live logs on the Atlantis server UI.
I installed atlantis v0.19.7, local installation and git enterprise. None of the suggested solutions applies to me

[MattMencel]

Nice.... thanks for the hint about websockets! That was the answer. The solution depends on your Ingress/LB. e.g. for Emissary Mappings you just have to allow the websockets upgrade.

https://www.getambassador.io/docs/emissary/latest/howtos/websockets

Maybe the docs should add a note about websockets?

[jamengual]

PRs are welcome for the Docs.

[nitrocode]

This seems to be a duplicate of

#2026
#2129

We can add docs to one of the older issues instead of this one so ill close this issue to help consolidate discussion there.

[ldunkum]

For future reference and for anybody deploying Atlantis on k8s with traefik, we just had to add a custom middleware to our ingress routes to fix this issue:

---
apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: atlantis-headers
  namespace: atlantis
spec:
  headers:
    customRequestHeaders:
      X-Forwarded-Proto: "https"