Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: 500 on reference of Ptera after install 0.10 #953

Closed
kenshin133 opened this issue May 18, 2024 · 6 comments · Fixed by #951
Closed

[Bug]: 500 on reference of Ptera after install 0.10 #953

kenshin133 opened this issue May 18, 2024 · 6 comments · Fixed by #951
Labels
Bug / Fix Something isn't working and may need a fix High Priority Critical. Act quickly for resolution

Comments

@kenshin133
Copy link
Sponsor

kenshin133 commented May 18, 2024

What is your request about?

Ive included install directions in the additional info section.

The main issue here is it seem on fresh installs of the dev branch any page which references pterodactyl results in a 500 error.

Pages like : producs, Users, Servers work fine.
but pages like : Overview, and Settings result in a 500 and the specific error is LONG but starts with either
production.ERROR: Typed property App\Classes\PterodactylClient::$application must not be accessed before initialization {"userId":1,"exception":"[object] (Error(code: 0): Typed property App\\Classes\\PterodactylClient::$application must not be accessed before initialization at /var/www/controlpanel/app/Classes/PterodactylClient.php:115)
or
production.DEBUG: Failed to construct Pterodactyl client, Settings table not available? {"exception":"[object] (Illuminate\\Contracts\\Encryption\\DecryptException(code: 0): The payload is invalid. at /var/www/controlpanel/vendor/laravel/framework/src/Illuminate/Encryption/Encrypter.php:214)

ill include my entire install log, and a log containing only loading one of these pages.

Branch

development

Solution idea

To test, I tried to get some of the variables around what was failing to output and all of them seemed empty, cant be 100% sure but They seemed so.
installer.log
laravel.log

Ctrlpanel Logs

No response

Additional Info

I've verified I have all requirements by following the install doc to get a clean install from main branch.
after testing i've ran to get a clean dev install:

`mysql -e "drop database controlpanel"
mysql -e "create database controlpanel"
mysql -e "GRANT ALL PRIVILEGES ON controlpanel.* TO 'controlpaneluser'@'%'"
mysql -e "FLUSH PRIVILEGES"

envDir="/var/www/controlpanel"
rm -rf $envDir
mkdir -p $envDir
cd $envDir

git clone https://github.com/Ctrlpanel-gg/panel.git ./ -b development

composer install --optimize-autoloader
chmod -R 777 $envDir
chown -R www-data:www-data $envDir`

After this I go to mydomain/install
enter database details, click next, it fails with There was an error after running command php artisan migrate --seed --force Please check the installer.log file in /var/www/controlpanel/storage/logs !

I click again and it continues.

I skip email setup, enter keys/api details normally.

@S0ly S0ly added Bug / Fix Something isn't working and may need a fix High Priority Critical. Act quickly for resolution labels May 18, 2024
@S0ly S0ly linked a pull request May 18, 2024 that will close this issue
7 tasks
@kenshin133
Copy link
Sponsor Author

kenshin133 commented May 18, 2024

The specific errors mentioned there might be a red herring, they show up loading any page..

@kenshin133
Copy link
Sponsor Author

This is resolved at present. thanks to (im guessing) b747b7d

@1day2die
Copy link
Collaborator

yuo. this happens when the settings arent initialized yet or if something went wrong on the settings. sometimes it can be caused by a faulty reinstall where the old appkey is still cached. had the same issue a few days ago, but thats just cause of my dev env

@S0ly
Copy link
Member

S0ly commented May 22, 2024

hi ! have this been resolved by PR #951 ? thanks

@kenshin133
Copy link
Sponsor Author

hi, it has

@S0ly
Copy link
Member

S0ly commented May 23, 2024

Resolved by PR #951

@S0ly S0ly closed this as completed May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug / Fix Something isn't working and may need a fix High Priority Critical. Act quickly for resolution
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants