NodeMC / CORE

Core of NodeMC, including stock dashboard and setup files.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Firewalled server not running

opened this issue · comments

The server I would like to run this on is firewalled & part of an network that is not connected to the internet (which I can not change)... this means that it will never run because it tries to access a lot of pages, could make it such that it does not do this:

/Users/Tristan/Minecraft/NodeMC-CORE/Main.js:246
throw err;
^
http://ifconfig.co/x-real-ip : Error: connect EHOSTDOWN 188.113.88.193:80 - Local (0.0.0.0:0),http://icanhazip.com/ : Error: connect EHOSTDOWN 64.182.208.181:80 - Local (0.0.0.0:0),http://ifconfig.io/ip : Error: connect EHOSTDOWN 104.27.153.130:80 - Local (0.0.0.0:0),http://ip.appspot.com/ : Error: connect EHOSTDOWN 216.58.212.177:80 - Local (0.0.0.0:0),http://curlmyip.com/ : Error: connect EHOSTDOWN 184.106.112.172:80 - Local (0.0.0.0:0),http://ident.me/ : Error: connect EHOSTDOWN 176.58.123.25:80 - Local (0.0.0.0:0),http://whatismyip.akamai.com/ : Error: connect EHOSTDOWN 2.16.4.192:80 - Local (0.0.0.0:0),http://tnx.nl/ip : Error: connect EHOSTDOWN 193.200.132.187:80 - Local (0.0.0.0:0),http://myip.dnsomatic.com/ : Error: connect EHOSTDOWN 67.215.92.215:80 - Local (0.0.0.0:0),http://ipecho.net/plain : Error: connect EHOSTDOWN 146.255.36.1:80 - Local (0.0.0.0:0),http://diagnostic.opendns.com/myip : Error: connect EHOSTDOWN 74.125.136.121:80 - Local (0.0.0.0:0)

Hi, do you have a http-proxy setup on your network?

If not, and it's completely isolate that's OK. If you do, look into this: https://github.com/request/request#controlling-proxy-behaviour-using-environment-variables

If not, then this is a valid bug (suppose it is anyways) to networks that have no outside internet access and is a valid usecase aswell

This is definitely a bug - because of the way NodeMC operates I rely on a request to an outside server that will relay the public IP back. I will look into adding a fallback for this error though.