Skip to content
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

Full nuxt restart doesn't close websocket server #1935

Closed
killjoy1221 opened this issue Feb 27, 2023 · 0 comments · Fixed by #1952
Closed

Full nuxt restart doesn't close websocket server #1935

killjoy1221 opened this issue Feb 27, 2023 · 0 comments · Fixed by #1952

Comments

@killjoy1221
Copy link

Environment

N/a

Reproduction

Happens on the minimal template, no changes

Describe the bug

Modifying nuxt.config.ts and triggering a full reload will open a new websocket port, but leave the old one open. The more you reload the server, the higher the ports get: 4000, 4001, 4002, etc.

Additional context

Attempts to connect to the old ports via wscat -c localhost:4000 results in a 503 error.

Logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant