#Looking to connect a new node to the panel (Separate machine)

39 messages · Page 1 of 1 (latest)

unkempt forum
#

Hey Guys, I am trying to connect a separate machine to my existing panel for some more headroom with resources, I have my panel online and working 100% and I have attempted to connect my new separate machine (Different IP too) to my existing panel with a node already connected. I can't seem to get it to connect, where can I start to let you guys know of what I am stuck on?

I have installed Ubuntu 22.04 on the new machine and followed the wings instructions from your official site, I have then used the auto-deploy function in the node for the configuration file but I am stuck now.

Cheers

marble river
#

Have a look at your panel/wings logs

unkempt forum
rich valleyBOT
#

I have found the following for: https://ptero.co/kuzifodora
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.

unkempt forum
#
:~# ss -plnt | grep :8080
LISTEN 0      4096               *:8080            *:*    users:(("wings",pid=1374,fd=10)) 
#

that was the only output

marble river
unkempt forum
#

yep, wings is supposed to run to connect to the panel?

marble river
#

Check the systems firewall?

#

Make sure wings ports are open

unkempt forum
#

which ports are for wings again?

marble river
#

8080 and 2022

unkempt forum
rich valleyBOT
#

I have found the following for: https://ptero.co/lazabelaxe
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.

unkempt forum
#

thank you these are the updated logs

#

it would be there paragraph at the bottom i think?

marble river
#

Ahh, your using WSL2

unkempt forum
#

i sure am

#

do you think that might be causing multiple bind ports being used

#

some sort of windows protocol hogging 8080

marble river
unkempt forum
#

if you are talking about my panel.imnita.net that is on a whole different computer

#

that is where my panel is installed

#

this node is on a separate computer with a separate IP

marble river
#

The wings log file is that from the node with the issue?

unkempt forum
#

correct :)

#

the panel itself is running and ready

#

trying to add this node on for more resources

marble river
#

That 2nd node is using the same ssl as the panel?

unkempt forum
#

yep it looks to be grabbing my same cert

#

it has the same cert as the main domain and panel computer

marble river
#

And for the 2nd node conf what address did you use?

unkempt forum
#

the same FQDN

#

i used the auto-deploy

marble river
#

And thats the issue....

unkempt forum
#

i thought that was how the second node knew what panel to connect to

jagged yarrow
#

no. the nodes FQDN represent the address of the node

#

WSL is also not really a supported platform

unkempt forum
#

Ohhhhhhhh