If you've ever set up a WordPress site or configured a PHP application, there's a good chance you've typed localhost into the database hostname field without thinking twice. It's one of those habits that sticks — and for good reason, because it works on a lot of hosting platforms.
But if you're hosting with Cyberin, localhost won't work. And understanding why actually tells you something useful about how Cyberin's infrastructure is built.
When you use localhost as a database hostname, you're essentially telling your application: "the database is on the same machine as the website."
In traditional shared hosting setups, that's exactly what's happening. The web server and the MySQL server sit on the same physical machine, so everything talks to everything else locally. Simple, straightforward, and common.
The problem is that this "one machine does everything" approach has real limitations — in performance, security, and reliability. Cyberin takes a different approach entirely.
Cyberin follows what's called a "One Server, One Role" policy.
Rather than cramming your website, database, and storage onto a single machine, Cyberin separates everything across dedicated servers. Your web hosting runs on one server. Your MySQL databases live on another. Storage and network services are handled separately too.
This separation exists for very good reasons:
Performance — Database traffic and web traffic don't compete for the same resources, so both run faster.
Reliability — If one service is under heavy load, it doesn't drag everything else down with it.
Security — Isolated services mean a problem in one area is far less likely to affect another.
Scalability — Each part of the infrastructure can be upgraded independently as your needs grow.
It's a more modern, enterprise-style architecture — and it's genuinely better for your website's stability and speed. The trade-off is that localhost simply doesn't point to anything meaningful, because your database isn't on the local machine at all.
Instead of localhost, you need to use the remote database hostname that's assigned to your hosting package.
It typically looks something like this:
shareddb1b.hosting.stackcp.netYour exact hostname will depend on which server your account is allocated to, so don't copy that example directly — you'll need to grab the one specific to your account.
It's easy to locate inside your Cyberin hosting control panel. Here's how:
Log in to your Cyberin hosting account
Open your hosting package dashboard
Click on MySQL Databases

Find the database you created
Copy the hostname listed there
That's the value you'll use wherever your application asks for a database hostname.
Once you have the correct hostname, your database connection settings will look something like this:
Database Name: example_db
Username: example_user
Password: your_password
Hostname: shareddb1b.hosting.stackcp.netYou'll plug these values into whatever you're configuring — the WordPress wp-config.php file, a CMS installer, a PHP connection script, or any other application that needs database access.
If you try to connect using localhost on Cyberin, your application won't be able to find the database server and you'll typically run into one of these errors:
Error establishing a database connectionor
Access denied for userBoth of these can feel confusing at first because they look like credential errors — but more often than not, the hostname is the actual culprit. Swap localhost for your correct remote hostname and the connection will usually go through cleanly.
Using localhost is a deeply ingrained habit for anyone who's set up websites before, so it's an easy mistake to make. But on Cyberin, the database and web server are intentionally kept on separate machines — and that separation is what makes the hosting faster, more stable, and more secure.
Whenever you're setting up a new website or application on Cyberin, just head to the MySQL Databases section in your hosting control panel, grab the hostname listed there, and use that instead. It's a small change that makes everything work the way it should.