Missing initial files/permissions issues on install

Hello! Having issues running bash blueprint.sh inside the pterodactyl folder. Pterodactyl version: 1.11.5 Steps I've taken: - Download zip - Unzip to /var/www/pterodactyl - Run chmox +x blueprint.sh (inside pterodactyl folder) - Run bash blueprint.sh (inside pterodactyl folder) Result: A few lines of the similar to the below, and then the below
blueprint.sh: line 221: /var/www/pterodactyl/.blueprint/extensions/blueprint/private/debug/logs.txt: No such file or directory
blueprint.sh: line 222: cd: /var/www/pterodactyl/public/assets/extensions: No such file or directory
[FATAL] Tried to navigate to a directory that does not exist, halting process.
blueprint.sh: line 221: /var/www/pterodactyl/.blueprint/extensions/blueprint/private/debug/logs.txt: No such file or directory
blueprint.sh: line 222: cd: /var/www/pterodactyl/public/assets/extensions: No such file or directory
[FATAL] Tried to navigate to a directory that does not exist, halting process.
After creating logs.txt and the public/assets/extensions folder manually, running bash blueprint.sh gives a load of permissions issues even when pterodactyl is already owned by www-data. (I have also tried chown as current user). Running sudo bash blueprint.sh (which I'd prefer to not have to do) does get me further, and installs, however I then get the following (full section attached as text and image):
ERROR in ./resources/scripts/components/App.tsx
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: /var/www/pterodactyl/resources/scripts/components/App.tsx: Package subpath './lib/node' is not defined by "exports" in /var/www/pterodactyl/node_modules/postcss/package.json
ERROR in ./resources/scripts/components/App.tsx
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: /var/www/pterodactyl/resources/scripts/components/App.tsx: Package subpath './lib/node' is not defined by "exports" in /var/www/pterodactyl/node_modules/postcss/package.json
ERROR in ./resources/scripts/i18n.ts
Module not found: Error: Can't resolve 'i18next-http-backend' in '/var/www/pterodactyl/resources/scripts'
ERROR in ./resources/scripts/i18n.ts
Module not found: Error: Can't resolve 'i18next-http-backend' in '/var/www/pterodactyl/resources/scripts'
ERROR in ./resources/scripts/i18n.ts
Module not found: Error: Can't resolve 'i18next-multiload-backend-adapter' in '/var/www/pterodactyl/resources/scripts'
ERROR in ./resources/scripts/i18n.ts
Module not found: Error: Can't resolve 'i18next-multiload-backend-adapter' in '/var/www/pterodactyl/resources/scripts'
ERROR in ./resources/scripts/index.tsx
Module not found: Error: Can't resolve 'postcss-loader' in '/var/www/pterodactyl'
ERROR in ./resources/scripts/index.tsx
Module not found: Error: Can't resolve 'postcss-loader' in '/var/www/pterodactyl'
As well as some extras. Ultimately ends with [SUCCESS] Blueprint has finished it's installation process.
30 Replies
Phedona
Phedona2y ago
missing dependencies?
Emma
Emma2y ago
I usually run Blueprint as root, which is not that safe but it does usually make it run better. If it tries to navigate to a directory that does not exist, it will halt to prevent data loss. Either way, try running blueprint -upgrade as root if you are comfortable doing so, because it might fix some things.
Jabraham
JabrahamOP2y ago
Initial issues running as root (no such file or directory etc.)
No description
Jabraham
JabrahamOP2y ago
No description
Jabraham
JabrahamOP2y ago
Excuse the poor console, don't have SSH enabled for root
Emma
Emma2y ago
Insanely weird, could you show an "ls -a" for the Pterodactyl directory?
Phedona
Phedona2y ago
"su -" for root
Emma
Emma2y ago
Windows: reboot Linux: be root
Jabraham
JabrahamOP2y ago
Yeah, I thought I'd lost and forgot the root password but have just figured it out lol
Jabraham
JabrahamOP2y ago
No description
Emma
Emma2y ago
Blueprint's folder is missing. weird but "tools" exists, which is also from blueprint
Phedona
Phedona2y ago
blueprint re-run-install
Jabraham
JabrahamOP2y ago
Yep. The folder obviously exists in the zip also
Emma
Emma2y ago
not really useful in this case
Jabraham
JabrahamOP2y ago
It's blueprint -rerun-install and I have done
Emma
Emma2y ago
yeah it's just rerunning the "bash blueprint.sh" thing could you try manually copying the blueprint folder from the zip file?
Jabraham
JabrahamOP2y ago
Sure, what command should I run after?
Emma
Emma2y ago
blueprint -rerun-install to test if asset building fails and stuff
Jabraham
JabrahamOP2y ago
initial issues before asking if I want to migrate the database is again, no logs.txt file
Jabraham
JabrahamOP2y ago
No description
Jabraham
JabrahamOP2y ago
Same issue The new section in the UI is showing though
Emma
Emma2y ago
i think that issue in red is related to dependencies might be best to rm the node modules folder and run "yarn install"
Emma
Emma2y ago
either way i'm gonna have to sleep now embed perms are done on a per-member basis lol
Jabraham
JabrahamOP2y ago
No worries, really appreciate the support still
Emma
Emma2y ago
alrighty gn
Jabraham
JabrahamOP2y ago
gn
Cam
Cam2y ago
If you only have pterodactyl and nothing else, like add-ons. It may be worth backing up your pterodactyl installation and "updating" the panel using the update docs
Jabraham
JabrahamOP2y ago
I had it working, although after then installing Nebula, the UI wouldn't load correctly. After removing Nebula, the UI would just give a white page, and it was an empty view that was served 🤷‍♂️ . I've started from a fresh install of Pterodactyl and seeing how this goes Yeah, currently doing that 🙂, although instead of just updating, doing a bit of a "soft" reinstall I can provide more details if necessary, but with a fresh install of Pterodactyl, I've still had to do the following things to get Blueprint working:
$ mkdir public/extensions
$ mkdir .blueprint/extensions/blueprint/private/debug
$ touch .blueprint/extensions/blueprint/private/debug/logs.txt
$ mkdir public/assets/extensions
$ mkdir public/extensions
$ mkdir .blueprint/extensions/blueprint/private/debug
$ touch .blueprint/extensions/blueprint/private/debug/logs.txt
$ mkdir public/assets/extensions
And for Nebula:
$ mkdir .blueprint/tmp
$ mkdir .blueprint/tmp
All seems to be working okay now.
Emma
Emma2y ago
might be better to symlink these directories instead of making them nvm only counts for some subdirectories

Did you find this page helpful?