You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using create-remix without a template and the following selection:
Just the basics
Cloudflare Workers
Typescript
No npm install
After starting the dev server with npm run dev, both Firefox and Safari cannot connect to the dev asset server web socket.
Expected Behavior
Browser should be able to connect to web socket.
Actual Behavior
Browser attempts to reconnect to web socket unsuccessfully.
The remix.config.js setting devServerPort is ignored in my barebones project (no changes made).
Observation
After saving any file in the app folder (which triggers either 2 or 3 [mf:inf] Worker reloaded! (0.50MiB) messages for me) AND subsequently reloading the page in the browser, the browser can connect to the web socket.
However, after worker reloaded 2 or 3 times, it falls back to port 8002 by itself. As I said above, this does not depend on the devServerPort setting; it falls back to 8002 either way.
The text was updated successfully, but these errors were encountered:
@feljx if you are using vs code in remote mode, try to add WebSocket port (e.g. 56754 in your case) manually under ports>add ports - this will forward the port for you. You can also use devServerPort in the remix config ws port to set and ensure the manually forwarded port won't change
to change the application server port, you can use PORT=.... in .env, note that this is the application port, not the socket
What version of Remix are you using?
1.7.6
Steps to Reproduce
Using
create-remix
without a template and the following selection:After starting the dev server with
npm run dev
, both Firefox and Safari cannot connect to thedev asset server web socket
.Expected Behavior
Browser should be able to connect to web socket.
Actual Behavior
Browser attempts to reconnect to web socket unsuccessfully.
The
remix.config.js
settingdevServerPort
is ignored in my barebones project (no changes made).Observation
After saving any file in the
app
folder (which triggers either 2 or 3[mf:inf] Worker reloaded! (0.50MiB)
messages for me) AND subsequently reloading the page in the browser, the browser can connect to the web socket.However, after worker reloaded 2 or 3 times, it falls back to port
8002
by itself. As I said above, this does not depend on thedevServerPort
setting; it falls back to8002
either way.The text was updated successfully, but these errors were encountered: