-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to resource #227
Comments
Hey, |
According to the VPS yes. I have tried both in a VPS and on my local server. |
A couple of things you could check: make sure the endpoint on the Newt logs and in the Gerbil section of the config.yml resolves to your VPS IP from your Newt location. Usually you can run nslookup to check. Next make sure one more time nothing is blocking that port and you did allow UDP. UFW or iptables can block. Finally if all that is good run a tcpdump on the VPS and filter for that port and see if you are getting packets. You can run newt to connect or see if you can connect with netcat
|
Thanks all for the advise. Looks like 51820 is blocked somehow but cant find where. |
Hum that's odd. You could look through your VPS settings maybe in the hosting provider and also check UFW and IPTABLES rules to make sure it is not blocked. Who is your hosting provider?
|
Yes the port is supposed to be forwarded |
I have tried multiple different hosts to install the newt agent on. I have tried my primary network as well as vlans.
The text was updated successfully, but these errors were encountered: