Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.
#Wings doesn't work
dusk yarrowBOT
I have found the following for: https://ptero.co/oxuhumygoz
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.
olive burrow
Check if your port is open from the outside anyways. Disabling the firewall doesn't always do it.
olive burrow
I have found the following for: <https://ptero.co/oxuhumygoz>
You already have a...
Before running wings --debug, stop wings with systemctl stop wings
Could mean wings isn't started
It's not closed
Is wings started?
Scan again
systemctl status wings says active? No errors?
8080 is open to TCP Traffic?
Are you using Cloudflare's Proxy?
curl -4 icanhazip.com (or it might have been .net)
Make sure the IP your A record is pointing at matches the public IP it gives back
Go to the page with the red heart under nodes and press F12, then click console
What's the error message?
You'll have to wait a bit
Even if it's just timed out, something will show up if the heart is red
Nothing had shown up still?
Can you try Firefox?
Also is the Daemon port set to 8080 in /etc/pterodactyl/config.yml?
Have you posted the link from wings diagnostics to see if the bot finds anything yet?
And that was after you stopped the wings service?
I'm pretty sure it's an issue with your firewall. 8080 TCP isn't getting through.
Are you using UFW?
UFW manages iptables
If you disabled it, nothing is telling iptables to open your port
Try opening it in iptables just in case
iptables -I INPUT -p tcp --dport 8080 -j ACCEPT
At the very least it will rule it out as a problem
It means accepting connections from the outside
Should be copy pasteable
Yes
I got it from here and changed the port to 8080. https://www.systutorials.com/how-to-open-a-port-in-iptables/
olive burrow
iptables -I INPUT -p tcp --dport 8080 -j ACCEPT
If it works you'll have to make it permanent or have that run every startup. That rule will disappear when your server restarts.
It's not iptables then... Were there any errors in Firefox?
You may have to wait a few minutes for one to show up
I'm on a phone right now. I can check it in a few hours. I'll DM you my email to add.
olive burrow
jquery.min.js?t={cache-version}:4 XHR failed loading: GET "https://node-1.redacteddomain.extension:8080/api/system".
I'm not sure. The bot doesn't have a response to that error and I've never come across it before.
Both port 8080 and 2022 are timing out. That usually means either wings isn't running or there is a problem with the firewall.
Do you have another firewall besides the one on your system? Like through your hosting provider?
I'm 99% sure it's a firewall issue
What hosting provider are you using?
I think you have to turn it's firewall on and then open the ports.
You can remove my account on your panel whenever you want now btw, we already got the error.
On the AWS firewall?
I'm unfamiliar with AWS. I have no idea if that's right or not. I am still 99% sure it's a firewall issue though. Maybe AWS has support you could contact?
You could also check /var/log/syslog for any rejected requests from iptables.
It might also be /var/log/messages or /var/log/kern.log
ashen orbit