Reading Your Hosting Control Panel

The screen nobody reads

You log in perhaps twice a year, usually because something is wrong, and are presented with forty icons in categories that mean nothing.

So you close it and telephone somebody, which is a reasonable response and leaves you dependent on that person for things you could do in a minute.

The useful position is not understanding the whole panel. It is knowing where six things are, so that when somebody asks you to check something you can find it.

That is twenty minutes of orientation, done once, at a moment when nothing is broken.

The six worth knowing

• File manager: where the website actually lives.
• Databases: what the site stores its content in.
• Email accounts: what exists and how full each is.
• Backups: what the host holds and how far back.
• Error logs: what the server recorded when something failed.
• The certificate: its status and expiry date.

Between them those answer most of the questions a supplier will ask you, and looking at any of them changes nothing, which makes them safe to explore.

Where the site actually lives

The file manager is the one worth opening first, because it makes the abstraction concrete.

Your website is a folder of files on a computer somewhere, and the file manager shows you that folder.

It usually sits in a directory with a name like public html or www, and everything inside it is what visitors can reach.

Seeing that once explains a great deal: why a file uploaded to the wrong place does not appear, why a folder name shows up in an address, and what somebody means when they say the site is on the server.

Look, and do not move anything. Dragging a folder in a file manager is one of the few actions here that can take a site down.

Email is usually here too

The section that produces the most avoidable problems and is the least expected.

On most small business hosting, the email accounts on your domain are managed in the same panel, not somewhere separate.

Which means this is where you find out how many addresses exist, which ones nobody uses, whether any are near their storage limit, and where forwarding rules have been set.

A full mailbox stops receiving mail silently, and that is the single most common hosting-adjacent failure a small business experiences.

Check the usage figures once a year and you will avoid it.

A worked example

A business could not receive enquiries from their website form and assumed the form was broken.

Their developer was away, so the owner logged into hosting for the first time in two years to look.

The email section showed the address the form sent to at its storage limit, having been full for eleven days.

The form had been working throughout and the mailbox had been silently rejecting everything.

Clearing it took ten minutes and eleven days of enquiries were unrecoverable.

The owner's remark was that they had assumed the panel was for technical people and it had contained the answer in plain language on the first screen.

What not to touch

Worth stating so the exploration is safe.

Anything described as DNS, name servers, or zone records, which control where your domain points and can take email and the site down together.

Anything about PHP versions or server configuration, which can break a site instantly and is not obvious to reverse.

Database tools beyond looking, since editing a database directly is how content disappears.

And any account or user management, which can lock you out of your own hosting.

Look at all of it. Change none of it without somebody who knows what it does.

Get your own access

A point that matters more than any of the above.

A meaningful number of small businesses do not hold their own hosting login, because a developer set it up on their own account years ago.

That is a problem regardless of how good the relationship is, and it is the same problem as not holding your domain.

Ask for the login, in your own name, on an account billed to you, and store it in your password manager.

If the answer is that it is on the supplier's reseller account, ask what would happen if they were unavailable, and treat the response as information about the arrangement.

If somebody else manages it

Which is common and entirely reasonable.

You still benefit from being able to look, because it turns a support conversation from a description into an observation.

Being able to say the mailbox is at ninety-eight percent, or the last backup shown is from Tuesday, saves a round trip and occasionally solves the problem.

It also lets you verify things you are told, which is not distrust so much as ordinary diligence.

Ask for read access if full access is not appropriate, which most managed hosts and suppliers will provide without difficulty.

The counter-case

There is a version of this that causes damage.

An owner who learns enough to feel confident and then changes a setting during an incident, without understanding it, produces a worse problem and one that is harder to diagnose because nobody knows what was altered.

Fully managed arrangements also exist precisely so nobody has to look at this, and for a business paying for that, poking around undermines what was bought.

There is a real difference between knowing where things are and administering a server, and this is only an argument for the first.

Look, learn the six locations, and keep the phone number of whoever should make changes.

The twenty minutes

1. Confirm you hold the login, in your own name.
2. Open the file manager and find the site folder.
3. Look at the databases list.
4. Check email accounts and their storage usage.
5. See what backups exist and how far back.
6. Find the error log and the certificate status.
7. Change nothing, and note where each was.

Step four is the one that prevents a real and common failure, and it takes about thirty seconds once you know where to look.

What a hosting plan includes is covered in what hosting actually buys you.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.