Blueprint 500 server error after installing extension
40 Replies
I'll just quickly compare this to mine.
Do you get any errors when running a Blueprint command?
@Element Do you get any errors when running any Blueprint command?
When I run blueprint -install or -remove the only error is the permissions but that's just because the install script assumes Debian
And I manually set the correct permissions afterwards
Is this only one error?
Only one I noticed
Alright, that's expected.
Want me to reinstall recolor and check?
Yeah
Go ahead.
Is it still the same problem on the admin page?
The theme is there but still throws a 500

Affirmative
Let me just get the correct path rq.
Another thing that seemed to have happened after I ran the upgrade command is everytime I load the admin page it shows

Mind showing me an
ls -a
of the following folders?
.blueprint/data/extensions
.blueprint/data/extensions/recolor
app/Http/Controllers/Admin/Extensions
app/Http/Controllers/Admin/Extensions/recolor
resources/views/admin
resources/views/admin/extensions/recolor
And the contents of the following files:
resources/views/admin/extensions.blade.php
resources/views/admin/extensions/recolor/index.blade.php
routes/admin.php
Expected behaviourThank you, I'm going to read the output real quick, give me a couple minutes.
It appears that something in Rocky Linux is making the Recolor route look like this:
You'll need to change that to this:
I'm not sure what is causing these weird routes. Could you try changing them and then reloading the Blueprint extensions page?
Actually I think the output of cat just bugged
Unless that's wrong?
That appears to be correct.
That's what it is
So I guess cat just messed up
Could you go into your .env and enable debug?
It might be, yeah.
I assume it's this you want
"Route [admin.extensions.recolor.index] not defined."
This seems to be the problem.
Yeah
Could you try this?
It should fix the issue you are facing.
That did seem to fix it 🤔
I wonder what caused it

Blueprint uses echo to put the routes at the bottom of the file.
Didn't read that "everytime" part. That isn't expected behaviour.
Yeah
Happens everytime I load it
iirc that also relies on echo, so it might have to do with echo being annoying
Hm okay
Didn't seem to do it until I ran upgrade
I don't exactly know how that could happen honestly
Wait, I might know why.
Are you running Pterodactyl in something other than
/var/www/pterodactyl
?Negative
Strange. Then I have no clue what the problem could be.
Well at least the original issue is fixed
Fixed it by setting the contents of
.blueprint/data/internal/db/onboarding
to nothingalright