SOLVED: Mac self-hosted action stopped connecting to job server in the last week #149350
-
Select Topic AreaBug BodySometime in the last week our self-hosted github action stopped working. It fails once it receives a job. It says that it is starting a job but then no further to the terminal. Digging into the logs, I can see that the problem is the worker is unable to connect to the server:
Running curl on that URL, I also am unable to connect to the server, however if I run nmap to the server, it sees that it can be reached:
We are running our action on a M2 Mac Mini. Our runner was installed on 14.7.2 when it was last running, and I have tried updating to 15.2. I have also tried making a new action worker, and even did so a third time, configuring it without TLS. Does anyone have advice? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Have seen this happen as well. |
Beta Was this translation helpful? Give feedback.
-
We figured it out. Our router, an eero max 7, had a recent update which saw the github action as an insecure application and blocked it. We disabled all of the router's built-in security features and our worker started running again. |
Beta Was this translation helpful? Give feedback.
We figured it out. Our router, an eero max 7, had a recent update which saw the github action as an insecure application and blocked it. We disabled all of the router's built-in security features and our worker started running again.