Error 500
After installing the panel and trying to build, this happened:
root@panel-kyonix:/var/www/pterodactyl# php artisan up
In Connection.php line 760:
SQLSTATE[HY000] [2002] Connection refused (Connection: mysql, SQL: select * from information_schema.tables where table_schema = panel and table_name = migrations and table_type
= 'BASE TABLE')
In Connector.php line 65:
SQLSTATE[HY000] [2002] Connection refused
root@panel-kyonix:/var/www/pterodactyl#
SQLSTATE[HY000] [2002] Connection refused (Connection: mysql, SQL: select * from information_schema.tables where table_schema = panel and table_name = migrations and table_type
= 'BASE TABLE')
In Connector.php line 65:
SQLSTATE[HY000] [2002] Connection refused
root@panel-kyonix:/var/www/pterodactyl#
14 Replies
This is unrelated to Blueprint. Your database is unreachable.
She's standing on this f host
Maybe it's because she has a custom port? Not 3306
Who are you referring to?
I changed it recently and changed it in the .env panel at var/www/pterodctyl
MariaDB Database Port
Yeah this might be the issue
might have to wait until someone with more knowledge about databasing than me reads this
There are no problems in the port itself. And pterodactyl itself works normally. Maybe it's about configuring the database port in the blueprint itself? Should he have access to it?
Maybe it is specified somewhere in the config?
Check MariaDB logs to find out why it's refusing. If there's nothing about this in the logs, it's a network issue.
I have returned the port to the standard one. The error is gone. How do I get it back to the caste so that there is no error?
I'm not sure what you're asking.
By default, the Mysql database runs on port 3306. But for the sake of safety, I'm changing it. Then the panel works on port 7306 (fictional). After I change the connection data in .env, but blueprint gives an error
Using non-standard ports does NOT harden your machine by a large enough amount to be recommended; anyone can still see what ports are open, then look at the response given to see what service is running. It's not a substitute for setting up TLS encryption and restricting access to users and services who actually need it with permissions and your firewall.
With that being said, in typical Pterodactyl you would just change it in MariaDB's config, restart the service, change it in your .env file, restart your webserver, and you'd be set. It's possible Blueprint caches the setting somewhere; I'd cd into /var/www/pterodactyl and run
grep -ir "3306" . to check.The ports are closed, but the database will be used elsewhere. Connection to this port will be limited to certain IP addresses of the balancer and other system components.
As far as networking, it just uses the panel user I believe; if your panel is working, your blueprint database connection should be working.
I thought so too, but no