-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Incorrect root url detection for WebSocket with any non-root url path #101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I can also see that getting the webpack_hmr is failing because it looks for it in the host root. |
I'm having the exact same problem. Nginx is set up to run a reverse proxy under a Outside of using e.g. a subdomain and an entirely new Nginx site, I don't see a feasible solution for this; and I imagine having VSCode exist as a sub-directory may be a common setup. |
Ah I know the issue. Updating https://github.com/codercom/code-server/blob/master/packages/ide/src/fill/client.ts#L95 to contain the browser URL should fix this. |
This seems to have been fixed by #149 Have built a fresh image from upstream and tested the same setup that was previously broken - all working. |
i have pulled the latest image from https://hub.docker.com/r/codercom/code-server
sample docker-compose file
|
Works well with that fix: https://twitter.com/betatim/status/1106195567892402177 |
i have pulled the latest image again this morning from https://hub.docker.com/r/codercom/code-server (March 15, 2019 05:19 AM) and im still getting the 404 error ? |
@si458 Odd, as that fix seems to be included in the latest release: Are you sure it's the same issue / able to post your nginx config? |
@MrDetonia i dont use nginx?
|
@si458 as I understand it, this issue was specific to using a reverse proxy with nginx (see OP). You may be seeing some other issue that is unrelated. |
@MrDetonia your are correct, sorry ill tag onto the other issue thats been closed but it needs re-opening as its still an issue |
I believe this is fixed. cc: @code-asher |
Yup, the websocket uses the same URL that serves |
code-server
version: 1.0.0Steps to Reproduce
Also, I did not find any documentation (or config in general) related to this type of deployment... guess that probably can be improved a bit?
The text was updated successfully, but these errors were encountered: