#Pterodactyl Panel to Node Error:

63 messages · Page 1 of 1 (latest)

cloud baneBOT
#

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.

stoic nova
#

Open browser console on node page and give us the error or just screenshot it, doesn’t exactly matter

#

Also there is #panel-in-docker and #docker-help for specific help with running stuff in docker

#

But prob slightly different because of unraid

foggy dome
#

Okay Quick Question:

For the FQDN (when i dont want to use SSL), do i need to writie down the IP from the UnRAID Server ?

Like 192.168.0.23 ? Or + the Port for the Deamon Docker ? (DEFAULT: 8181)

stoic nova
#

you can use the ip yes

#

Just make sure to set the checkbox for ssl as http connection (forgot the exact wording for it but close enough)

foggy dome
#

Yea you're correct.

okay when i dont wanna use SSL i can keep the 8080 Port ? Or do i need to change it to the deamon port (8181) ?
I'm a bit confused 😄

stoic nova
#

the port needs to be whatever wings is running on

foggy dome
#

Okay Wings is Pterodactyl Deamon, gotcha, okay so 8181

But what does Host Port #1 and Host Port #2 mean?

#

Host Port #1 is default 2022 and #2 8181

stoic nova
#

Oh 2022 is for sftp

#

that goes is used to be able to access the servers via sftp

foggy dome
#

I'm conntected via vpn with the server

#

hopefully it doesnt make it worse

stoic nova
#

is wings running?

foggy dome
stoic nova
#

Also I thought 8080 was default but it’s prob different with how you have it setup

stoic nova
foggy dome
#

idk, i didnt changed the compose.yml

#

lemme restart the deamon rq

stoic nova
#

I say port 8080 because that’s what it is in the offical docs

foggy dome
#

ah kk

crazy it says no config even when there is one

stoic nova
#

Unless it’s being mapped to 8181 outside of the container

#

Which I assume is what your doing?

foggy dome
stoic nova
#

Hmm

foggy dome
stoic nova
#

You may need to use the ip 172.17.0.9 instead

foggy dome
#

You mean in the FQDN Thingy?

stoic nova
#

Yea

#

I’ve personally not ran pterodactyl or wings within docker before so I could be wrong

foggy dome
#

Hm strange thing is, it worked perfectly fine before i deleted everything to make it "clean" lul

stoic nova
#

I should also probably go because it’s 1:35am for me and my phone is on 2%

foggy dome
#

oh

#

RIP

stoic nova
#

Yea..

#

2nd night in a row :/

foggy dome
#

uff, its 5:36pm here 😄

ok something is strange

#

now i can see my cores and system informations

#

but still red heart

stoic nova
#

Different error maybe? And make sure to reload the page

foggy dome
#

i did, i even reload the docker everytime i change something

stoic nova
#

It can just be visual sometimes if you can see node info

foggy dome
#

when it would be a visual bug, i go crazy

#

i try to figure it out since 2 days

stoic nova
#

If you reloaded then no

foggy dome
#

i can my infos, but yea still red heart and no error message in console

stoic nova
#

I meant, that it just doesn’t update the heart icon if the wings go up after the red heart

foggy dome
stoic nova
#

Are you able to see the version number if you hover over the heart?

foggy dome
#

nop#

cloud baneBOT
#

I have found the following for: https://media.discordapp.net/attachments/1389624342417117264/1389631793870672033/image.png?ex=686552f5&is=68640175&hm=d1dd3c5772780ec7d73bc931cf6ab7ee407c28674c040abd61f2af18716a1226&
@foggy dome; 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.

stoic nova
#

So there is still an error, yea idk tbh (I am tired so ig I’ll leave for now)

foggy dome
#

alright, still thx for your help

#

gn8

stoic nova
#

I’ll most likely be back once I wake up ofc

foggy dome
#

yea dw