pterodactyl build failed with nebula
live laugh slowmode
post created for @Partymann2000
15 Replies
ok now i see this on my panel site
Nebula was unable to initialize because it couldn't access the app node. This usually indicates a failed webpack build and is usually indicated by a blank page on stock Pterodactyl instances. Administrators might be able to identify the exact problem by running blueprint -rerun-install and watching for errors.
Please note that this error is commonly not caused by Nebula due to the theme being a shell around Pterodactyl and doesn't modify any part of it's bundle, hence why we're able to show this error to you.
Feedback Nebula
( ._.) INITIALIZATION_FAILED
i use nebula 2.0-1
after i upgarded to the lastest blueprintrun
blueprint -rerun-install to see yarn logsi do it same
wait i send
Which extensions do you have installed?
alot
Alright so
remove extensions one-by-one until you don't get errors anymore
if you run the
source blueprint command you can use your TAB key after -remove to see removable extensions in the blueprint -remove commandnoew it works after i reinstall all ext 5 times 🙂
no stop
did it break
i have a new one
sob
i found the s*** extension its the last one i remove 🙁
This Extension not work
- monacoeditor
where did u download it from
Hey, that one replaces core files which is probably why it broke after an update iirc, this one should work https://blueprint.zip/browse/pteromonaco