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

DNS Server failed: listen tcp 127.0.0.1:9253: bind: address already in use error when starting the app with puma-dev command #334

Open
oleksandr-danylchenko opened this issue Mar 16, 2023 · 3 comments

Comments

@oleksandr-danylchenko
Copy link

oleksandr-danylchenko commented Mar 16, 2023

I have the ~/.puma-dev folder config where one of the entries points to the folder with the app. So it automatically starts on ports :80 and :443 under webtexts.localhost domain:
image

I also want to run the puma-dev explicitly from the linked webtexts folder using the puma-dev --http-port 3333 --https-port 4444 command. I hope will allow me to access the underlying application from the mobile device via localhost:3333.

Unfortunately, on the command execution, I get such an error:

2023/03/16 12:23:54 Existing valid puma-dev CA keypair found. Assuming previously trusted.
* Directory for apps: /Users/oleksandr_danylchenko/.puma-dev
* Domains: test
* DNS Server port: 9253
* HTTP Server port: 3333
* HTTPS Server port: 4444
! Puma dev running...
! DNS Server failed: listen tcp 127.0.0.1:9253: bind: address already in use

Even after I ran the puma-dev -stop and tried the command above - I got the same error. Here's the output of the lsof -i :9253 right after the puma-dev -stop:
image

Is it safe to kill the process running on the :9253? Can it be mitigated in a more "civilized" way?


P.S. I'm running the app on MacOS 13.2.1

@oleksandr-danylchenko
Copy link
Author

Moreover, even after killing the processes on 9253, the puma-dev revives immediately
image

@ozgurtezel-kitmanlabs
Copy link

Is there a solution for this issue? I run into the same problem on MacOS 14.6

@oleksandr-danylchenko
Copy link
Author

Is there a solution for this issue?

IIRC, rebooting the Mac mitigates the issue for some time. But it can randomly reappear 🤷🏻‍♂️

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

No branches or pull requests

2 participants