gatsby.dev connection refused by server

Created on 7 Mar 2019  Â·  14Comments  Â·  Source: gatsbyjs/gatsby

Description

gatsby.dev links are not visible

Steps to reproduce

open the link https://gatsby.dev/reproduction in browser

Expected result

redirect to gatsbyjs manual

Actual result

Error: connection refused by server

Environment

gatsby info --clipboard

  System:                                                                                                                                                               
    OS: macOS High Sierra 10.13.6                                                                                                                                       
    CPU: (8) x64 Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz                                                                                                              
    Shell: 3.2.57 - /bin/bash                                                                                                                                           
  Binaries:                                                                                                                                                             
    Node: 11.9.0 - /usr/local/bin/node                                                                                                                                  
    npm: 6.8.0 - /usr/local/bin/npm                                                                                                                                     
  Languages:                                                                                                                                                            
    Python: 2.7.15 - /usr/local/bin/python                                                                                                                              
  Browsers:                                                                                                                                                             
    Chrome: 72.0.3626.121                                                                                                                                               
    Safari: 12.0.3                                                                                                                                                      
  npmGlobalPackages:                                                                                                                                                    
    gatsby-cli: 2.4.9        

All 14 comments

Note: there is no mention of gatsby.dev in the docs if i search for it

My awesome co-worker @jlengstorf has some ideas here.

Do you have any local aliasing or other set up which could be preventing access to .dev domains? Can you visit, e.g. https://nodejs.dev?

Which browser are you using?

Note: there is no mention of gatsby.dev in the docs if i search for it

We're using it for error messaging, short links, etc. It wouldn't necessarily _need_ to be linked in our docs, but if there's a place that makes sense, we'd love a PR!

Note:

  • on iphone safari in the same wifi it works
  • chrome & safari not work

but on macos terminal its redirected to localhost

ping gatsby.dev
PING gatsby.dev (127.0.0.1): 56 data bytes                                                                                                                              
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.040 ms 

We're using it for error messaging, short links, etc. It wouldn't necessarily need to be linked in our docs, but if there's a place that makes sense, we'd love a PR!

because i google for it and found nothing mentioning the redirect ... even the doc search not

Do you have a redirect in /etc/hosts for any dev domains?

all .dev are routed to localhost

cat /etc/hosts
##                                                                                                                                                                      
# 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
> gatsby.dev                                                                                                                                                            
Server:         192.168.178.1                                                                                                                                           
Address:        192.168.178.1#53                                                                                                                                        

Non-authoritative answer:                                                                                                                                               
Name:   gatsby.dev                                                                                                                                                      
Address: 52.72.49.79

Yeah - so you've probably installed something or enabled something that routes .dev domains to localhost.

I'm not really sure how to best address this, because this is very much outside the realm of something we _can_ fix.

Have you done something like this by chance?

I used to have this configured locally so I could develop different projects at local "domains". I had done this using Dnsmasq — maybe you did something similar? https://passingcuriosity.com/2013/dnsmasq-dev-osx/

thx for the fast help:

scutil --dns
[...]
resolver #9                                                                                                                                                             
  domain   : dev                                                                                                                                                        
  nameserver[0] : 127.0.0.1                                                                                                                                             
  port     : 20560                                                                                                                                                      
  flags    : Request A records, Request AAAA records                                                                                                                    
  reach    : 0x00030002 (Reachable,Local Address,Directly Reachable Address)  
[...]

but i found it in directory /etc/resolver/

cat /etc/resolver/dev
# Lovingly generated by Pow                                                                                                                                             
nameserver 127.0.0.1                                                                                                                                                    
port 20560     

nice that pow have placed a comment

@muescha is the fix to just delete that file?

Glad you were able to mostly solve it--I'll close this out once you give the confirmation that this has, indeed, been solved.

renaming solved it - i can immediate use the links

Wonderful!

Thanks to @jlengstorf for the assist, and glad you were able to solve it @muescha!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rossPatton picture rossPatton  Â·  3Comments

ghost picture ghost  Â·  3Comments

hobochild picture hobochild  Â·  3Comments

totsteps picture totsteps  Â·  3Comments

dustinhorton picture dustinhorton  Â·  3Comments