Skip to content

Cookie settings

Choose which kinds of cookies you allow. You can change your choice at any time via Cookie settings at the bottom of every page. Privacy statement

Necessary

Always on

Needed to log in, keep your cart and remember your choices. These are always on.

Which cookies?
  • weboke_sessie, weboke_klant, weboke_remember: your session and staying logged in
  • weboke_basket: your cart
  • wkBtwIncl: showing prices with or without VAT
  • wok_cookies: your cookie choice, 12 months

Measures which ad leads to a visit or order, so we do not pay for ads that do nothing.

Which cookies?
  • Google Ads via Google Tag Manager (_gcl_au, _gcl_aw), up to 90 days
  • OpenAI Ads, ads in ChatGPT
  • wok_aff: which partner referred you to us (affiliate programme), 60 days

4.6

Country and language

Each country has its own site, with prices and VAT for that country.

View

SSH access and the Terminal in DirectAdmin: which packages and how to log in

With SSH or the Terminal you work on the command line of your package, for example for Composer, WP-CLI or importing a large database. In this article you'll read which packages have SSH, how to open the Terminal and how to log in with your own SSH program.

Which packages have SSH?

The Terminal and SSH are included in Power Webhost Three and Four, AI Wordpress Three and Power Reseller. The other packages, such as Webhost One, Webhost Two, AI Wordpress One and Two, don't have SSH.

Want SSH added? Then switch to a package with SSH: in My WebOké go to My Products, click on your package and choose Change Package. If you don't see SSH Keys and Terminal in DirectAdmin, SSH isn't included in your package.

Opening the Terminal in your browser

With the Terminal in DirectAdmin you work on the command line directly in your browser. You don't need an SSH program or a key.

  1. Log in to DirectAdmin: in My WebOké go to My Products and click DirectAdmin next to your hosting package.
  2. Under System Info & Files, click Terminal.
  3. After a few seconds it will say Terminal (Active). You're logged in as your DA user, in your home directory.
  4. Done? Click Disconnect.
The Terminal in DirectAdmin with a command prompt
The Terminal in your browser

Logging in with your own SSH program

With WebOké you log in with an SSH key, not with a password. You'll need this:

  • Server: the server name of your package, for example servername.webawere.nl. See Finding your server name and DA username.
  • Port: 1967 (not the default port 22).
  • Username: your DA username.
  • Login: only with an SSH key.
  1. Create a key pair on your own computer, for example with ssh-keygen -t ed25519. The private key stays on your computer. Never share it.
  2. In DirectAdmin, under Advanced Features, click SSH Keys and then PASTE KEY.
  3. Paste your public key (the contents of the .pub file) as a single line into the Key field and click CREATE.
  4. Connect from your terminal (Mac, Linux or Windows Terminal):
ssh -p 1967 username@servername.webawere.nl

The first time, your computer will ask whether you trust the server: type yes. If you're using PuTTY or FileZilla (SFTP), also choose port 1967 and your private key.

The Paste Authorized Key window with a public key in the Key field and the Create button
Paste your public key into Key (1) and click Create (2)

Can't log in?

  • Getting Permission denied (publickey)? Check that you're using port 1967, that your public key is listed under Authorized Keys, and that your program is using the matching private key.
  • After a few failed attempts, your IP address may get blocked. You can check this in My WebOké under Am I blocked?. See Solving login problems.
  • Does DirectAdmin say your key is invalid? Paste the public key, not the private key, and make sure it's a single line.

Also see in the DirectAdmin manual: SSH Keys and logging in with SSH.

Detailed explanation with screenshots: Terminal in your browser in the DirectAdmin manual.

Was this article helpful?

← Back to DirectAdmin and WebOké control panel

One moment…

Set up your domains

For each domain, arrange the nameservers, the link to your hosting and who becomes the owner.

Loading your domains…