This repository has been archived by the owner. It is now read-only.

pow not work when not connected to the network on Yosemite #471

Open
FireQQTW opened this Issue Oct 19, 2014 · 24 comments

Comments

Projects
None yet
@FireQQTW

FireQQTW commented Oct 19, 2014

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

This comment has been minimized.

Show comment
Hide comment
@koenpunt

koenpunt Oct 19, 2014

Contributor

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

Contributor

koenpunt commented Oct 19, 2014

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

@kevintom

This comment has been minimized.

Show comment
Hide comment
@kevintom

kevintom Oct 22, 2014

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.

kevintom commented Oct 22, 2014

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 comment has been minimized.

Show comment
Hide comment
@koenpunt

koenpunt Oct 22, 2014

Contributor

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..?

Contributor

koenpunt commented Oct 22, 2014

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

This comment has been minimized.

Show comment
Hide comment
@gshaw

gshaw Oct 22, 2014

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

gshaw commented Oct 22, 2014

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

This comment has been minimized.

Show comment
Hide comment
@kubens

kubens Oct 23, 2014

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

kubens commented Oct 23, 2014

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

@koenpunt

This comment has been minimized.

Show comment
Hide comment
@koenpunt

koenpunt Oct 23, 2014

Contributor

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

Contributor

koenpunt commented Oct 23, 2014

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

@kubens

This comment has been minimized.

Show comment
Hide comment
@kubens

kubens Oct 23, 2014

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

kubens commented Oct 23, 2014

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

@koenpunt

This comment has been minimized.

Show comment
Hide comment
@koenpunt

koenpunt Oct 23, 2014

Contributor

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.

Contributor

koenpunt commented Oct 23, 2014

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

This comment has been minimized.

Show comment
Hide comment
@FireQQTW

FireQQTW Oct 23, 2014

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

FireQQTW commented Oct 23, 2014

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

This comment has been minimized.

Show comment
Hide comment
@jriff

jriff Oct 28, 2014

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

Can anyone confirm the issue on 10.9?

jriff commented Oct 28, 2014

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

Can anyone confirm the issue on 10.9?

@kevintom

This comment has been minimized.

Show comment
Hide comment
@kevintom

kevintom Oct 28, 2014

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.

kevintom commented Oct 28, 2014

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

This comment has been minimized.

Show comment
Hide comment
@lachlanjc

lachlanjc Nov 12, 2014

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 😭

lachlanjc commented Nov 12, 2014

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 comment has been minimized.

Show comment
Hide comment
@benjaminwood

benjaminwood Nov 21, 2014

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.

benjaminwood commented Nov 21, 2014

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

This comment has been minimized.

Show comment
Hide comment
@lenciel

lenciel Dec 30, 2014

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

lenciel commented Dec 30, 2014

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

@benjaminwood

This comment has been minimized.

Show comment
Hide comment
@benjaminwood

benjaminwood Dec 30, 2014

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

benjaminwood commented Dec 30, 2014

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

@msroot

This comment has been minimized.

Show comment
Hide comment
@msroot

msroot Mar 20, 2015

Editing hosts its works but not with subdomains :(

msroot commented Mar 20, 2015

Editing hosts its works but not with subdomains :(

@koenpunt

This comment has been minimized.

Show comment
Hide comment
@koenpunt

koenpunt Mar 22, 2015

Contributor

You should add each subdomain to the hosts file

Contributor

koenpunt commented Mar 22, 2015

You should add each subdomain to the hosts file

@msroot

This comment has been minimized.

Show comment
Hide comment
@msroot

msroot Mar 23, 2015

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

msroot commented Mar 23, 2015

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

@BrianGilbert

This comment has been minimized.

Show comment
Hide comment
@BrianGilbert

BrianGilbert Apr 23, 2015

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

BrianGilbert commented Apr 23, 2015

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

This comment has been minimized.

Show comment
Hide comment
@benjaminwood

benjaminwood Apr 24, 2015

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

benjaminwood commented Apr 24, 2015

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

This comment has been minimized.

Show comment
Hide comment
@Jamedjo

Jamedjo Apr 24, 2015

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).

Jamedjo commented Apr 24, 2015

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

This comment has been minimized.

Show comment
Hide comment
@davebell

davebell Jun 30, 2015

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

davebell commented Jun 30, 2015

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

@benjaminwood

This comment has been minimized.

Show comment
Hide comment
@benjaminwood

benjaminwood Jun 30, 2015

Nice catch! This is great news!

benjaminwood commented Jun 30, 2015

Nice catch! This is great news!

@waynn

This comment has been minimized.

Show comment
Hide comment
@waynn

waynn Sep 28, 2015

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?

waynn commented Sep 28, 2015

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?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.