-
Notifications
You must be signed in to change notification settings - Fork 1
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
Can not connect to sites without VPN #1209
Comments
That sounds very weird, indeed! My assumption is that the VPN app is maybe controlling it's own DNS server/dnsmasq instance? Could you see if (when Herd is not running) anything is running on the default dnsmasq port?
When Herd is running, it should look something like this:
|
Thanks for helping (i am not very at home at these things — i am more of a designer who love to toy around with building websites) This is what i got when Herd is active.
Doing the sudo lsof -i :53 again when Herd is not running, it returns nothing. |
Okay that sounds right to me. Can you simply try and run ping foo.test In your terminal once Herd is running? Does that resolve to 127.0.0.1? |
Once Herd is running it states:
|
Thank you for your help so far! I think I’ve got it working again. It turned out Docker was the issue. I had installed Docker and tried stopping it, but that didn’t help. The only difference from yesterday? No Docker was installed. So, I deleted Docker and rebooted. Now I can connect to my Odd! A friend of mine, who’s really into Docker and networking, is visiting in a few days. I’ll share his thoughts here once he takes a look. |
Platform
macOS
Operating system version
Macos
System architecture
Intel (x86)
Herd Version
1.13.0
PHP Version
php 8.28
Bug description
Hello there.
For some reason none of my herd sites are working anymore. Unless i connect to the web via a vpn.
I tried to uninstall the VPN app, reboot, to no avail.
I tried to install the herd app again, reboot, to no avail.
Baffled how to fix this.
Thank you.
Steps to reproduce
Open herd website in browser
Relevant log output
No response
The text was updated successfully, but these errors were encountered: