#Questions
1 messages · Page 1 of 1 (latest)
The dev is on break, give it a while, for now you can downgrade
Download panel.tar.gz from https://github.com/pterodactyl/panel/releases/tag/v1.11.11 and run these 2 cmds
And then just follow ptero install guide
If that doesn't work you might also have to downgrade composer deps by doing COMPOSER_ALLOW_SUPERUSER=1 rm -rf /var/www/pterodactyl/vendor && composer install --no-dev --optimize-autoloader
definitely not a such a great idea
The only concerning one is TOTP, as for the SFTP thing, permissions not being resynced is a bit concerning but I think I can count on one hand the amount of people that use the server sharing stuff
As for the final 3, blueprint will probably be fixed by then lol
Also one of the known ones is a wings bug that probably didn't even take any panel changes
Me using wings-rs:
You don't have an encryption key in your .env file
how to fix it?
Add an encryption key to your .env file
how?
Google it
ok
This is basic pterodactyl stuff that you should have done when installing pterodactyl
That is unofficial and not supported iirc
But those 90% of those people know what they are doing
right
If they use it they should not be running a host
i generated the encryption key btw
Any good sysadmin should know and understand the things that they are doing to install software. If they are using the ptero install script, I fear the other practices they may be ignoring
Honestly it's pretty simple, like I don't understand that clearly how to run ptero on docker but that's just skill issue since I'm not that familiar with docker itself
It isn't as bad when its docker since its containerised, but if you are running anything on the system itself you should know what is happening
Still, if they used an install script it could mean that they are doing other things like not properly configuring things like firewalls, fail2ban, and other basics
Anyways, enough of my rant, this is defo not the right channel for that lol
Temporary fix
Use the following command to update to the latest commit of the pterodactyl-v1.12 development branch:
blueprint -upgrade remote blueprintframework/framework pterodactyl-v1.12
https://github.com/BlueprintFramework/framework/pull/197
For AnswerOverflow readers
If beta-2026-01 is already out by the time you read this, just use the blueprint -upgrade command and you'll be fine :)