pow not work when not connected to the network on Yosemite

[FireQQTW]

I used #452 to solve the problem Yosemite not work, But when I do not have a network connection to the Internet (wifi or a home network), my http://myapp.dev/ is no work, any suggestions?

[koenpunt]

NB. The official release of Pow (0.5.0) supports Yosemite without hacks.

[kevintom]

I have the same issue on the official release of Pow 0.5.0.

I never installed any hacks or forked branches.

Ran uninstall script to remove previous version, and then installed 0.5.0

Turning off wifi networking, pow stops working.

[koenpunt]

This is a limitation of the DNS resolver in OS X. I found that when I had the OS X Server application installed, I had no issues being offline. But that's not really a solution. Maybe there's a way to let OS X think there is a connection available..?

[gshaw]

Confirming that this is indeed a problem. I have clean install of 0.5.0 and have only installed the final Yosemite. I can't resolve .dev domains while offline.

A work around for others that are experiencing this issue is to manually update your /etc/hosts file with the .dev domains you want to point to 127.0.0.1. Example:

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1             localhost
127.0.0.1       mysite.dev

[kubens]

I have the same issue. After going offline pow 0.5.0 stop working. Yosemite from AppStore

[koenpunt]

No need to keep conforming. Is has been a longstanding issue: #104

[kubens]

@koenput after you install a OS X server, you can work offline?

[koenpunt]

Just tried, and I think it's not the case anymore. Or I had some settings changed previously, but I'm not sure about that.

[FireQQTW]

You can also install powder, and then run powder host to add to the hosts file, you can speed up a little bit. haha..

[jriff]

@koenpunt I just can't recall having this issue on Mavericks.

Can anyone confirm the issue on 10.9?

[kevintom]

this does not occur on my second mac running 10.9.5

but does occur on my primary mac running 10.10.

both machines are clean installs of stable releases only.

[lachlanjc]

Yep, not working on Yosemite here either. I have to boot up Puma and go to localhost:9292 when I'm not on Wi-Fi 😭

[benjaminwood]

This is happening to me also. Is this a known issue? Or is it only affecting some users?

Manually updating my host file does work and is a decent workaround until this is resolved.

[lenciel]

Having the same issue after updated to Yosemite. Any progress or workaround about this?

[benjaminwood]

@lenciel the only known workaround is adding your .dev domains to your hosts file. See @gshaw comment for further information.

[msroot]

Editing hosts its works but not with subdomains :(

[koenpunt]

You should add each subdomain to the hosts file

[msroot]

@koenpunt yes i ve done it and it works! but too much effort :(

[BrianGilbert]

Here is a video I made showing Yosemite's behaviour vs Mavericks'
https://www.youtube.com/watch?v=3m9OI_AjCx8

In my mind this is a bug in the way that DNS resolution behaves since the change to discoveryd

[benjaminwood]

The powder gem (pow manager) has a feature to update your hosts file with all your linked apps in a single command: powder host. Makes it a bit less painful. :-)

https://github.com/Rodreegez/powder

[Jamedjo]

powder doesn't add subdomains

On 24 April 2015 at 08:40, Benjamin Wood notifications@github.com wrote:

The powder gem (pow manager) has a feature to update your hosts file with
all your linked apps in a single command: powder host. Makes it a bit
less painful. :-)

https://github.com/Rodreegez/powder

—
Reply to this email directly or view it on GitHub
#471 (comment).

[davebell]

Yosemite 10.10.4 has done away with discoveryd. Out-of-the-box offline development with POW is back!

[benjaminwood]

Nice catch! This is great news!

[waynn]

I'm running 10.10.5 and I'm still seeing this problem -- if I have my wi-fi off, when I try to go to a pow domain, I get an error from Chrome. Anyone else having this problem? Or do I have to change some setting?