-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
/__webpack_hmr 404 #141
Comments
Will be fixed! |
#149 shouldn't have fix this. This is related to a build issue w/ webpack. |
Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-1030-azure x86_64)
Response Code: 404 <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot GET /__webpack_hmr</pre>
</body>
</html> |
Check masteR branch, not generate release |
I wanted to clarify your comment - are you saying that the fix is in the master branch but not in e.g. the 1.32.0-245 release or do you mean earlier releases? I'm trying to proxy code-server in JupyterHub (data science tool). I'm still getting
using the 1.32.0-245 release binaries. I'm building my environment as in https://gist.github.com/dirkcgrunwald/d3d5669e291e8249f5b4f6ad8b6c1f46 I haven't tried building from source because my other tools need node 11.11.0 |
i have pulled the latest image from https://hub.docker.com/r/codercom/code-server
sample docker-compose file
|
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 Your browser doesn't seem to be able to connect to the server at all, do you see anything at all, or just the no __webpack_hmr? |
It seems to work fine, loads up ok but keep seeing the 404 error in the web console for the web pack file |
I've seen this error and solved it with another project - will update when I can track down this with either: - Solution
- Comment removal if unable to find it |
Any update for this issue? |
code-server
version: master branchSteps to Reproduce
The text was updated successfully, but these errors were encountered: