#First Time setup Node Issue
96 messages · Page 1 of 1 (latest)
Worth going to the docs > troubleshoot and look at the ''Basic Debugging Steps''
Along with some logs @hollow crane
Thanks for the advice ill go have a look at those now 🫡
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
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)
Its currently 20:16 for me
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;
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
Okok thankyou banana
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.
Can i stop wings with the killall wings command ?
So, that debug.. you made it seem like u generated that now, but it was actually half an hour ago?
Yes i generated it right now
But i did take a break after setting this up so it would make sense
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.
Okay ill give that a go now
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
do i need su in front of any of those or run them currently in this ?
Go back to the docs, https://pterodactyl.io/wings/1.0/installing.html#daemonizing-using-systemd
Pterodactyl is an open-source game server management panel built with PHP, React, and Go. Designed with security in mind, Pterodactyl runs all game servers in isolated Docker containers while exposing a beautiful and intuitive UI to end users.
Make sure after you made the wings.service (urs says wing.service, check for typos) that u also enable it.
ah i got a different debug now
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?
Yep exactly as i said.
Always stop wings first ''systemctl stop wings'' before testing it's functionality with the debug.
im honestly a tad lost ive tried using systemctl stop wings but i get nothing
Yes
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
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.
Okay will do
Yep spotted ur issue.
Is it the binding ?
Wings itself started fine, but u seem to be proxying the connection
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.
Is that becuase im using cloudflare by any chance
Yes ur proxying through cloudflare.
ahh okok
If u don't want/need it, put ur DNS records to ''DNS only''
As they are now set to ''Proxied''
Okay could you explain how i can fix this would i need to go through cloudflare and change dns settings or through pterodactyl ?
... 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
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.
Simple! 😘
systemctl restart wings
So should look like this ?
perfect i appreciate your help
Check ur node, it's probably already online and ready to go.
As i now see port 8080 open on ur network
On my end it's already propagated, try restarting wings.
Yep, all good.
Thankyou so much do u have like a buy a coffee thing or something just to show some appreciation for your time?
Thankyou for the learning curve as well haha
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)
No problem at all i hoped giving as much as possible would make it alot easier
haha yes it is !!
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)
I went for the amd processor because there wasnt any arm free 😭
4vcpu and 24gb of memory
So, not free tier then.
It will most defintely, and probably quite alot.
Yes im going to try to hop over to arm when i get the chance
Seen people try it for 2 years, without any luck lol
Or.. just pay for a decent spec VPS.