Short answer: No — at Amicatek you must use the database hostname provided for your package, not 'localhost'.
Why 'localhost' doesn't work at Amicatek
Many hosts run databases on the same server as web sites, so 'localhost' works there because the database server is on the same machine as the web server. Amicatek uses a split infrastructure where different services run on separate physical or virtual servers. Web servers, database servers and storage servers are separate. Because of this "one server, one rule" policy, 'localhost' does not point to your database server and will not work.
How to find the correct database hostname
To find the hostname for your database:
- Log into
https://cp.amicatek.link - Click Manage Hosting
- Select your hosting package
- Open the MySQL Databases icon (or similar)
- Look for the database details — the hostname will be listed there
Example hostnames look like
sdb-123.hosting.stackcp.net. Your actual hostname will be different — copy it from the control panel and use it in your application configuration.
How to update your application
Use the hostname you found in the previous step in your application's database configuration. Example settings:
DB_HOST = sdb-123.hosting.stackcp.net
DB_NAME = your_database_name
DB_USER = your_db_user
DB_PASS = your_db_password
Troubleshooting connection errors
- If you get a connection refused or host not found error, double-check the hostname and whether the database exists on your package.
- If you see access denied errors, verify username and password and that the user has privileges for the database.
- Some applications default to 'localhost' — update the configuration file or environment variables to use the correct hostname.
Need help?
If you're unsure which hostname to use or if you can't connect after updating your settings, contact Amicatek support through cp.amicatek.link and provide:
- Your package name
- Database name
- The hostname you're trying to use
- Any error messages you receive