#My panel just stopped resonding and all my servers as well. I restarted my VPS but itstill wont work

92 messages · Page 1 of 1 (latest)

crimson cloak
#

what can i do? Are their any commands to run that i need ? please help asap

#

im finally now able to connect via Putty but still cant load panel page

crimson cloak
#

@tardy bluff

tardy bluff
#

what's the error in your browser

crimson cloak
#

refused to connect

tardy bluff
crimson cloak
#

its been perfectly fine for over a year

#

which port is default

#

port 80 is open btw

tardy bluff
crimson cloak
#

yeah

tardy bluff
#

are you connecting to panel using http?

crimson cloak
#

https

tardy bluff
#

check https port then

crimson cloak
#

is that 443 and 8443?

tardy bluff
#

just 443

crimson cloak
#

it says closed now

tardy bluff
#

well that's the issue

crimson cloak
#

but i would always connect so idk why it randomly closed

tardy bluff
#

you're connecting through https which defaults to 443 and port is closed

#

you either open it again in your firewall or contact your VPS provider

crimson cloak
#

i have it open on VPS pagelet me try to reopen via putty

#

it says they are already enabled

#

would it be because of cloudflare?

tardy bluff
#

check whether anything is listening on port 443

tardy bluff
crimson cloak
#

how would i do that

#

just dns

tardy bluff
tardy bluff
real beaconBOT
#

You are expected to understand how to read documentation to use this Panel. We have spent many hours detailing how to install or upgrade our software. Please, take some time and read rather than copy and pasting and then complaining when things do not work.

If you expect to be able to install this with no understanding of basic linux system administration you should stop and turn around now

tardy bluff
#

or at least google it

crimson cloak
#

alr hold up

#

nothing happens when i run the command to check wtf

#

i tried sudo netstat -tnlp | grep :22 and lsof -i:443

#

alr hold on i just did list all

#

i dont see it

tardy bluff
#

then your apache is not listening on port 443; check your webserver configuration if you're binding to port 443 or re-copy it from docs

crimson cloak
#

alr

#

hold on im finding the doc to see where its located

#

It wont open wtf

crimson cloak
#

So I just woke up and I went on my weirder and the page loaded but said “An error was encountered by the application while rendering this view. Try refreshing the page.”

#

I refreshed and it can’t connect at all again

#

It’s so weird

tardy bluff
crimson cloak
#

Nope

tardy bluff
#

try in private tab then

crimson cloak
#

I wasn’t able to check the web server config yesterday either as it was late but it’s weird it loaded then stopped working again I’m going to have to double check after work

crimson cloak
#

Doesn’t load

real beaconBOT
#

There were too many logs to read @crimson cloak. Please post 5 or less. Alternatively, please share larger logs using paste sites, such as pteropaste or hastebin.

crimson cloak
#

@tardy bluff

#

i got it

#

for some reason apache started

#

so i stopped it and started nginx

#

do you think its because of vps restart?

thorny socket
#

Disable it if you don't want it running on boot.

sudo systemctl disable --now apache2

crimson cloak
#

thank you for that

#

also what else is apache used for

thorny socket
#

It's an alternative to nginx, just a webserver and reverse proxy. You only need one of them.

crimson cloak
#

oh alr

#

well i think everything is good im just going to see what msmaciek is going to say if they need to then close it

#

thanks for the command

thorny socket
#

No problem

crimson cloak
#

well it crashed all servers after a few minutes

#

so not fixed

crimson cloak
#

panel wont work any more again uhhggg

#

and nginx is using the 80 and 443 port so idk why its not loading

crimson cloak
#

i have to force restart it again and it works now

#

do you think its because its overloaded?

vital summit
#

Type htop

#

And see ram + cpu usage

crimson cloak
#

it seems fine now

#

oh wait

#

hold on wrong vps

#

here it is

vital summit
#

Nope

#

Not due to overload

crimson cloak
#
[Pterodactyl Daemon]: Checking server disk space usage, this could take a few seconds...
[Pterodactyl Daemon]: Updating process configuration files...
[Pterodactyl Daemon]: Ensuring file permissions are set correctly, this could take a few seconds...
container@pterodactyl~ Server marked as starting...
[Pterodactyl Daemon]: Pulling Docker container image, this could take a few minutes to complete...
Pulling from pterodactyl/yolks 
Status: Image is up to date for ghcr.io/pterodactyl/yolks:java_17 
Digest: sha256:7f64ec51cd8363376f377b93efcde9bf1ff975103305aa94cd029efacbeb3a45 
[Pterodactyl Daemon]: Finished pulling Docker container image
container@pterodactyl~ Server marked as offline...
container@pterodactyl~ Error Event [e2168e56-5f17-4b5e-8997-e69e618ebe76]: environment/docker: failed to start container: Error response from daemon: driver failed programming external connectivity on endpoint 7b146ec4-5f4c-4deb-9a6b-4be8a1e76645 (af42cf5802e6afa910d038f281edc66b55d1cff39787627020a2a24d225f74d4): Error starting userland proxy: listen tcp4 146.235.215.131:25500: bind: cannot assign requested address
[Pterodactyl Daemon]: ---------- Detected server process in a crashed state! ----------
[Pterodactyl Daemon]: Exit code: 128
[Pterodactyl Daemon]: Out of memory: false
[Pterodactyl Daemon]: Aborting automatic restart, last crash occurred less than 60 seconds ago.
real beaconBOT
#

At your service, @crimson cloak!

The IP address you have assigned to your server is not actually available for use on your machine. Node allocation creation is explained in the Wings install documentation: https://pterodactyl.io/wings/1.0/installing.html#node-allocations

Execute the command hostname -I | awk '{print $1}' and change your Node allocations to use this IP. Yes, it can be your internal/local IP when you're behind NAT. When behind NAT you will allocate the internal IP and connect using the public IP.

If you have added multiple public IPs to your network interface, you can view all of them using the command ip a | grep "inet "

crimson cloak
#

hmm i think i know whats wrong

upbeat lion
crimson cloak
#

i think i accidenlty put the public ip instead of local ip as in 10.0.0.175

#

im transfering files now to new node then testing