viscid wave Jan 4, 2025, 1:43 PM

#

your panel cant reach your wings server. i would assume your wings or nodes ssl certificate is expired. run "certbot renew" as root

fickle sequoia Jan 4, 2025, 1:46 PM

#

viscid wave your panel cant reach your wings server. i would assume your wings or nodes ssl ...

ive renewed all of them already

viscid wave Jan 4, 2025, 1:47 PM

#

alright then go to your nodes page and check the browser console on that side

fickle sequoia Jan 4, 2025, 1:48 PM

#

the request says cancelled

#

nothing in the console

viscid wave Jan 4, 2025, 1:50 PM

#

have you restarted your wings?

fickle sequoia Jan 4, 2025, 1:51 PM

#

alot of times

viscid wave Jan 4, 2025, 1:51 PM

#

hmm

#

is the node hearth red?

fickle sequoia Jan 4, 2025, 1:51 PM

#

yes

viscid wave Jan 4, 2025, 1:51 PM

#

and browser console doesnt say a thing?

fickle sequoia Jan 4, 2025, 1:51 PM

#

yep

viscid wave Jan 4, 2025, 1:52 PM

#

tf

fickle sequoia Jan 4, 2025, 1:52 PM

#

wait

#

no like error things but i turned on log xmlhttprequests

#

and this

#

but i dont think thats much

#

thats legit the only thing tho

#

ik normally theres some error stuff in there if its not working

viscid wave Jan 4, 2025, 1:53 PM

#

hmm

fickle sequoia Jan 4, 2025, 1:53 PM

#

if i press on a server on the node it says

#

but theres nothing else

viscid wave Jan 4, 2025, 1:54 PM

#

hmm aight

#

sudo wings diagnostics

fickle sequoia Jan 4, 2025, 1:54 PM

#

should i systemctl stop wings first?

viscid wave Jan 4, 2025, 1:54 PM

#

lets see what that gives us

#

nah you dont have to

fickle sequoia Jan 4, 2025, 1:55 PM

#

https://ptero.co/uwimakoveb

#

under docker running containers theres some other stuff on the machine , ignore that

viscid wave Jan 4, 2025, 1:57 PM

#

wings look fine

#

tail -n 150 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc pteropaste.com 99

fickle sequoia Jan 4, 2025, 1:58 PM

#

https://ptero.co/uturiqefep

viscid wave Jan 4, 2025, 1:58 PM

#

thx

#

i assume delta.bla is you node?

fickle sequoia Jan 4, 2025, 1:59 PM

#

ye

viscid wave Jan 4, 2025, 2:03 PM

#

error is failed to connect so either some firewall is interrupting or your dns is broken. i can ping the domain can you verify it is the correct ip?

fickle sequoia Jan 4, 2025, 2:04 PM

#

100% dns is correct ip

#

and ufw already allowed 8080 and 2022

viscid wave Jan 4, 2025, 2:04 PM

#

are you using some kind of proxy

fickle sequoia Jan 4, 2025, 2:05 PM

#

only the panel is proxyed thorugh cf

viscid wave Jan 4, 2025, 2:05 PM

#

that should or cant be the problem

fickle sequoia Jan 4, 2025, 2:05 PM

#

error in onsole now

viscid wave Jan 4, 2025, 2:06 PM

#

hmm

fickle sequoia Jan 4, 2025, 2:06 PM

#

and its gone

#

wtf

#

idek

#

tf is happening

#

Failed to restart wings.service: Unit docker.service is masked.
now this is happening when i run restart wings

echo kilnBOT Jan 4, 2025, 2:07 PM

#

Simple! 😘

systemctl restart wings

fickle sequoia Jan 4, 2025, 2:07 PM

#

let me fix give me a sec

fickle sequoia Jan 4, 2025, 2:07 PM

#

echo kiln Simple! 😘 ``` systemctl restart wings ```

Wrong

viscid wave Jan 4, 2025, 2:08 PM

#

echo kiln Simple! 😘 ``` systemctl restart wings ```

great job buddy xD

knotty owl Jan 4, 2025, 2:08 PM

#

It's just reacting to keywords in their message

viscid wave Jan 4, 2025, 2:08 PM

#

we know all good :D

fickle sequoia Jan 4, 2025, 2:08 PM

#

root@v25728:~# systemctl restart wings
A dependency job for wings.service failed. See 'journalctl -xe' for details.
root@v25728:~#

echo kilnBOT Jan 4, 2025, 2:08 PM

#

@fickle sequoia You'll need to grab error logs from Wings. The following command allows to easily collect the relevant data and share the link with us: sudo wings diagnostics

fickle sequoia Jan 4, 2025, 2:09 PM

#

root@v25728:~# systemctl restart docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
root@v25728:~#

viscid wave Jan 4, 2025, 2:09 PM

#

it seams like port 8080 on your node is closed

fickle sequoia Jan 4, 2025, 2:09 PM

#

just give me a sec

viscid wave Jan 4, 2025, 2:09 PM

#

np

fickle sequoia Jan 4, 2025, 2:09 PM

#

docker died now

viscid wave Jan 4, 2025, 2:09 PM

#

ouch

fickle sequoia Jan 4, 2025, 2:09 PM

#

root@v25728:~# systemctl status docker
× docker.service - LSB: Create lightweight, portable, self-sufficient containers.
Loaded: loaded (/etc/init.d/docker; generated)
Active: failed (Result: exit-code) since Sat 2025-01-04 14:09:01 UTC; 27s ago
Docs: man:systemd-sysv-generator(8)
Process: 24394 ExecStart=/etc/init.d/docker start (code=exited, status=1/FAILURE)
CPU: 8ms

Jan 04 14:09:01 v25728 systemd[1]: Starting LSB: Create lightweight, portable, self-sufficient containers....
Jan 04 14:09:01 v25728 docker[24394]: * /usr/bin/dockerd not present or not executable
Jan 04 14:09:01 v25728 systemd[1]: docker.service: Control process exited, code=exited, status=1/FAILURE
Jan 04 14:09:01 v25728 systemd[1]: docker.service: Failed with result 'exit-code'.
Jan 04 14:09:01 v25728 systemd[1]: Failed to start LSB: Create lightweight, portable, self-sufficient containers..
root@v25728:~#

#

ima restart the machine and hope

viscid wave Jan 4, 2025, 2:09 PM

#

beg*

knotty owl Jan 4, 2025, 2:09 PM

#

That would suggest docker is not installed

#

/usr/bin/dockerd not present or not executable

fickle sequoia Jan 4, 2025, 2:10 PM

#

huh , i havent even touched it , i was running through troubleshoot steps with @viscid wave i went back on it to check status and it died out

knotty owl Jan 4, 2025, 2:10 PM

#

Docker install script is near the top of the wings install guide. Just run the docker install script again

echo kilnBOT Jan 4, 2025, 2:10 PM

#

The documentation you are looking for can be found at https://pterodactyl.io/.

viscid wave Jan 4, 2025, 2:11 PM

#

i think smth is wrong with his machine, let him try restarting it

fickle sequoia Jan 4, 2025, 2:11 PM

#

root@v25728:~# curl -sSL https://get.docker.com/ | CHANNEL=stable bash

Executing docker install script, commit: 4c94a56999e10efcf48c5b8e3f6afea464f9108e

Warning: the "docker" command appears to already exist on this system.

If you already have Docker installed, this script can cause trouble, which is
why we're displaying this warning and provide the opportunity to cancel the
installation.

If you installed the current Docker package using this script and are using it
again to update Docker, you can ignore this message, but be aware that the
script resets any custom changes in the deb and rpm repo configuration
files to match the parameters passed to the script.

You may press Ctrl+C now to abort this script.

sleep 20

fickle sequoia Jan 4, 2025, 2:11 PM

#

viscid wave i think smth is wrong with his machine, let him try restarting it

i did

viscid wave Jan 4, 2025, 2:11 PM

#

i viewed his logs and docker is clearly installed it was running like 5 minutes ago

fickle sequoia Jan 4, 2025, 2:11 PM

#

exactly

#

but now its gone?

knotty owl Jan 4, 2025, 2:12 PM

#

Run these please

sudo snap list  | nc pteropaste.com 99```

fickle sequoia Jan 4, 2025, 2:12 PM

#

root@v25728:~# sudo docker info | nc pteropaste.com 99
sudo snap list | nc pteropaste.com 99
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info
https://ptero.co/ulukajiwut

https://ptero.co/ujamifunub
root@v25728:~#
root@v25728:~#

echo kilnBOT Jan 4, 2025, 2:12 PM

#

@fickle sequoia: It looks like Docker probably is not running on your machine. Use systemctl status docker to check the status of it, and systemctl restart docker to get it operational again.

fickle sequoia Jan 4, 2025, 2:13 PM

#

echo kiln <@632281445754470420>: It looks like Docker probably is not running on your mach...

root@v25728:~# systemctl restart docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
root@v25728:~# systemctl status docker
× docker.service - LSB: Create lightweight, portable, self-sufficient containers.
Loaded: loaded (/etc/init.d/docker; generated)
Active: failed (Result: exit-code) since Sat 2025-01-04 14:12:57 UTC; 2s ago
Docs: man:systemd-sysv-generator(8)
Process: 1572 ExecStart=/etc/init.d/docker start (code=exited, status=1/FAILURE)
CPU: 6ms

Jan 04 14:12:57 v25728 systemd[1]: Starting LSB: Create lightweight, portable, self-sufficient containers....
Jan 04 14:12:57 v25728 docker[1572]: * /usr/bin/dockerd not present or not executable
Jan 04 14:12:57 v25728 systemd[1]: docker.service: Control process exited, code=exited, status=1/FAILURE
Jan 04 14:12:57 v25728 systemd[1]: docker.service: Failed with result 'exit-code'.
Jan 04 14:12:57 v25728 systemd[1]: Failed to start LSB: Create lightweight, portable, self-sufficient containers..
root@v25728:~#

knotty owl Jan 4, 2025, 2:13 PM

#

What does ls -aslh /usr/bin/dockerd say ?

fickle sequoia Jan 4, 2025, 2:13 PM

#

root@v25728:~# ls -aslh /usr/bin/dockerd
ls: cannot access '/usr/bin/dockerd': No such file or directory
root@v25728:~#

#

huh

#

where did it disappear to

knotty owl Jan 4, 2025, 2:13 PM

#

Yeah the docker daemon is missing, even tho you have the docker cli client tool

fickle sequoia Jan 4, 2025, 2:13 PM

#

should i bypass the install script to download again?

knotty owl Jan 4, 2025, 2:14 PM

#

Remove docker best you can and try the install script again

fickle sequoia Jan 4, 2025, 2:14 PM

#

rm -rf?

knotty owl Jan 4, 2025, 2:14 PM

#

apt remove docker docker*

fickle sequoia Jan 4, 2025, 2:14 PM

#

ok doing rn

#

ok wings is running now locally but still red heart

#

says this tho
Jan 04 14:15:55 v25728 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/wings/daemon.pid → /run/wings/daemon.pid; please update the unit file accordingly.
Jan 04 14:15:56 v25728 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/wings/daemon.pid → /run/wings/daemon.pid; please update the unit file accordingly.
Jan 04 14:15:56 v25728 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/wings/daemon.pid → /run/wings/daemon.pid; please update the unit file accordingly.

knotty owl Jan 4, 2025, 2:16 PM

#

at least wings is up and responding now

viscid wave Jan 4, 2025, 2:16 PM

#

well now your port 8080 is open again or reachable

knotty owl Jan 4, 2025, 2:16 PM

#

#

Refresh the page and check your browser console again

fickle sequoia Jan 4, 2025, 2:17 PM

#

'

#

for me

knotty owl Jan 4, 2025, 2:17 PM

#

Are you on the same network as the node ?

fickle sequoia Jan 4, 2025, 2:17 PM

#

nah

#

its a vps

#

does any of ur ips start with 45.33.50

#

cause i got something but dont want to leak the ip

#

i got a tls handshake error from a ip

#

which is none of mine

knotty owl Jan 4, 2025, 2:19 PM

#

if it's not starting with 144. then you're good on my end

viscid wave Jan 4, 2025, 2:19 PM

#

mine not either

fickle sequoia Jan 4, 2025, 2:19 PM

#

Jan 04 14:16:08 v25728 wings[6685]: 2025/01/04 14:16:08 http: TLS handshake error from 45.33.50.110:48002: EOF

knotty owl Jan 4, 2025, 2:20 PM

#

That's just a random bot scanning ports

fickle sequoia Jan 4, 2025, 2:20 PM

#

still red heart

viscid wave Jan 4, 2025, 2:21 PM

#

i know what that is, i used portchecker to see if your port is open

knotty owl Jan 4, 2025, 2:21 PM

#

fickle sequoia '

You ping that hostname from your computer, you get the ip 37.114.50.19 ?

fickle sequoia Jan 4, 2025, 2:21 PM

#

k

#

thats the vps ip

knotty owl Jan 4, 2025, 2:21 PM

#

Yep. I'm wanting you to double check that is what it is resolving to on your computer

fickle sequoia Jan 4, 2025, 2:22 PM

#

how

viscid wave Jan 4, 2025, 2:22 PM

#

win key type cmd and then ping "domain"

knotty owl Jan 4, 2025, 2:22 PM

#

Since connections to the VPS from the rest of the world are getting though fine, either your computer is getting the address wrong somehow, or your IP is blocked from accessing the VPS

knotty owl Jan 4, 2025, 2:23 PM

#

fickle sequoia how

just ping delta.vertexhosting.co.uk and double check the IP that appears is the expected one

fickle sequoia Jan 4, 2025, 2:23 PM

#

wait

#

let me check somerhin

viscid wave Jan 4, 2025, 2:23 PM

#

knotty owl Since connections to the VPS from the rest of the world are getting though fine,...

those are his panels logs:
Failed to connect to delta.vertexhosting.co.uk port 8080 after 11 ms: Connection refused

fickle sequoia Jan 4, 2025, 2:24 PM

#

knotty owl just `ping delta.vertexhosting.co.uk` and double check the IP that appears is th...

dosent work

#

does it for u?

viscid wave Jan 4, 2025, 2:25 PM

#

what means doesnt work

fickle sequoia Jan 4, 2025, 2:25 PM

#

this is the conso

fickle sequoia Jan 4, 2025, 2:25 PM

#

viscid wave what means doesnt work

timeout

knotty owl Jan 4, 2025, 2:25 PM

#

viscid wave those are his panels logs: Failed to connect to delta.vertexhosting.co.uk port ...

Wouldn't be surprised if that was from when wings wasn't actually running, but it might be useful to run this from the te panel server to check things.
curl -vv https://delta.vertexhosting.co.uk:8080/

knotty owl Jan 4, 2025, 2:25 PM

#

fickle sequoia dosent work

Yes I can ping that address just fine. It doesn't work for you? What does it say ?

fickle sequoia Jan 4, 2025, 2:26 PM

#

knotty owl Yes I can ping that address just fine. It doesn't work for you? What does it say...

Request timeout

knotty owl Jan 4, 2025, 2:26 PM

#

Can you show the whole output in a screenshot, including the command you ran

fickle sequoia Jan 4, 2025, 2:26 PM

#

knotty owl Wouldn't be surprised if that was from when wings wasn't actually running, but i...

let me run this first

fickle sequoia Jan 4, 2025, 2:29 PM

#

knotty owl Wouldn't be surprised if that was from when wings wasn't actually running, but i...

it dont look the best since its novnc

knotty owl Jan 4, 2025, 2:29 PM

#

The panel server can reach wings just fine now

#

Can you show us that ping from your computer

viscid wave Jan 4, 2025, 2:30 PM

#

i think he should restart his router and/or his computer or flush his dns on his pc

fickle sequoia Jan 4, 2025, 2:30 PM

#

#

should i try w vpn

viscid wave Jan 4, 2025, 2:31 PM

#

problem is just occuring on your machine or local internet somehow your pc cant reach the wing server but your panel can just fine

fickle sequoia Jan 4, 2025, 2:31 PM

#

huh

#

the panel server and node server the exact smae

#

same

knotty owl Jan 4, 2025, 2:31 PM

#

In the list of nodes, click on the node.
See where it justs versions and stuff, does that information load ?

fickle sequoia Jan 4, 2025, 2:32 PM

#

on the about page ye

knotty owl Jan 4, 2025, 2:32 PM

#

Yep. Panel is communicating with wings

viscid wave Jan 4, 2025, 2:32 PM

#

viscid wave problem is just occuring on your machine or local internet somehow your pc cant ...

^^

fickle sequoia Jan 4, 2025, 2:32 PM

#

on every server , not just me also

echo kilnBOT Jan 4, 2025, 2:32 PM

#

I have found the following for: https://media.discordapp.net/attachments/1325094362107084936/1325109702291357827/image.png?ex=677a9814&is=67794694&hm=1355660541c0672e62c7ccc562673ec1515bc7261301a4f722262de6a238d0d0&
@fickle sequoia; It looks like your browser is unable to reach the 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

Should the panel and wings be located on the same network, you might experience NAT reflection issues. In that case, type .nat for more information.

knotty owl Jan 4, 2025, 2:34 PM

#

Wings is working fine. You must have something between you and the server blocking your traffic. The rest of the world can reach your wings port fine.

fickle sequoia Jan 4, 2025, 2:35 PM

#

other users are alo having trouble connecting to server in completly diffrent countrys

knotty owl Jan 4, 2025, 2:35 PM

#

Perhaps talk to your network provider and see why their connections aren't getting through

fickle sequoia Jan 4, 2025, 2:36 PM

#

let me try some stuff

#

send me a ss of it workng for u

knotty owl Jan 4, 2025, 2:42 PM

#

viscid wave Jan 4, 2025, 2:44 PM

#

fickle sequoia it dont look the best since its novnc

thats also proove it works

#

also working for my server in helsinki 6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 33.276/33.330/33.381/0.037 ms

fickle sequoia Jan 4, 2025, 2:46 PM

#

wait for users why do it not work also?

fickle sequoia Jan 4, 2025, 2:47 PM

#

viscid wave thats also proove it works

that might be since they on the same machine but idk

knotty owl Jan 4, 2025, 2:47 PM

#

knotty owl Perhaps talk to your network provider and see why their connections aren't getti...

^

fickle sequoia Jan 4, 2025, 2:47 PM

#

knotty owl Perhaps talk to your network provider and see why their connections aren't getti...

wdym the vps provider?

knotty owl Jan 4, 2025, 2:48 PM

#

Who ever controls your network, in this case that would be your VPS provider

#

because unless you've got some firewall rules on your VPS that are specifically blocking these effected customers (including yourself), then the issue is likely somewhere with your providers network.

fickle sequoia Jan 4, 2025, 2:57 PM

#

how do i ping in cmd with port and website

knotty owl Jan 4, 2025, 2:57 PM

#

You don't.

fickle sequoia Jan 4, 2025, 2:57 PM

#

arent u pinging the port tho?

knotty owl Jan 4, 2025, 2:58 PM

#

ICMP ping does not have ports

knotty owl Jan 4, 2025, 2:58 PM

#

fickle sequoia arent u pinging the port tho?

No.

fickle sequoia Jan 4, 2025, 2:58 PM

#

knotty owl Jan 4, 2025, 2:58 PM

#

My curl requests are directed at the port tho

#

That is curl, that is not ping

fickle sequoia Jan 4, 2025, 2:58 PM

#

ok

#

ok

fickle sequoia Jan 5, 2025, 1:11 PM

#

If i redo the config file will all servers and data still work?

viscid wave Jan 5, 2025, 1:33 PM

#

fickle sequoia If i redo the config file will all servers and data still work?

dude there is no problem with your install, there is a problem either with your network or the network of your vps provider

magic axle Jan 6, 2025, 7:49 AM

#

I have my node proxies through CF tunnels, occasionally when this happens, due to the tutorial I had watched on it, if I go into the node configuration on the panel and change the port from 8080 to 443 my node is magically alive again, but it reverts on restart because it's a half ass hacky fix.

#

I fixed the issue for me at least by changing my port to 8443 in the config.yml file, in the node settings on the panel and in the cf tunnels.

fickle sequoia Jan 6, 2025, 10:17 PM

#

it dont matter , just started working again after i re did the config and changed the ip from vps provider

#Wings running but not working on panel

Executing docker install script, commit: 4c94a56999e10efcf48c5b8e3f6afea464f9108e