#[FIXED] failed to load server configurations error

180 messages · Page 1 of 1 (latest)

ancient hemlock
#

Hello, I managed to get everything working yesterday but I turned my server off last night, turned it back on this morning and I couldn't access it from SSH. after some troubleshooting I noticed that the server decided to change its IPv4 from 192.168.0.189 to 192.168.0.187.

I have now followed some tutorials to fix its ip adress to 192.168.0.189 (which was the adress it had when I configured Pterodactyl and everything worked), I am back to having access to the SSH, my Pterodactyl panel but my nodes wont work which I read somewhere was an issue with my wings not being able to communicate with the panel. I did run a sudo wings --debug and I get :

#

Stacktrace:
Get "https://panel.nyrzdomain.org/api/remote/servers?page=0&per_page=50": dial tcp PUBLICIP: connect: no route to host
http: request creation failed
github.com/pterodactyl/wings/remote.(*client).request.func1
        github.com/pterodactyl/wings/remote/http.go:151
github.com/cenkalti/backoff/v4.RetryNotifyWithTimer.Operation.withEmptyData.func1
        github.com/cenkalti/backoff/[email protected]/retry.go:18
github.com/cenkalti/backoff/v4.doRetryNotify[...]
        github.com/cenkalti/backoff/[email protected]/retry.go:88
github.com/cenkalti/backoff/v4.RetryNotifyWithTimer
        github.com/cenkalti/backoff/[email protected]/retry.go:61
github.com/cenkalti/backoff/v4.RetryNotify
        github.com/cenkalti/backoff/[email protected]/retry.go:49
github.com/cenkalti/backoff/v4.Retry
        github.com/cenkalti/backoff/[email protected]/retry.go:38
github.com/pterodactyl/wings/remote.(*client).request
        github.com/pterodactyl/wings/remote/http.go:136
github.com/pterodactyl/wings/remote.(*client).Get
        github.com/pterodactyl/wings/remote/http.go:81
github.com/pterodactyl/wings/remote.(*client).getServersPaged
        github.com/pterodactyl/wings/remote/servers.go:201
github.com/pterodactyl/wings/remote.(*client).GetServers
        github.com/pterodactyl/wings/remote/servers.go:26
github.com/pterodactyl/wings/server.(*Manager).init```
gentle drumBOT
#

Not good, @ancient hemlock! The host you're trying to reach might be invalid or its firewall is blocking your connection attempts gracefully.

If you believe the host to be correct and have checked it with dig or https://dnschecker.org/, it means your DNS might be experiencing issues. You can try to ping a different domain, such as Google and if it resolves the issue is not with your DNS and rather with the host you are trying to reach.

ping google.com
ancient hemlock
#
github.com/pterodactyl/wings/server.NewManager
        github.com/pterodactyl/wings/server/manager.go:36
github.com/pterodactyl/wings/cmd.rootCmdRun
        github.com/pterodactyl/wings/cmd/root.go:138
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/[email protected]/command.go:987
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/[email protected]/command.go:1115
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/[email protected]/command.go:1039
github.com/pterodactyl/wings/cmd.Execute
        github.com/pterodactyl/wings/cmd/root.go:71
main.main
        github.com/pterodactyl/wings/wings.go:17
runtime.main
        runtime/proc.go:267
runtime.goexit
        runtime/asm_amd64.s:1650```
#

I was able to ssh from outside of my own wifi using my public IP but I can't anymore

lyric root
#

Has your public IP changed?

ancient hemlock
#

only thing that's a bit weird on my server is my systemd-networkd-wait-online.service not being able to go online

#

idk if it has something to do with any of that

#

here my ip a

#

here my ss -tupln

#

here my allow ports on firewall

#

here my port forwarded ports on router

still brook
#

check that there isnt another device on your network with the same ip. Could cause some weird issues

#

restart your router so its forced to update all the IPs of every device.

#

if both are done restart your server again. And check if it works now

ancient hemlock
#

ok I'll do that and come back to you

ancient hemlock
#

what I don't get is why my server has 3 different IPv4

#

when my ip a says :

still brook
#

what did you do to fix your ip to 189?

ancient hemlock
# still brook what did you do to fix your ip to 189?

created a file named sudo nano /etc/netplan/01-netcfg.yaml and deleted /etc/netplan/50-cloud-init.yaml

  version: 2
  renderer: networkd
  ethernets:
    enp0s31f6:
      dhcp4: no
      addresses: [192.168.0.189/24]
      gateway4: 192.168.0.254
      nameservers:
        addresses: [8.8.8.8,8.8.4.4]```
still brook
#

do the wings still give the same error?

ancient hemlock
#

debugging

ancient hemlock
#

but I'm not even sure this has something to do with Ptero at this point because why would I not be able to access my server with SSH if my SSH port is forwarded and I'm using my Public IP

still brook
#

it does not its a networking issue

#

idk why you didnt just fix your ip via your router tho

ancient hemlock
#

pinning an ip adress would be in advanced settings right ?

still brook
#

depends on router to router but yeah probably

ancient hemlock
#

yeah I check every category anyway and it's not there

#

any idea why my router sees 3 different IPv4 coming from my server if my ip a only says it's 189 ?

#

and let's say I wanted to redo everything with a clean install

#

how do I access my server files to back them up

still brook
#

try running this first: ip -4 a

ancient hemlock
#

and what if

#

I forwarded everything to 192.168.0.187

#

which is the IP my server chooses dynamically

#

do I need to change something in ptero config somewhere ?

#

I don't even understand why it changed IP because I only have 3 devices connected on it, my server, my PC and my phone

still brook
#

how did you setup your wings config using your DNS or your public ip?

ancient hemlock
#

used my DNS

#

iirc

#

is there a file I can check to be sure ?

still brook
#

okay if you change your DNS to go to 192.168.0.187 it should work

ancient hemlock
#

so

#

cloudflare DNS ?

still brook
#

/etc/pterodactyl/config.yml

still brook
ancient hemlock
#

my DNS is setup using my Public IP tho

still brook
#

and it didnt change right? Just dubbel check it using whatsmyipv4 or something else

ancient hemlock
#

y y it didn't change

#

checked it multiple times

#

and I'm pretty sure this router has a fixed ip

#

since it literally never changed in multiple months

#

in my config.yml

still brook
#

you can login to your panel right?

ancient hemlock
#

yes

#

but no access to node

#

and no access to the panel at all from an external network

still brook
ancient hemlock
#

host unreachable

still brook
ancient hemlock
#

I open port 187 from firewall ?

#

oh nvm

#

you mean the IP

still brook
#

change 192.168.0.189 tgo 192.168.0.187

ancient hemlock
#

so you want me to port forward from 192.168.0.187 ?

#

but thne I need to make my server go back to 192.168.0.187 as well

gusty trench
#

is you server/pc ip static?

ancient hemlock
#

but I made it static today

still brook
#

just check it bcs its purely a weird networking issue. Maybe the router still thinks its on 187

ancient hemlock
#

it's this morning but restarting the server it switched to 187

#

for some reason

#

so I went and made it static on 189

#

want me to try restarting everything again ?

still brook
#

yeah and today it changed to 187 so try it. there is nothing wrong with trying and seeing if it works. Trouble shooting a DNS issue without directacces is a pain in the ass to help someone with it.

ancient hemlock
#

ok so I change my port forwarding to 187 and my server too ?

still brook
#

just leave the server ass is for now

ancient hemlock
#

kk

#

I'll be back in 5-10 that router literally takes ages to change settings and restart

ancient hemlock
#

running debug right now

still brook
#

yeah its still not connecting

ancient hemlock
#

nope

#

same error

#

pings are not reaching either

still brook
#

what if you change your ip back to 187 on your server.

ancient hemlock
#

ok will do

#

rebooting server

#

when server is booting up my systemd-networkd-wait-online-service doesn't start btw could it be a problem ?

still brook
#

the problem is purely a networking issue.

ancient hemlock
#

but isn't this service network related ?

#

I still get an error

#

but a new one

#

Stacktrace:
listen tcp 0.0.0.0:8080: bind: address already in use
github.com/pterodactyl/wings/cmd.rootCmdRun
        github.com/pterodactyl/wings/cmd/root.go:369
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/[email protected]/command.go:987
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/[email protected]/command.go:1115
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/[email protected]/command.go:1039
github.com/pterodactyl/wings/cmd.Execute
        github.com/pterodactyl/wings/cmd/root.go:71
main.main
        github.com/pterodactyl/wings/wings.go:17
runtime.main
        runtime/proc.go:267
runtime.goexit
        runtime/asm_amd64.s:1650```
gentle drumBOT
#

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.

ancient hemlock
#

I killed all wings and made a new debug

#

does this mean it's connected ?

#

ok apparently yes

#

so the problem now is that it works with 187

#

but I'm back to it being dynamic

still brook
#

yeah but your still not able to connect to your panel from outside of your network

ancient hemlock
#

network:
version: 2
ethernets:
enp0s31f6:
dhcp4: true

still brook
#

okay

ancient hemlock
#

if I change dhcp4 to false

#

will it stick to 187 ?

still brook
#

check your /etc/systemd/network/ directory

ancient hemlock
#

I'm also able to ssh from outside of my network

still brook
#

and then a file called eth0.network or something somilar

ancient hemlock
#

so this is fixed

still brook
ancient hemlock
#

I will

still brook
#

thats probably why it still was looking for 187 bcs it was still set in that file to do so..

ancient hemlock
#

I don't have anything in this directory

still brook
#

okay no clue then

#

but glad it worked. Lock your ip to 187 now. So it stays on that one

ancient hemlock
#

for my netplan

#

to make it fixed

#

do you think I should set dhcp4 to false ?

#
  version: 2
  ethernets:
    enp0s31f6:
      dhcp4: true```
#

OR

#
  version: 2
  renderer: networkd
  ethernets:
    enp0s31f6:
      dhcp4: no
      addresses: [192.168.0.189/24]
      gateway4: 192.168.0.254
      nameservers:
        addresses: [8.8.8.8,8.8.4.4]
#

use this but with 187

still brook
#

false

ancient hemlock
#

k

still brook
#

dhcp4: false and then 187 yeah

ancient hemlock
#

but these are 2 different files

#

I only have first one right now

#

which is the dynamic one

#

jsut setting dhcp to false will fix my IP on 187 then ?

#

I'm gonna try

still brook
#

I dont use netplan to fix my ip so no clue.. but probably yeah

ancient hemlock
#

ok this doesn't work lmao

gentle drumBOT
#

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.

ancient hemlock
#

it just made my eth disappear from ip a

#

switched it back to true

#

will try with other config and setting it to 187

still brook
#

there is probably documentation online. I cant help you with netplan. Just glad that you can connect to wings again

ancient hemlock
#

yep tyvm

#

will try on my side and update here in case it helps anyone

#

ok

#

so

#

I found the original culprit lmao

#

in my netplan file my gateway was set to 192.168.0.254 but it needed to be set to 192.168.0.1

#

which is my router thingy (idk the name)

#

so it was my bad from the beginning

#

[FIXED] failed to load server configurations error

#

but now I have another issue wtf

#

when I run sudo wings --debug my node connects to my panel

#

but as soon as I stop the debug command it disconnects itself

#

ok found it

#

wings service was offline

#

started it with systemctl and it works fine now

#

guess having a brain is useful sometimes