#Node unstable

18 messages · Page 1 of 1 (latest)

vapid apex
#

Also, on the node panel the node seems to be online

#

but on the information doesn't

thick apexBOT
#

You'll need to grab error logs for Wings and share the link with us. The following command will help you collect the required information for debugging: sudo wings diagnostics

vapid apex
thick apexBOT
#

I have found the following for: https://ptero.co/elemahenap
At your service, @vapid apex!

The IP address you have assigned to your server is not actually available for use on your machine, or something is already running on that port. Use ss -plnt | grep :<port> (replacing <port> with your own) to find what processes might be using it.

If you don't find any service using the port, then refer to the instructions below.

Execute the command hostname -I | awk '{print $1}' and change your Node allocations to use this IP. Yes, it can be your internal/local IP when you're behind NAT. You still have to use it as that is your network interface IP.

If you have added multiple public IPs to your network interface, then you can view all of them using the command ip a | grep "inet "

vapid apex
worldly jetty
#

You will have to assign a IP that’s actually available/assigned to the node that the server is on

#

It has nothing to do with the machine the panel is on

vapid apex
#

okey

#

but I mean, on the Fully Qualified Domain Name there is a domain with an A record

#

and the allocations have the ip showed with the hostname -I | awk '{print $1}' command

vapid apex
#

Now its alive, didn't do anything

image.png
#

in some minutes it would be offline again

vapid apex
#

Again xd

image.png
thick apexBOT
#

We need some logs from you in order to help debug this issue.
Panel: tail -n 150 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc pteropaste.com 99
Wings: sudo wings diagnostics
Please see .plogs and .wlogs respectively for more information.

vapid apex
thick apexBOT