Pterodactyl Panel not working how its supposed to!! LINUX
I have setup the the panel using my LAN ip, the app url is pointed to the LAN ip in the .env config, in the remote: part in the wings config and in the config in the panel for the node. The node works, comes online and I can create and manage servers.
But I need to give access to the panel and server to an admin. Since my router changes my IP everytime it restarts, I installed and setup NoIP on the server machine and its setup properly. I forwarded all required ports. Now I followed a lot of steps using chatgpt and other sources and no matter what I do, the node doesnt come online, wings breaking, and so on. I tried a lot of different configurations, and I was able to give the admin access using the NoIP domain that I setup. But he could only access the panel and when visiting the server, he would get the we are unable to connect to the server error infinitely. I somehow managed to put my LAN ip everywhere and make it work, and everything works now, but again, only I can access it.
I have been doing this for 17 hours
Is there any guide or method I can follow to make it so that he can access the panel and the server and perform all actions without any issues? Thank you very much.
66 Replies
the app url configured in the .env MUST be the url that people have in their browser
so if I'm visiting your site using
nuts.ddns.net then that MUST be the app url
You should be able to set a static dns record on your router to make the hostname resolve to the internal IP of the panel if hairpin nat (browsing to your public IP from that network) doesn't workohh alright i will try
wait so if i just set a record on my router to point to my lan ip address from the NoIp subdomain and set the app url in env to that domain, it should work?
thank you for your reply
I think so
ohh thank you.
Sadly my router doesnt allow editing dhcp configs. can I achieve this by doing it locally on my device and asking my admin to do it on his?
or maybe an internal DNS server?
Also, when I set the app url to the domain, it kind of breaks wings and stuff and the node goes offline
and even after a lot of debugging it doesnt seem to work
you'll need wings to be able to connect to the app url and you may need to regenerate the config for wings
I did regenerate it, what should the remote: part contain in the wings config?
right now it has my LAN ip
like I said, for it to work, you need to be able to connect to the app url from the server running wings
you shouldn't need to modify the config that the panel generates for wings
okay so basically I just put the domain name in the settings of the node when generating it?
in the fqdn
You should, but depending on if wings + the panel are on the same device, you may need to add an entry to your hosts file if your router doesn't support hairpin NAT
@Aadi
thank you. Yes wings and panel are on the same device. I did make the app url to the domain from Noip, and in the fqdn when making the node, and the config that generates still has my LAN ip for some reason
is this the reason its not working?
So you set:
Yes
and in the app url
And in the configuration page for the same node you set the FQDN, it's
but it generates this
yes
Yeah, that's incorrect
If you go back to the other tab, did it save the domain you set?
It typically checks accessibility, and will fail if it's unreachable iirc
wait what do you mean save it?
I just used that to make it, I didnt edit an existing node
There's a blue save button in the bottom right...
Ah
Yeah its a new node
I kind of thought thats why its not working
I did a try a lot of things and deleted and made nodes 10-12 times
but it always generates like that
Just to confirm, this is behind a router (e.g. on a home network), right?
And your no-ip domain resolves to your public IP address if you do
nslookup yourNoIpDomain.com?yes
yes it does
ok, you'll need to add an entry to your hosts file, pointing your no-ip domain to 127.0.0.1 on your wings server, e.g.
sudo nano /etc/hosts
This is usually needed as when wings tries to speak to the panel, it resolves the panel's address to your public IP, which then is blocked by your router due to being hairpin traffic (going from an internal device, to the routers external interface, attempting to go back to an internal device)
wait i understand it now
thats actually pretty smart of u lol
u explained it well
but the thing is, i have my lan address everywhere and the panel and server work fine right now. Someone recommended I could use WireGaurd and it will be like my admin is in my lan and he can access stuff, which works for me since I only have one admin
Or should I risk it and try setting all of it again
do u think its worth it
It will work, but anyone outside your network won't be able to access the panel, if that's your goal
My only requirement is sharing full access to my one admin
who is outside my network
it will never be anyone else
Then yeah, I'd recommend switching it over to the domain. The issue with using your IP everywhere, is that for it to work for you, you'd have to use your local IP, for it to work for your friend, you'd have to use your public IP (which would then break wings and your access).
Using a domain allows you to set it to use your external IP for your admin, and override it for yourself to use your local address
ohh but the person recommending wiregaurd said that my admin will be able to access everything via the lan address
even tho he is outside my network
They would, which is why using a VPN probably isn't the recommended solution (though you can only allow access to specific IP's through your wireguard config)
ur right, but since there is just one admin who will have the same ip all the time, is this the easier solution for me?
imo switching it over to a domain is easier, as it's just changing it in 3 places: your panels
.ENV file, your nodes FQDN setting in the panel, and your wings config.
(plus adding a static DNS entry on your DNS server, or host file entries per device)
But it's up to you to decide what you think is easierI think it probably is, but I have been doing this for a stupid amount of time and i think im just scared of it all breaking again lol
Worst case you change it back in the 3 places, restart pterodactyl and then wings
ur right
its my fault entirely for not asking for support sooner
correct me if im wrong, my setup is almost correct, i just need to add an entry to my hosts file right?
and change the LAN address to the NoIP domain everywhere
thank you so much for your help
Mostly correct, yeah
thank you very much
sorry for the ping, but i changed the hosts thing and made a new node and it still generated the 192 thing
am I missing something
the last line used to be 192.168.1.50
which i changed to 127
i did save the file and restarted all services
You can just modify the config directly
I can't remember if ptero will only show the last address it successfully connected to in the config
(it shouldn't for new nodes though)
I did, but I thought it shouldnt say my lan address in the config in the web panel?
Does that not affect it?
I did change it manually in the wings config in my machine\
The settings tab is what matters
i just made a node again and the file it generated has the domain
not my LAN address
even tho it has my LAN in the web panel
okay, the settings tab has the domain
Then that should be fine
start wings with
wings --debug
verify it's able to connect to the panelthis seems to be the error
You've either already got another instance of wings running, or another application is listening on port 8080
ill stop wings alltogher and then run it
From what that logs says though, it did connect to the panel, unless I'm misreading it
ohh okay. It says this now, however the node is still offline
the node settings have the domain as the fqdn
You'll need to add the hosts file entry on your machine too, but instead, pointing it at your servers LAN IP (or add a static DNS entry on your router, if it supports it, and you haven't changed your local DNS server)
but the node config in the panel has the LAN
im sshing to the machine on the server, so when i did the hosts file entry i added them on that machine right? are you saying I need to add them on this machine as well?
The machine you're sshing from, in addition, yeah
but that hosts file entry is to your servers LAN IP, 192.168.1.50, rather than 127.0.0.1
gotchu
And that should fix everything locally
The heart on the nodes tab should be green
and the console should work
Just out of curiosity, how does that work?
sort of confused about this point
like what does my pc have to do with the node not starting
The way wings/pterodactyl works, is that clients (your browser) attempting to check the status of a node, or get the console, start a server, etc. by connecting directly to Wings.
Currently your Wings address is the no-ip URL, just like Wings couldn't speak to your pterodactyl instance via the no-ip address, your browser can't speak to wings via that address either
perfect, i understand now
In a normal network, you'd set this up in a single place, your DNS server, but not all home routers allow you to add static entries (overrides), which is why the two host file entries are needed
ohh makes sense now
Thank you so much it finally works now
cannot be more grateful
No worries, the setup when you're behind hairpin NAT is a little janky
which is why it can be preferable to use a hosting provider, but if you've got the hardware, may as well use it
🫡
sorry to ping but I couldnt ask this to anyone else
the port forwarding seems to have broken after doing this
do you have an idea what could the fix be?
thank you
port forwarding for 25565
I have port forwarded it using my LAN address and it used to work but when I check on canyouseeme it gives an error
My bad I managed to fix it
sorry for the ping
It's all good
How did you manage to fix it?
I had accidently set the allocation to 127.0.0.1
I needed to set it to my LAN address
Makes sense