Stacktrace after login
We are currently having an error with an installation (v.0.27.1), maybe one of you have already encountered this issue:
After logging into the dashboard, we receive a stack trace with
uRe@https://example.com/assets/index-c8b5bf4c.js:320:28919
jR@https://example.com/assets/index-c8b5bf4c.js:320:28681
and so on...
The coder is running behind a reverse proxy with Apache.
Apache2 (example.com) --> Proxy Pass --> 127.0.0.1:3000 (coder)
In Coder, the access URL is defined as example.com.
Without Apache: It works when directly accessing the IP, i.e., changing the access URL and HTTP address in Coder to the server IP.
Without Apache: With the access URL as example.com and HTTP address on server IP, the exact same error comes up as with the Apache. So, the issue doesn't seem to be with Apache.
Has anyone encountered this problem before?
Edit: We are running behind a proxy in an internal network. Thus, for the Ubuntu machine where Coder is running, a no_proxy variable is set for example.com.
After logging into the dashboard, we receive a stack trace with
uRe@https://example.com/assets/index-c8b5bf4c.js:320:28919
jR@https://example.com/assets/index-c8b5bf4c.js:320:28681
and so on...
The coder is running behind a reverse proxy with Apache.
Apache2 (example.com) --> Proxy Pass --> 127.0.0.1:3000 (coder)
In Coder, the access URL is defined as example.com.
Without Apache: It works when directly accessing the IP, i.e., changing the access URL and HTTP address in Coder to the server IP.
Without Apache: With the access URL as example.com and HTTP address on server IP, the exact same error comes up as with the Apache. So, the issue doesn't seem to be with Apache.
Has anyone encountered this problem before?
Edit: We are running behind a proxy in an internal network. Thus, for the Ubuntu machine where Coder is running, a no_proxy variable is set for example.com.
