#500 | server error
12 messages · Page 1 of 1 (latest)
Hey @sudden cargo! Post your Panel logs to find out more information about the cause of your 500 server errors tail -n 150 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc pteropaste.com 99
I have found the following for: https://ptero.co/ifulilawoq
🇫🇷 🥖 Bienvenue sur Internet, @sudden cargo 🥖 🇫🇷
Your database is refusing the Panel's attempts to connect to it. This can be for a number of different reasons so I'll let a human double check, but here are some ideas.
- Is your MySQL instance running?
systemctl status mysql(hopefully not down the road) - Is the user you're trying to connect with authorized to access the given database from this IP address?
- Did you correctly give that user permission to even access that database?
- Do you have a Firewall that is blocking connections?
- Is your MySQL instance bound to
127.0.0.1orlocalhostand you're trying to connect from outside the server? - Does the user have
GRANTpermissions if you're trying to use them to create a new database for a server? - Have special characters in your password? Make sure DB_PASSWORD in your .env file is enclosed in double quotes
Here is some additional documentation to help you out: https://pterodactyl.io/tutorials/mysql_setup.html
I'm using mariadb and the docker compose
if you are connecting to the database (on panel) locally, ensure that the database ip is the local ip.
if you are using external database connection for the panel, then make sure that the database accepts connections from all incoming or your specific server.
panel - database should not be exposed
how do I check that, I'm using docker compose so most the networking should be handled by that
;-;
in the .env file inside of the ptero web folder
The env file can be found at /var/www/pterodactyl/.env. Files starting with a . in Linux are hidden so it may not show up in file browsers by default. You can open it directly with nano /var/www/pterodactyl/.env
I managed to figure it out, seems to be an issue with the official docker image, building one with the changes from #5324 seems to fix it