How do I connect to my Adminor web hosting over SSH?

Create a shell account under Shell Users in the control panel (or ask support), then connect with ssh yourusername@your-server-address on port 22. You'll find the server address in the control panel or your welcome email; it differs between hosting servers, so always use your own.

Which server address should I use for SSH?

Use the address for your specific server, shown in the control panel under your hosting account or shell user, or in your welcome email. The address differs between servers, so always use your own. If unsure, support will help you.

Can I use WP-CLI, Composer and git on the hosting?

Yes. WP-CLI (wp), Composer and git are pre-installed in the shell environment. Run wp, composer or git from your web directory (usually web/). Check whether a tool exists with which, for example which wp.

Do I have root access on the web hosting?

No. The shell environment is an isolated chroot jail with no root or sudo, and you cannot install system packages or run your own daemons. The most common developer tools are pre-installed, though. If you need full root access, a VPS is the right product.

SSH access to your web hosting — how to connect

SSH gives you a command-line shell to your web hosting, so you can manage your files, your WordPress installation and your projects directly on the server — without going through FTP or the control panel. This guide walks through how to connect and which tools are available.

Enable SSH

SSH access works through a shell account tied to your web hosting. If you don’t have a shell account yet, create one under Shell Users in the control panel or contact support. You choose your own username and password (and can add an SSH key).

Find your server address

Your hosting lives on one of Adminor’s web hosting servers, and the server address differs between servers. Always use the address for your specific server — you’ll find it in one of these ways:

In the control panel, under your hosting account or shell user (the server or hostname field).
In the welcome email you received when the account was created.
Unsure? Contact support and we’ll give you the right address.

The examples below use the placeholder your-server.xh.se — replace it with your actual server address. (You can also connect using your own domain if it points to the hosting, but the server’s hostname is always the safe choice.)

Connect

Setting	Value
Server	your server address, e.g. `your-server.xh.se`
Port	`22`
Username	your shell username
Authentication	password or SSH key

From Linux/macOS or Windows (PowerShell/Terminal):

ssh [email protected]

With an SSH key (recommended):

ssh -i ~/.ssh/your_key [email protected]

The same credentials work for SFTP and scp if you just want to move files:

sftp [email protected]
scp localfile.zip [email protected]:web/

Your environment

Once logged in you land in your own home directory in an isolated environment (chroot jail). This means:

You only see your own files, not other customers’ or the system’s.
Your web files live in the web/ folder (that’s your public web root).
You also have private/ (for files outside the web, e.g. configuration) and tmp/.
You are not root and cannot install system packages, but the most common developer tools are already available (see below).

cd web        # go to your web root
ls -la        # list files

The exact directory structure may vary slightly between hosting servers. If you’re unsure where your web root is, run pwd right after login and ls to see your folders — or ask support.

Available tools

The following tools are normally pre-installed in your environment. The selection may differ slightly between servers — run which <tool> to check whether a tool exists, for example which git.

Editors: nano, vim, joe
Version control: git, tig
PHP / WordPress: wp (WP-CLI), composer, php
Files and transfer: rsync, curl, wget, zip, unzip, scp, sftp
Terminal: tmux (multiple sessions / keep a session on disconnect)

Common tasks

WordPress with WP-CLI

WP-CLI runs from your WordPress directory (usually web/):

cd web
wp core version
wp plugin list
wp plugin update --all
wp search-replace 'http://old.com' 'https://new.com' --dry-run
wp db export backup.sql

Database connection: WP-CLI reads your database credentials from wp-config.php. Our WordPress installations use DB_HOST = '127.0.0.1', which works directly. If your wp-config.php instead has DB_HOST = 'localhost' and WP-CLI can’t reach the database, change the line to 127.0.0.1 and it will work.

Composer

cd web
composer install
composer require monolog/monolog
composer update

Composer fetches packages from packagist.org and works directly in your environment.

Git deploy

cd web
git clone https://github.com/youraccount/yourproject.git .
git pull            # fetch the latest changes

Archive / extract and sync

unzip archive.zip
zip -r backup.zip web/
rsync -av web/ private/backup-web/

tmux (keep a session)

tmux              # start a session
# (detach with Ctrl-b then d)
tmux attach       # reconnect later

Limitations

The environment is deliberately restricted for security reasons:

No root/sudo and no system package installations.
No custom services/daemons or processes listening on ports. Don’t use the shell to run long-lived servers.
Scheduled jobs (cron) are managed in the control panel, not via the shell.
tmux works for normal use; advanced interactive features may be limited in the jail environment.
You can only access your own files and your own database.

If you need full control — root access, custom services, arbitrary system packages — a VPS is the right product instead of shared hosting.

Support

Something not working as expected, or missing a tool? Contact support and we’ll help you.