TROUBLESHOOTING/issue template: connectivity issues

[saper]

An idea: since we normally fetch the binary by ourselves we should consider questions similar to what npm has never in their issue tracker

[nschonni]

I was thinking about adding a 404 section to the TROUBLESHOOTING.md, or where you thinking something else?

[saper]

npm has this:

supporting information:

• npm -v prints:
• node -v prints:
• npm config get registry prints:
• Windows, OS X/macOS, or Linux?:
• Network issues:
  • Geographic location where npm was run:
  • [ ] I use a proxy to connect to the npm registry.
  • [ ] I use a proxy to connect to the web.
  • [ ] I use a proxy when downloading Git repos.
  • [ ] I access the npm registry via a VPN
  • [ ] I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • [ ] I develop using Vagrant on Windows.
  • [ ] I develop using Vagrant on OS X or Linux.
  • [ ] I develop / deploy using Docker.
  • [ ] I deploy to a PaaS (Triton, Heroku).

I think this is something useful for us as well