Problem after panel upgrade
I used blueprint -upgrade and now the client side panel works, but admin does not load anything and I get error 500. I originally had installed modpack installer and it didn't work right and bugged the client side. So I tried upgrading to the patched version (I was on F248) and here I am now.
51 Replies
Resolved part of my issue, but reinstalling my extensions now is a pain. I'm having issues with each one.
I'm seeing this visual bug whenever I click extensions page.
R u behind cf proxy
no
Did you try clearing your cache?
Made it worse
This is how nebula looks right now
on client side
Wtf
Try reinsing nebula with blueprint -install nebula
Yeah just removed it for now because its so broken
I already did that 3 times
Oh
Is there something in the browser console? @AssaultLine
I'll check
Thats installation though, only thing at the beginning was that one error
And all my stuff doesn't run as www-data
I use Plesk so its ran under different user
I had all this working fine and I went and screwed with modpack installer and it broke one thing and now all the things are broken lol
This was right after I just reinstalled nebula
Not even sure what to do now, and my dumb ass did this on my live panel.
Think any of these relate to it?
Its 403 for any blueprint logos
I'm wondering if it does the same whenever I install nebula
It's 100% a perm issue
I'm setting the entire directory and all files/folders within to the proper user/group
Try setting the owner var
I know its right because the whole panel doesn't even load up if I don't have it right
Plesk must be ran as the user that the "site" is installed under.
Those 403 are acting like its not even reading those files though
blueprint.zip
Powerful, fast and developer-friendly extension framework for Pterodactyl. Utilize extension APIs, inject HTML, modify stylesheets, package extensions and so much more.
I was getting 500 when it was the permission issue
Look at the configuration section
Try to set the user before running any bp command
Oh so I can change that in the blueprint.sh?
Yep
I was manually going and fixing perms after every install lol
Lol
Let blueprint handle it's magic
I see an issue, I hope this will fix it though. Its not setting the proper permissions/user on .blueprint and a few other files in main directory whenever I try to run that command.
Fixed some of them, but the overall site is still not working
š§āāļø
Slate worked fine
So its unique issue with Nebula I think, I'll try a couple other addons
I guess I should just ask @Emma then what is the best method to reset or just clear out things with nebula? I'd really prefer if I could at least keep the config settings, but if not then oh well.
Other addons seems to be working fine, just issue when Nebula theme is applied.
Just a quick question, why don't you run it on a normal VM?
I've never understood the point running it in plesk
remind me to reply tomorrow
Remind me to remind you to reply tomorrow
Thanks
Just another cost
I run a bunch of other sites so Plesk was already there
Any other tips about fixing Nebula ^ this is what it looks like when I install the nebula theme.
pls don't forget to reply, still not sure whats causing the nebula only issue.
im so confused
Oh btw
could you give a summary
Hi ivy
I'm reminding you to reply
Thanks for reminding me that this exists
Alright so started out I installed modpack installer and it bugged my client side panel. So I ended up doing blueprint -upgrade to get the new patched version (I was on that bugged F248 version prior) And now I'm attempting to reinstall all the extensions and the only one I'm having an issue with is Nebula. That screenshot above is what client side looks like. The background is meant to be black, but you can see all the tabs on the left are all broken code at the bottom.
@Emma The summary is above
She's probably busy
I still haven't figured this out
im so sorry for missing this
have been busy
could you try installing an older version of nebula?
Still was acting weird and gave me 403 error on my Plesk when trying to load the panel nebula editor.
I tried to do what you said with installing an older version and the above happened. What would be the best option to just get a fresh install of Nebula running?
Probably, yeah.
I'm not sure what could be giving you that error honestly.
I made sure that the blueprint.sh file had the proper user and group set for my server configuration. Its setting up everything correctly and any other extensions installed fine, Nebula was the only one that caused me any issue.
This is how Nebula determines whether or not you are authorized to view a page in Designer.
Something might be preventing it from detecting you as an administrator. What exactly, I'm not sure.
Would running these help at all?
php artisan view:clear
php artisan config:clear
I tried doing it again and still get 403 error, I'm trying to find log to read more into what is causing the error.
Fixed it, was an issue with a certain path being blocked on nginx/apache with my Plesk install. I added an exception for the specific extension path it was trying to access and it worked fine installing the theme after that. What a pain that this took me 2 weeks of screwing around to figure out though lol.
Glad you ended up finding the solution. Yeah, definitely couldn't have guessed that being the problem.