Hey, installation problem
Hello! I wont lie, your speaking to someone who dosent really know what they are doing.
My pterodactyl sys admin has attempted to install blueprint. It broke, and he hasnt been able to fix it, and has cut contact with me. I personally have no clue how to fix it, so any help would be massively appreciated!
Here is what happens, the panel builds with no errors, but when I try and access the panel it returns 503, service unavailable.
Thanks for any help again!
17 Replies
It will be better, if you posted the logs ^
I havent ever used pterodactyl before, I have always had someone do it for me, so I know this will be a really silly questions, but how do I get the logs? So sorry again
tail -n 100 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).logNo such file or directory
Here are the two logs on that dir
Honestly at this time, although blueprint would be nice, if I an somehow uninstall it and get the panel back up im happy
Hm, they hasnt to-do with blueprint at all. ^
Thats what I thought when I looked at them
Any ideas on what I should try?
I really dont want to have to re-install the panel if I dont have to
You can try reinstall blueprint, or find a system operator maybe can help you (free) ^
What system operator would do that for free?
this is not an issue with blueprint, its due to a pterodactyl addon/mod that you have installed
"MinecraftPlayerManager"
production.ERROR: Trying to access array offset on value of type bool {"userId":1,"exception":"[object] (ErrorException(code: 0): Trying to access array offset on value of type bool at /var/www/pterodactyl/app/Http/Controllers/Api/Client/Servers/MinecraftPlayerManagerController.php:87)
Those logs were from days ago looking at the date
Plus that was working 100% fine before the blueprint install
hmm
oh
503
just run
php artisan up
in pterodactyl's directorytry running
php artisan up in your pterodactyl directory
oops
didn't read new messagesThat worked! Thanks! Damn that made me look stupid, thats everyone for the help
no i get it
i'll add it to the troubleshooting docs in the future ;)
Awesome