daring vortexBOT
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.
sturdy basin
I already tried this nothing happened
ive changed port to 8080,8081,8801 and all the same
stark ingot
I already tried this nothing happened
You did not, or you would have more information. These are troubleshooting steps.
sturdy basin
I am unsure what you are saying?
cuz i did the ss and got this
This is my wings debug
stark ingot
Did you use the unofficial installation script?
sturdy basin
nope
stark ingot
Did you daemonize wings before it ran without errors?
I just don't understand how you managed to run it twice otherwise; the docs have you use wings --debug FIRST before anything else; there shouldn't be another wings running in the background unless you either ignored the instructions or used the unoffiical install script.
sturdy basin
i did the debug first and it seemed fine and im not using the unofficial install script, i didnt even know there was one
stark ingot
i did the debug first and it seemed fine and im not using the unofficial install...
Ah, that would explain it. If the debug was fine you won't find any errors in there; the error you're seeing is caused by running wings twice. If you've already daemonized wings it will be running in the background.
If you're still seeing a red heart and wings doesn't have any errors, the errors will be in your browser's console (F12 -> Console on most browsers).
stark ingot
Give it a minute, maybe try refreshing the page too. Something should show up there eventually.
stark ingot
There should be a longer one that includes an endpoint it's trying to reach.
ie, node.example.com:8080/api/endpoint or something. Click on it and see if you can reach it.
stark ingot
Gotta find the error message somewhere in there. That's part of your browser, not the endpoint it's failing to get to.
sturdy basin
thought could be a firewall thing so allowed them ports on my hoster and nothing still but not getting no errors at all on console
vague sierra
thought could be a firewall thing so allowed them ports on my hoster and nothing...
whitelisted on the OS?
sturdy basin
whitelisted on the OS?
what you mean?
vague sierra
itsa dedicated server which has a firewall hetzner
point still stands, the firewall on your VPS and the firewall on your OS are 2 different things that need to be configured seperately
sturdy basin
Go these messages again :/
