82 Replies
I managed to fix the encryption key, but I just need to setup my .env
The theme worked perfectly fine before, and I'm wondering why I'm recieving this error, I would like to purchase the nebula theme for it, but I don't think that will resolve it.
If you nano to your
.env file in the /var/www/pterodactyl directory, is there a APP_KEY field?Oh sorry yes I fixed that earlier,
It's just the theme issues im worried about
It did work before but not now
as in the
ERROR in resources/scripts/state/server/index.ts:1:35 type of errors
So I reset my template to the default pterodactyl theme, and it seems to be an issue with that,when using export NODE_OPTIONS=--openssl-legacy-provider and then yarn build:production, this also happens when using blueprint -rerun-installDid you have any non-blueprint extensions before?
Nope, this is a fresh install
I've just install pterodactyl and wings, and then started installing blueprint, nothing else
Well probably get some screenshots, I don't really understand what's your issue
Do the ones at the top not help?
I'll open console and do
blueprint -rerun-install if that helps?Oh I didn't see
Try
blueprint -upgradeI've run that and blueprint re installs, yet I still get this error:
This is using the default Pterodactyl theme / folder config
it gives the same error when running yarn build:production
ok
Ok so I get these errors:
It's less errors
I've done it
byte snippet-upgrade
1. Remove certain files and directories with
rm -r resources public node_modules.
2. Go through the Pterodactyl update documentation.
3. Install dependencies by running the yarn command.
4. Repair Blueprint with blueprint -upgrade.
5. Get some Blueprint extensions (if you haven't already) and install them onto your panel.byte snippet-upgrade
So i've done that, I just need help setting up my databases in my
.env
Everything builds fine
I just need some helpSo you did all of these?
Yes and it worked
So this is my .env
This is my mariadb
This is my redis
And I get this error:
Use localhost for redis host
??
I did and that worked, now what does this mean? ^
I have no idea
I'm asking claude xD
apparently redis doesnt need a password when running locally
Oh try setting the password to
nullYou can just remove it entirely
Just fixing my mysql and hopefully that works!
Any idea?
--------------------------
So, my website now doesn't start / load
There is no errors in the blueprint, no errors in laravel all it says was about the encryption key which I fixed???
When I build it there is no errors?
Oh I found the errors they were located in pterodactyl console:
Here is my .env
@ℓєzєтнσ or @root@david1117:~# can you help?
Yes
firewall i believe
loki can probably confirm
What port do I let through?
Is this a port for blueprint?
Because it was working before?
Check the status of your Redis container. If it's up, change the host to the gateway IP of the network it's on. The container name seems to be routing to localhost.
What's the gateway ip?
Redis is running in docker and so is pterodactyl?
Only you know what network Redis is on and what subnet that network uses.
What command do I do?
Routing to the container name should be working as is... is your panel connecting to MariaDB successfully?
So this is the current error
Is the name really crafty_panel-redis?
yes
docker container inspect crafty_panel-redis
What does it say for gateway?Well that's interesting?
There's your problem
The container either isn't up, doesn't exist, or isn't named that.
I'm not talking about redis
im talking about maria
Ive fixed this
I mean this one
MariaDB worked fine in the snippets you shared.
What errors are you seeing?
Ohhh
Sorry i misunderstood
I thought port 6783 is maria
its 3306 mb
Back to this then
The container is up, and it exists
the containers name is
de7def9df163Is that going to change, or is that name permanent?
I'm not sure? But will this help?
The name will only change every time i redeploy an instance of the maria db, which i'll never do
If you're not sure, you can use the gateway instead. Back to this, but with the correct name.
Here is the commands output
You should absolutely be updating your containers regularly, even if you're staying on the same tag. Keeping your packages to you date is the easiest and most effective way of securing your server.
Yes of course
But why can't it find the server? Do I need to allow the port on my firewall, its only internal though??
You had the wrong name. There was nothing there. Change REDIS_HOST to
crafty_panel-redis.1.uampq8nrlj3kgv0hhwxv9b9vg and it should work. It appears to not have a gateway address based on that output... never seen the before, but DNS seems to work on your setup.Also will have to do that for mariadb
I mean it looked like the name was correct for MariaDB. Your screenshot showed that it connected fine.
Perhaps you named the MariaDB container mariadb when you made it, but forgot to name the Redis container?
No I didn't build the containers, my webpanel did, it appears it names them differently
So redis returns this
and this is redis console
It shouldn't be trying to reach localhost. Your networking is screwed up somewhere, and the Redis container appeared to not even have a gateway. Are you using host mode for it?
Omg
I put in the wrong name xD
Ah. That would do it xD
What??? It still retuns this error
What's wrong?
Does it need a password?
It still gives the same error with the password
Yes, your Redis container is taking a variable for a password. It trying to connect to localhost is still wrong though. Try the short container name for REDIS_HOST.
Still the same error?
Idk then, this is specific to Crafty. I don't use that panel.
No it's called easypanel
Specific to that then
My friend set it up
Ok
I'll contact them
I've contacted them just waiting to hear back