#Node doesn't want to go online

1 messages · Page 1 of 1 (latest)

rain ferryBOT
glossy skiff
#

YES I KNOW

sturdy prawn
#

The end of that log looks like wings is operating normally.

glossy skiff
#

it doesn't log anything in console

sturdy prawn
#

Can your computer reach the node directly?

#

node_ip:port

#

an example being https://example.com:8080 if you have ssl enabled

glossy skiff
#

I also have to do ssl on the wings right?

#

but how to do that if it's the same FQDN as the panel?

glossy skiff
sturdy prawn
#

Then you have a network issue most likely

#

either the port forward or a firewall

#

or both

glossy skiff
#

should i reinstall the wings?

#

If yes how can i do the ssl on the wings if the FQDN is the same as the certificate for the panel?

sturdy prawn
#

You can use the same certificate. You shouldn't need to reinstall wings.

#

You need to check firewalls and ports

glossy skiff
#

ohk

rain ferryBOT
glossy skiff
#

this is the panel log

#

where do i set my wings certificates?

sturdy prawn
#

They should be in the lets encrypt folder right?

glossy skiff
#

here yes

#

archive_dir = /etc/letsencrypt/archive/domain
cert = /etc/letsencrypt/live/domain/cert.pem
privkey = /etc/letsencrypt/live/domain/privkey.pem
chain = /etc/letsencrypt/live/domain/chain.pem
fullchain = /etc/letsencrypt/live/domain/fullchain.pem

#

except domain is the actual domain

glossy skiff
simple night
#

did you have the panel on port 8080 at the begging and now it's on 80/443?

glossy skiff
#

it's still on 8080 and 2022 right?

simple night
#

the node, yes

#

your panel

#

no

glossy skiff
#

heh

#

but that doesn't matter for the node right?

simple night
#

I might have went off on the wrong hitch

glossy skiff
#

this is in the node

#

correct right

simple night
#

yes

glossy skiff
#

i'll try resetting master key and rebooting the node

#

maybe that works

#

nop

rain ferryBOT
#

You'll need to grab the error logs from the Panel. The following command uploads the last 100 lines of this day's log to our pastebin and provides a link you can share.
tail -n 100 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc pteropaste.com 99

glossy skiff
rain ferryBOT
glossy skiff
#

how to fix this -__

rain ferryBOT
#

I have found the following for: https://pteropaste.com/bzdjxh/
@glossy skiff It looks like you are having issues with connecting to Wings.

Make sure that your wings are running using systemctl status wings and that your Wings ports (by default 8080/2022) are open in your firewall or router. This website can check your ports https://dnschecker.org/port-scanner.php

Browser console errors can also provide additional debugging information. More troubleshooting steps can be found at https://pterodactyl.io/panel/1.0/troubleshooting.html#cannot-connect-to-server-errors

sturdy prawn
#

Ignore that. You should be getting to where ti loads in your browser directly

glossy skiff
#

still offline + no errors in console

sturdy prawn
#

Right

#

So we are back to firewall and port forwarding

#

Where is this hosted?

glossy skiff
#

they use Virtualizor

sturdy prawn
#

That should be fine

glossy skiff
#

ye

sturdy prawn
#

I am wondering about the network setup though

#

That is why I asked

glossy skiff
sturdy prawn
#

That's not official and has nothing to do with the network setup

glossy skiff
#

alright

#

So what now?

sturdy prawn
#

You are still at "networking problem"

#

Because you can't reach wings at all.

glossy skiff
#

yup

sturdy prawn
#

I have covered what you need to look at for that

glossy skiff
#

if i do curl https://domain:8080
i get
{"error":"The required authorization heads were not present in the request."}
Which is normal right?

sturdy prawn
#

Where are you curling that from?

#

That is the expected output

glossy skiff
#

from the ssh itself

sturdy prawn
#

So it's talking to itself

#

Which is not you trying to reach it

glossy skiff
#

ok that was dumb from me

#

curl: (28) Failed to connect to domain port 8080 after 21099 ms: Timed out

sturdy prawn
#

Yeah.

glossy skiff
sturdy prawn
#

What did you run to get that?

#

that looks like netstat

glossy skiff
#

sudo lsof -i -P -n | grep LISTEN

sturdy prawn
#

So a list of network listeners

#

That doesn't mean the firewall isn't blocking things

#

that is just showing that wings is listening

glossy skiff
#

how to check the firewall, i'm sorry that i'm not so good at networking

sturdy prawn
#

That depends on the os you are on

glossy skiff
#

ubuntu 20.04

sturdy prawn
#

then it's ufw

glossy skiff
#

i think its ufw status right

sturdy prawn
#

I don't run ubuntu so I don't know all the commands

glossy skiff
#

welp so that tells allot

#

the 8080 isn't open

sturdy prawn
#

or 2022

#

So you need to add those

glossy skiff
#

tcp?

#

sudo ufw allow 8080

sturdy prawn
#

tcp for both

#

no idea on the command

glossy skiff
#

welp that worked

#

thanks