[Bug]: Can't start the remix server after stopping it
See original GitHub issueWhich Remix packages are impacted?
-
remix(Remix core) -
create-remix -
@remix-run/architect -
@remix-run/cloudflare-workers -
@remix-run/dev -
@remix-run/express -
@remix-run/netlify -
@remix-run/node -
@remix-run/react -
@remix-run/serve -
@remix-run/server-runtime -
@remix-run/vercel
What version of Remix are you using?
1.0.6
Steps to Reproduce
Start a remix server, working on the code, then stopping the server using ctrl +c and then starting it again
I’m using ubuntu 20.04 with nodejs 14.17 and yarn 1.22.15
Expected Behavior
It should restart the server again
Actual Behavior

Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:7 (1 by maintainers)
Top Results From Across the Web
[Bug]: Live Reload not working. · Issue #1601 · remix-run/remix
I have to stop the dev server and restart to see any changes ... This doesn't seem to work? i start up the...
Read more >Can't access new Remix app - Questions / Help - Fly.io
I have trouble getting my new app to run. It is a remix app with express. Here is my package.json { "private": true,...
Read more >Data Loading - Remix
Data Loading. One of the primary features of Remix is simplifying interactions with the server to get data into components.
Read more >After stopping the websphere server, canoot start it again ...
Starting websphere application server classic v8.5 at localhost has encountered a problem. Cannot connect to the server process. Make sure the ...
Read more >Error: listen EADDRINUSE :::3000. Remix works. Storage not full
But the server is still unable to start. Even after cleaning up the storage and running his recommended commands. I remixed the project, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

You can also kill the process on the port by
npx kill-port <port_number>here you can donpx kill-port 8002Yes! this is the same problem