Err_connection_closed

Hi – I’m trying to access a site, https://answers-product-search.netlify.app/. Deploy preview works fine, publish went through successfully, however I’m experiencing what I believe to be is a DNS issue.

I’ve tried in incognito and in other browsers, no luck. Next, I followed the instructions listed on Connection to site refused and I get the following output from my dig:

r@MacBook-Air ~ % dig https://answers-product-search.netlify.app/ +trace

; <<>> DiG 9.10.6 <<>> https://answers-product-search.netlify.app/ +trace
;; global options: +cmd
.			518400	IN	NS	a.root-servers.net.
.			518400	IN	NS	b.root-servers.net.
.			518400	IN	NS	c.root-servers.net.
.			518400	IN	NS	d.root-servers.net.
.			518400	IN	NS	e.root-servers.net.
.			518400	IN	NS	f.root-servers.net.
.			518400	IN	NS	g.root-servers.net.
.			518400	IN	NS	h.root-servers.net.
.			518400	IN	NS	i.root-servers.net.
.			518400	IN	NS	j.root-servers.net.
.			518400	IN	NS	k.root-servers.net.
.			518400	IN	NS	l.root-servers.net.
.			518400	IN	NS	m.root-servers.net.
.			518400	IN	RRSIG	NS 8 0 518400 20210125050000 20210112040000 42351 . HHd7qwdZWEMKZwHBoo7LdP6u13hsF39p/Io3P78/qzU6pbXJqWc2BafV 6usv3mnvc6EYSZCFazA9ixk0QnGdCEWoZypswEdssiSbYBzL9+vkxwdM NTyNUawYyUkv6e+4EmLJ6/dkMO1TYU7/N9lsSmR67ko1M+BXyTzN9eBu 5DRkARi+JAwORZKt9fNntpPg8oMeU25jwFfMOQsZ5KYmYZQiy+KLfruD vYmCqhVa9ossX5iE4+oRAF5GeQvMaYfvwbNkqwrb2pktSu5RTRcy14en fGsfk+23GQjnZSWLj8e7cu6Nhem4cMmdBswEC/LOtrcMYmhFHaSeNkgM QBb1Vg==
;; Received 706 bytes from 127.0.0.1#53(127.0.0.1) in 67 ms

.			86400	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2021011200 1800 900 604800 86400
.			86400	IN	RRSIG	SOA 8 0 86400 20210125050000 20210112040000 42351 . AWP4OmRfFFNJ2AtXj53kOM0JvjRL8nfv0HN1W6Rv6qMCSR7c8UoMcQm0 KEDbemxItev5gHjcUWJvd9n/0wOxyolQFgw4vYUjw53V4KUUad7MCXiz C9V8BWQTCRCXMnvvaoF1bD0niCVr0nf0m3G0/mrjVIm+eHKpJDYswO+W pG4Ahbu5NTsvqMY3y1neFJfln0sCvd+XTD9i8fccWc3CtLSwTUGiWfsL JHrTp20VTx3GjsWrxNxWYDvurDk3CIiEdlyP/s3yCQkD09er+XX4hltb XlBPz7vCNMDliOGBnVzoB0MZibBgCDFlUrPC7gVSneNG6xNjikHEn20/ ZBfbjw==
.			86400	IN	NSEC	aaa. NS SOA RRSIG NSEC DNSKEY
.			86400	IN	RRSIG	NSEC 8 0 86400 20210125050000 20210112040000 42351 . ioeKWWSgUtsEUEEsTUAKBzx5hHWsufQezv/f4B7L050b5BKSO7e7ZJrw JfCuerQxRKsG/HN0n0/oOlvUQGIVfbQ8prKD5SsY4a5cc9T3sf2BAiht DRY4LgMQLCui7yVIJKUiqqB1Qiep3foDAJDITyfayVIDunYSm3v6MDIZ FTDcpMX9D0G2LjryY3G/OjLtWORMmjhTO5kMzg4BYfhYSURRCPSiazpR LQD8MgoysNjqfRRIZB2zdteBhJHtHO26/5cyI0Tktt3B7koZN6+7ktJZ SNcrZOHAM3wBOBQM5ZZjufJ/+79vTRS57if5I4dF6qQz/tgzrkol5B7A pfrL1Q==
app.			86400	IN	NSEC	apple. NS DS RRSIG NSEC
app.			86400	IN	RRSIG	NSEC 8 1 86400 20210125050000 20210112040000 42351 . YTkKEvoBAUulDApdlb6Fq6GLQuql/al2s5aTWUfLU45QVqLcQVYD3glk LH36GHeRQzfWE3w6r17XTMFWFcI2+t6IIucOrqKdOJ9ZmwwkjsVY/+4Q rJmBj/+Ui9MQg//HRWkAmemCr1eJmzXsFWPl/FFQsRKpTLPn7ZOx0eKR jtDKa5weOnVbbU2yguNjeyIOJcbb1h5PwYbe52CipEDPnTgSLd5oKAwu 0Zm7egAFL0Ohfob7pyKf5xQrDt/VIXqJ54RRlPcgBd+s+bObr6MB5UC1 f5VVWxrjY3oIha9aYK31go1G+vGpydAIjd8JHxLq7omgZU/omgJmsGgq zrUgSA==
;; Received 1061 bytes from 192.112.36.4#53(g.root-servers.net) in 52 ms

I would expect to see a netlify a record near the end – what can I do to resolve the issue?

Thanks!

Hi, @rosiegrant. The dig command is used on domain names. The example above is a query on a URL and that is why it didn’t work. This is the traced lookup for me:

$ dig +trace answers-product-search.netlify.app

; <<>> DiG 9.10.6 <<>> +trace answers-product-search.netlify.app
;; global options: +cmd
.			84852	IN	NS	e.root-servers.net.
.			84852	IN	NS	h.root-servers.net.
.			84852	IN	NS	l.root-servers.net.
.			84852	IN	NS	i.root-servers.net.
.			84852	IN	NS	a.root-servers.net.
.			84852	IN	NS	d.root-servers.net.
.			84852	IN	NS	c.root-servers.net.
.			84852	IN	NS	b.root-servers.net.
.			84852	IN	NS	j.root-servers.net.
.			84852	IN	NS	k.root-servers.net.
.			84852	IN	NS	g.root-servers.net.
.			84852	IN	NS	m.root-servers.net.
.			84852	IN	NS	f.root-servers.net.
.			84852	IN	RRSIG	NS 8 0 518400 20210125050000 20210112040000 42351 . HHd7qwdZWEMKZwHBoo7LdP6u13hsF39p/Io3P78/qzU6pbXJqWc2BafV 6usv3mnvc6EYSZCFazA9ixk0QnGdCEWoZypswEdssiSbYBzL9+vkxwdM NTyNUawYyUkv6e+4EmLJ6/dkMO1TYU7/N9lsSmR67ko1M+BXyTzN9eBu 5DRkARi+JAwORZKt9fNntpPg8oMeU25jwFfMOQsZ5KYmYZQiy+KLfruD vYmCqhVa9ossX5iE4+oRAF5GeQvMaYfvwbNkqwrb2pktSu5RTRcy14en fGsfk+23GQjnZSWLj8e7cu6Nhem4cMmdBswEC/LOtrcMYmhFHaSeNkgM QBb1Vg==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 18 ms

app.			172800	IN	NS	ns-tld1.charlestonroadregistry.com.
app.			172800	IN	NS	ns-tld5.charlestonroadregistry.com.
app.			172800	IN	NS	ns-tld3.charlestonroadregistry.com.
app.			172800	IN	NS	ns-tld2.charlestonroadregistry.com.
app.			172800	IN	NS	ns-tld4.charlestonroadregistry.com.
app.			86400	IN	DS	23684 8 2 3A5CC8A31E02C94ABA6461912FABB7E9F5E34957BB6114A55A864D96 AEC31836
app.			86400	IN	RRSIG	DS 8 1 86400 20210126050000 20210113040000 42351 . SdK8zwgaW2luOAf5A65ttS8wbzfPSqTbqBhCrMkShmM/QcE0Dmw1hGau C1jMQ/Ow4HILKmkzIaOgadSbpKm8rGPHUwpNuES7M/rDjCuNoZalBCu9 2ZLtDKd0G7PTvbxxGA9el7HIm432Uqzr5eAOXeWNeVv637JipL1Zbtpu YKYmHZNfFN/VNQ2Xhkwd1QDDB4bpgoaDoM/gqClLn7/3hX3317MWgk/V QMXrhO+xMacOll9aAnWXSTVDxFJw3c7Ipsq1P1p1a97jPLTAr3wgYJk/ 3l2wpwvmlQgtMlIc21LX4Rua8z45XHBqBxNQFpQXKi6NquA3uTCehxfa +Cb19A==
;; Received 757 bytes from 192.36.148.17#53(i.root-servers.net) in 31 ms

netlify.app.		10800	IN	NS	dns1.p01.nsone.net.
netlify.app.		10800	IN	NS	dns2.p01.nsone.net.
netlify.app.		10800	IN	NS	dns3.p01.nsone.net.
netlify.app.		10800	IN	NS	dns4.p01.nsone.net.
haqa3ebohni63ah1pgrs4ojlotehoudk.app. 900 IN NSEC3 1 0 1 139FCA6C02909936 HAQB3K01MR24F3THUF9TTB4RSSA9D58K  NS
haqa3ebohni63ah1pgrs4ojlotehoudk.app. 900 IN RRSIG NSEC3 8 2 900 20210131150721 20210109150721 62346 app. UKllOyRuVo15y513mkiSYml9YCLyTLhwIjTW0f4gsGcF49sGi4wLTawY ENuYlvH1ICzWRau9BNSsBoO1fNhFKZh8tpvGxeXxrOUGZXj0V381qiJE mW4yaaIuB2WBpPgbTmHApHU6c202OxEFQfpn0HLwNN00Bf6/zJYsR4Kw LDw=
;; Received 397 bytes from 216.239.60.105#53(ns-tld5.charlestonroadregistry.com) in 72 ms

answers-product-search.netlify.app. 20 IN A	165.227.0.164
answers-product-search.netlify.app. 20 IN A	165.227.12.111
;; Received 95 bytes from 198.51.45.65#53(dns4.p01.nsone.net) in 29 ms

Regarding the ERR_CONNECTION_CLOSED error, the following details will tell us more:

  • the complete URL requested
  • the IP address for the system making the request
  • the IP address for the CDN node that responded
  • the day of the request
  • the time of the request
  • the timezone the time is in

Normally, I would ask for the x-nf-request-id HTTP response header but if the connection is being closed, it probably isn’t being sent. Those details above replace the information the header would tell us.

You can post that information publicly or you can private message (PM) that to one of our support staff. I’ve confirmed that PMs are enabled for your community login. Please keep in mind that only one person can see the PM and this will likely mean a slower reply than posting the information publicly. Please feel free to reply to however you prefer though.

Also, if there are questions about anything in this reply please let us know.