#Error connecting to node!

1 messages · Page 1 of 1 (latest)

high pumice
#

Aside from getting a big red heart on my nodes panel, I'm also unable to automatically update my config.yml automatically, it also shows this error whenever I want to automatically replace the config.yml.

tls: failed to verify certificate: x509: certificate is not valid for any names, but wanted to match

weak ospreyBOT
#

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

high pumice
#

woah

#

sick bot

sand steppe
#

Well, i triggered it

#

But it is a sick bot indeed.

high pumice
#

is the first one not automatic?

sand steppe
#

First one, yes.

#

It responds to predefined keywords, with predefined responses. But some people seem to think it's AI.

high pumice
#

i'd understand why they think it's AI

weak ospreyBOT
#

I have found the following for: https://ptero.co/ahafelegaw
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.

Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.

sand steppe
#

Also read ur own logs, the bot will also see old entries in ur logs, and respond to it

#

Which is the case now.

high pumice
#

I didn't even know where the logs are 😭

#

I feel like an old person using linux

#

i only switched to linux after realizing my old server on windows was running with 8 gigs idle

#

of ram used up*

sand steppe
#

Do note mint isn't officially supported, it is derived of ubuntu though, so you should get it working.

And now your configurations.. assume ur trying to use some sort of tunnel/proxy setup?

high pumice
#

no, i'm using a subdomain service if that's important

#

i read through the let's encrypt eula and it mentioned something about "not having control of my domain" being bad

#

could that be an issue?

sand steppe
#

I think the main issue would be the use of custom ports, like 444, 445, networking issues etc

#

But i can't dig into further atm.

high pumice
#

i'll try the default ones again, but do the daemon ports have to be forwarded as well?

#

and could you remind me what the default ports are?

sand steppe
#

Check pins in #installation-help for the default ports.

high pumice
high pumice
#

thanks

sand steppe
#

So, the red/green heart in ur node is ur browser reaching wings/ or not, so if the port used isn't open/forwarded, it won't show a green heart.

high pumice
#

are there any useful commands I can use to check if ports are open or not on linux?

sand steppe
high pumice
#

sure, thanks

#

my wings are configured to 8080 but it returns nothing when i do ss -plnt | grep :8080

#

does the host address need to be changed?

weak ospreyBOT
#

I have found the following for: https://ptero.co/ereximoheb
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.

Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.

high pumice
#

im just gonna restart my pc

weak ospreyBOT
#

I have found the following for: https://ptero.co/ulayanuzox
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.

Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.

high pumice
#

ok no keywords

high pumice
#

it worked, i had to use a custom port

#

8080 refused to work

sand steppe
#

Yeah, it's not uncommon for ISPs to block port 8080 by default

high pumice
#

bummer

sand steppe
#

U can check it with ur ISP though. Although the node will work fine on a different port than 8080, might even be beneficial, security wise, for some people.

high pumice
#

i don't mind using random ports, i wouldnt imagine that it would affect me that much

#

worst it could do is that i would forget it and i'll be forced to check the configs

sand steppe
#

In most cases you wouldnt need to worry much about wings/it's configuration once everything is up and running.

Things that are more common to occur after time are expired ssl certificates, running out of diskspace etc.

high pumice
#

that'll be fine, probably

#

also my server "failed to bind host port" when starting

sand steppe
#

If its a local server, so behind NAT, make sure to allocate the local IP of the server running wings.

#

Instead of the public IP

high pumice
#

what's a NAT?

sand steppe
#

Network address translation. So a way it maps multiple local ips behind a public ip

#

So a local network as urs, u would allocate ur nodes server local IP to the servers, and have them publicly available through portforwarding.

high pumice
#

i believe i've set it up correctly

#

it's the same local IP as the web panel

sand steppe
#

So from inside ur network, u would connect to whatever server u run through localip:port and outside ur network through publicip:port

high pumice
#

and the web panel is working just fine

sand steppe
#

Does wings run on the same server as the panel?

high pumice
#

yes

sand steppe
#

On the server running wings, do this;

Execute the command hostname -I | awk '{print $1}'

#

The output of that command should be the correct IP to use for the allocation

high pumice
#

i'm using that ip

#

i'll copy paste it in case i have some random space in the start or the end

sand steppe
#

Can u show the error in the console?

high pumice
#

my UUID is safe to share right

sand steppe
#

Yeah, but feel free to DM me with the screenshots etc instead.

high pumice
#

it's fine i'll just post it here

#

for sure they cant do anything with an uuid

#

Stacktrace:
Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint bc287170-7b2f-48ef-8c7c-a510515b51d1 (783caf53f1341648ffeab9bf7d8faaf8d7a5fd3e5bf667e558634aaed0a117db): failed to bind host port for x:25565x:25565/tcp: cannot assign requested address
environment/docker: failed to start container
failed to start server after crash detection
github.com/pterodactyl/wings/server.(*Server).handleServerCrash
github.com/pterodactyl/wings/server/crash.go:90
github.com/pterodactyl/wings/server.(*Server).OnStateChange.func1
github.com/pterodactyl/wings/server/server.go:324
runtime.goexit
runtime/asm_amd64.s:1650

weak ospreyBOT
#

At your service, @high pumice!

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 "

high pumice
#

nothing is running on that port...

sand steppe
#

Why did u use xx instead of the IP?

#

If its a local IP, then there is no need to hide it.

high pumice
#

oh yeah

sand steppe
#

As it's private/personal to you.

high pumice
#

well the first ip is my public IP

#

the second one starts with 172

sand steppe
#

Exactly, so ur still assigning ur public IP as allocations.

#

And not ur servers local IP

high pumice
#

so i just use localhost?

sand steppe
#

No :p

high pumice
#

oh right

#

yeah

#

my local ip

#

got it

sand steppe
#

Yea, that is what you allocate to the server.

#

Ur public IP is not actually available on ur machine, hence why it can't bind

high pumice
#

oh, understood

#

yeah, works fine

#

thanks