#First Time setup Node Issue

96 messages · Page 1 of 1 (latest)

hollow crane
#

Just followed through with a first time setup however I'm getting an unhealth node can someone advise some fixes I can try as I'm unsure of what to do ?

shut inlet
#

Along with some logs @hollow crane

hollow crane
#

Thanks for the advice ill go have a look at those now 🫡

calm galleonBOT
#

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

hollow crane
shut inlet
#

Debug isn't showing errors, which is good.

#

But the time, 19:50 makes it look like the entries are old (depending on ur timezone)

hollow crane
#

Its currently 20:16 for me

shut inlet
#

Stop the debug, and to be sure other wings instances ''killall wings'' then start wings with ''systemctl start wings'' show us some logs after with;

calm galleonBOT
#

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

hollow crane
#

Okok thankyou banana

shut inlet
#

If u choose to redact info such as FQDNs/IPs then u would need to manually check for network/firewall issues etc, see if ports are open/closed.

hollow crane
#

Can i stop wings with the killall wings command ?

shut inlet
#

So, that debug.. you made it seem like u generated that now, but it was actually half an hour ago?

hollow crane
#

Yes i generated it right now

#

But i did take a break after setting this up so it would make sense

shut inlet
#

So stop the debug, then ''systemctl stop wings'', ''killall wings'', ''systemctl start wings''

#

Just to be completely sure we ain't getting bind errors.

#

Then some new logs.

hollow crane
#

Okay ill give that a go now

calm galleonBOT
#

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

hollow crane
#

do i need su in front of any of those or run them currently in this ?

shut inlet
#

Make sure after you made the wings.service (urs says wing.service, check for typos) that u also enable it.

hollow crane
#

ah i got a different debug now

shut inlet
#

Make sure to stop wings from running first, BEFORE using debugs.

#

As it will generate bind errors doing so (debug will start wings again, and it cant bind to port 8080 twice, for obvious reasons)

#

What does your debug show?

hollow crane
#

ah shit sorry i think it was still up trying to bind twice

shut inlet
#

Yep exactly as i said.

#

Always stop wings first ''systemctl stop wings'' before testing it's functionality with the debug.

hollow crane
#

im honestly a tad lost ive tried using systemctl stop wings but i get nothing

shut inlet
#

Because it doesn't give you an output.

#

You use the command? done

hollow crane
#

Yes

shut inlet
#

now ''systemctl start wings'' which also gives no output

#

And then give us some logs

calm galleonBOT
#

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

hollow crane
calm galleonBOT
#

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

shut inlet
#

Ignore the bot

#

He replied to an old error entry

hollow crane
#

Okay will do

shut inlet
#

Yep spotted ur issue.

hollow crane
#

Is it the binding ?

shut inlet
#

Wings itself started fine, but u seem to be proxying the connection

calm galleonBOT
#

Pterodactyl has features to enable use of proxies, however we cannot provide support for proxies as it adds great complexity to the application set up. Troubleshooting complex network setups involving tunnels and proxies is extremely difficult to do without access to that network. Supporting complex network issues is outside the scope of this support.

hollow crane
#

Is that becuase im using cloudflare by any chance

shut inlet
#

Yes ur proxying through cloudflare.

hollow crane
#

ahh okok

shut inlet
#

If u don't want/need it, put ur DNS records to ''DNS only''

#

As they are now set to ''Proxied''

hollow crane
#

Okay could you explain how i can fix this would i need to go through cloudflare and change dns settings or through pterodactyl ?

shut inlet
#

... it's a DNS issue with ur records, ofcourse you need to fix it through cloudflare, in this case xd

#

Litteraly all u need to do, is click on the little switch saying ''proxied'' and set it do ''dns only'' for the a-record for your panel

hollow crane
#

Sorry im a beginner with all this stuff so im trying to learn lol

#

Thankyou !

shut inlet
#

Then wait for DNS to propagate (can take minutes.. or up to 48 hours) but usually very quickly, and u shouldnt even need to restart wings, u should see ur node turn green quite quick.

calm galleonBOT
#

Simple! 😘

systemctl restart wings
hollow crane
#

So should look like this ?

hollow crane
shut inlet
#

Check ur node, it's probably already online and ready to go.

#

As i now see port 8080 open on ur network

hollow crane
#

Still red for now

#

Ill give it a bit longer

shut inlet
#

On my end it's already propagated, try restarting wings.

hollow crane
#

Okie dockie

#

All green now ❤️

shut inlet
#

Yep, all good.

hollow crane
#

Thankyou so much do u have like a buy a coffee thing or something just to show some appreciation for your time?

shut inlet
#

No need bud 🙂

#

Glad it's working

hollow crane
#

Thankyou for the learning curve as well haha

shut inlet
#

Yeah, often all you need is some troubleshooting. And i'm glad u choose not to ''redact'' your FQDN etc in the logs (which is an option)

#

Makes it hard for me to check peoples FQDN for issues such as proxies, ports etc.

#

Now, go enjoy that oracle cloud free tier machine (i assume)

hollow crane
#

No problem at all i hoped giving as much as possible would make it alot easier

hollow crane
shut inlet
#

Don't think i've ever seen anyone come into this server, using oracle that wasn't a free tier machine.

#

Now remember the ARM processor won't get u far, most games don't support it.. minecraft does (most people use it for MC)

hollow crane
shut inlet
#

1vcpu and 1gb of memory?

#

What do you plan on running?

hollow crane
#

4vcpu and 24gb of memory

shut inlet
#

So, not free tier then.

hollow crane
#

I think itll charge me eventually lol

#

Yes i think i get a month free

shut inlet
#

It will most defintely, and probably quite alot.

hollow crane
#

Yes im going to try to hop over to arm when i get the chance

shut inlet
#

Seen people try it for 2 years, without any luck lol

hollow crane
#

💀

#

its gonna be a rough one trying to get one myself then

shut inlet
#

Or.. just pay for a decent spec VPS.