Point your nameservers

After purchasing, your domain needs to point to Karajohn's nameservers before it can go live. This usually takes 1–24 hours.

Set both nameservers at the same time. The order doesn't matter.
Your nameservers
ns1.karajohnhosting.com ns2.karajohnhosting.com

Step-by-step by registrar

1
Sign in to Namecheap
Go to namecheap.com and click Sign In.
2
Open Domain List
Click Domain List in the left sidebar, then click Manage next to your domain.
3
Switch to Custom DNS
In the Nameservers section, select Custom DNS from the dropdown.
4
Enter nameservers
Add ns1.karajohnhosting.com and ns2.karajohnhosting.com. Click the green checkmark to save.
1
Sign in to GoDaddy
Go to godaddy.com and sign in to your account.
2
Go to My Domains
Click your name top-right → My Products → find your domain → click DNS.
3
Change nameservers
Scroll to the Nameservers section → click Change → select Enter my own nameservers.
4
Enter nameservers
Type ns1.karajohnhosting.com and ns2.karajohnhosting.com → click Save.
1
Sign in to name.com
Go to name.com and sign in to your account.
2
Open My Domains
Click My Domains, then click the name of your domain.
3
Manage nameservers
Open Manage Nameservers and remove the existing nameservers.
4
Enter nameservers
Add ns1.karajohnhosting.com and ns2.karajohnhosting.com → Save Changes.
Domains you register through the Karajohn dashboard are already set to our nameservers — nothing to do.
1
Sign in to Papaki
Go to papaki.com and sign in (Σύνδεση).
2
Open your domains
Go to My account → Domains (Ο λογαριασμός μου → Domains) and click your domain.
3
Change nameservers
Open the Nameservers section and choose to use your own nameservers instead of Papaki's.
4
Enter nameservers
Replace the existing entries with ns1.karajohnhosting.com and ns2.karajohnhosting.com → save.
For .gr domains the registry may check that our nameservers already answer for your domain — so order your hosting first, then change the nameservers. Updates for .gr can take a few hours.
1
Domain registered at Cloudflare?
Domains bought from Cloudflare Registrar must use Cloudflare's own nameservers — they cannot be pointed elsewhere.
2
Option A: transfer the domain
Transfer the domain to another registrar (for example name.com or Papaki.gr), then set our nameservers there. In Cloudflare: domain → Configuration → unlock it and get the transfer (auth) code.
3
Option B: registered elsewhere, DNS at Cloudflare
If only the DNS is at Cloudflare, change the nameservers at your registrar (where you pay for the domain) to ours, then you can remove the site from Cloudflare.
Do not keep the domain on Cloudflare DNS with a proxy (orange cloud) in front of Karajohn — we manage the DNS, email records and SSL for you.
1
Sign in to Squarespace Domains
Google Domains moved to Squarespace in 2023. Go to domains.squarespace.com and sign in with the same Google account.
2
Open your domain
Click your domain → DNS → Domain Nameservers.
3
Use custom nameservers
Click Use Custom Nameservers.
4
Enter nameservers
Add ns1.karajohnhosting.com and ns2.karajohnhosting.com → Save.

What happens next

1
Propagation (1–24 hours)
DNS changes spread across the internet. Most update within 1–2 hours.
2
Automatic provisioning
We detect the change automatically and finish setting up your hosting — no action needed from you.
3
Your site goes live
You'll see the domain status change to Active in your dashboard. Your SSL certificate is issued automatically.

Connect email to your device

Add your custom email (e.g. you@yourdomain.com) to your phone, tablet, or desktop mail client.

Server settings

SettingValue
Mail servermail.karajohnhosting.com
IMAP port (incoming)993 with SSL
SMTP port (outgoing)587 with STARTTLS
UsernameYour full email address
PasswordThe password you set in the dashboard

iPhone / iPad

1
Open Settings
Go to Settings → Mail → Accounts → Add Account.
2
Choose Other
Scroll down and tap Other → Add Mail Account.
3
Enter your details
Name, email address, password, and a description. Tap Next.
4
Configure IMAP
Select IMAP. Under Incoming Mail Server enter host mail.karajohnhosting.com, port 993, SSL on. Under Outgoing Mail Server enter the same host, port 587, SSL on.
5
Save
Tap Save. Your email will start syncing within a few seconds.

Android (Gmail app)

1
Open Gmail settings
Open the Gmail app → tap your avatar → Add another account → Other.
2
Enter email and password
Type your full email address and tap Next.
3
Choose IMAP
Select IMAP when asked what type of account.
4
Incoming settings
Server: mail.karajohnhosting.com, Port: 993, Security: SSL/TLS.
5
Outgoing settings
SMTP server: mail.karajohnhosting.com, Port: 587, Security: STARTTLS.

Outlook (Windows/Mac)

1
Add account
Open Outlook → File → Add Account. Enter your email and click Advanced options → Let me set up my account manually.
2
Choose IMAP
Select IMAP from the account type list.
3
Enter server details
Incoming: mail.karajohnhosting.com port 993 SSL. Outgoing: mail.karajohnhosting.com port 587 STARTTLS.
You can also access your email from any browser at mail.karajohnhosting.com/mail using Roundcube webmail.

Manage email accounts

Create mailboxes for your domain from the dashboard and access them via Roundcube or any mail client.

Create a mailbox

1
Open your domain
Go to your dashboard and click on the domain you want to add an email address to.
2
Click Email
Click the Email button in the domain header.
3
Add a mailbox
Enter the local part (the part before @) and a strong password. Click Create.
The full email address will be localpart@yourdomain.com. Use your chosen password to connect via IMAP or log in to webmail.

Access webmail

Visit mail.karajohnhosting.com/mail and sign in with your full email address and password. Roundcube lets you read, compose, and organise your email from any browser.

Mailbox size

Each mailbox can hold up to the size of your plan. The Email page shows how much each mailbox uses.

PlanPer mailbox
Basic1 GB
Starter2 GB
Standard5 GB
Business10 GB
Pro10 GB

When a mailbox is full, new mail to it is refused with "mailbox full" until you delete old messages. We email the mailbox when it reaches 85%, 90%, 95% and 100%.

Sending limits

To keep our servers off spam blocklists, which protects every customer's email, each mailbox can send:

  • up to 100 messages per hour, with at most 50 recipients per message
  • up to 500 messages per day
For newsletters and marketing campaigns, use an email marketing service (for example Brevo, Mailchimp or MailerLite) with your own domain. Their sending infrastructure is built for that.

Spam and virus filtering

All incoming mail is checked for viruses and spam. Likely spam is delivered to the Junk folder; messages with a virus, and messages that are clearly spam, are held back and never reach the mailbox.

"Sending paused" or "Held at current size"

If a mailbox goes over the sending limits or sends messages our filters classify as spam, we pause its sending. It still receives mail and you can still read it. This usually means its password leaked or a website form is being abused, so:

1
Change the mailbox password
On the Email page, click the key icon next to the mailbox. Update the password in your mail apps too.
2
Check your website forms
If your site has a contact form, make sure it has spam protection (for example a captcha).
3
Contact support
Email support@karajohnhosting.com and we'll turn sending back on.

If a mailbox grows abnormally fast (more than 500 MB, or half its size, in 24 hours), it is held at its current size, so new mail is refused until it is checked. Delete the unwanted mail and contact support. If the growth was expected, tell us and we'll release it right away.

Delete a mailbox

In the Email section, click the trash icon next to the mailbox. This permanently deletes the mailbox and all its messages. There is no undo.

Access your database

Each domain has its own MariaDB database. You can manage it visually using phpMyAdmin — no SQL knowledge required for basic tasks.

Open phpMyAdmin

1
Open your domain
Go to your dashboard and click on your domain.
2
Find the Database card
On the Overview tab, scroll to the Database card.
3
Click phpMyAdmin
Click the phpMyAdmin link in the top-right corner of the Database card. You'll be taken directly to phpMyAdmin, already logged in.
The auto-login link expires after 5 minutes. If it doesn't work, go back to your dashboard and click Database again.

Your database details

Your database credentials are shown in your domain settings. You'll need them if you're configuring an application manually (e.g. a custom PHP app).

DetailWhere to find it
Database nameDomain settings in the dashboard
UsernameDomain settings in the dashboard
PasswordDomain settings in the dashboard
Host127.0.0.1
Port3306

WordPress quick start

Install WordPress in one click, then get to know your admin panel and the basics of building your site.

Install WordPress

1
Open your domain
Go to your dashboard and click on your domain.
2
Click Install → WordPress
Click the Install button and select WordPress. Confirm the installation — any existing files will be replaced.
3
Save your credentials
After installation, your admin username and password are shown. Save them — they won't be displayed again.
Installing WordPress replaces any existing site on this domain. All files and database content will be cleared first.

Log in to WordPress admin

Go to https://yourdomain.com/wp-admin and enter the admin credentials shown after installation.

Reset your admin password

1
Open your domain in the dashboard
Find the WordPress admin section on the domain detail page.
2
Click Reset admin password
A 6-digit verification code will be sent to your account email.
3
Enter the code
Enter the code in the dashboard. A new secure password is generated and shown immediately.

Recommended first steps

Change your site title
Settings → General → Site Title
Choose a theme
Appearance → Themes → Add New. Search for a free theme or upload a premium one.
Install essential plugins
Plugins → Add New. Recommended: Yoast SEO, WPForms, WP Super Cache.
Create your first page
Pages → Add New. Build your homepage, about page, and contact page.

Which PHP version should I use?

Every website chooses its own PHP version, and you can change it at any time. For most sites the answer is simple: use PHP 8.3. This page explains the differences and how to switch safely.

The versions we offer

VersionSecurity fixes untilCompatibilityGood for
PHP 8.231 Dec 2026Works with almost everythingOnly older sites that have problems on 8.3
PHP 8.331 Dec 2027The version most WordPress plugins are tested onMost sites — our default
PHP 8.431 Dec 2028WordPress works; some older plugins show warningsModern, well-maintained sites
PHP 8.531 Dec 2029Newest — some plugins may not be ready yetDevelopers who want the newest features
Not sure? Stay on PHP 8.3. It is fast, secure until the end of 2027, and works with practically every theme and plugin.
PHP 8.2 ends on 31 December 2026. After that date it no longer receives security fixes, and we remove it from the control panel in January 2027. If your site is on 8.2, move it to 8.3 before then — we will email you beforehand.

How to switch

1
Make a backup
Open your domain → Backups → Back up now. Switching PHP does not change your files or database, but it is good practice before any change.
2
Choose the version
Open your domain → Overview → PHP version and click the version you want. It takes a few seconds; your other sites are not affected.
3
Check your site
Open your website and, for WordPress, the admin area. If something looks wrong (a blank page or an error), switch back to the previous version — that is safe and immediate.

What changes between versions (for developers)

PHP 8.2
Read-only classes and a new random-number extension. Creating object properties on the fly is deprecated — the reason some older plugins show warnings on 8.2 and newer.
PHP 8.3
Typed class constants, json_validate() and the #[\Override] attribute.
PHP 8.4
Property hooks, separate read/write visibility for properties, array_find() / array_any() / array_all() and a modern HTML5 parser. A few more old code patterns now cause deprecation warnings.
PHP 8.5
The pipe operator |>, a built-in URL parser and array_first() / array_last(). OPcache is always built in.

Each version is also a little faster than the one before. For a typical WordPress site the difference is small — the theme and plugins matter much more.

PHP limits on every plan

SettingValue
Maximum upload size64 MB per file
Maximum form / request size72 MB
Memory per request256 MB (your plan's total RAM still applies)
Maximum script run time60 seconds
Maximum form fields3000
For security, website PHP cannot run shell commands (exec, system and similar). Scheduled tasks run PHP files or URLs instead — see the cron rules in your dashboard.

Git push-to-deploy

Edit files locally, push from your terminal, and your site updates instantly. No FTP, no manual uploads.

Enable Git deploy

1
Open your domain
Go to your dashboard and click on your domain.
2
Click Enable Git deploy
Find the Git push-to-deploy card and click Enable. A Git repository is created and your existing site files are imported into it automatically.
3
Save your credentials
Copy the Remote URL, username, and password shown in the card. The password is only shown once — save it now.

Clone your site to your computer

Run this once to download your site’s files to your machine. Your existing files are already in the repository.

git clone https://cp.karajohnhosting.com/git/yourdomain.com.git
# Enter your username and password when prompted
cd yourdomain.com
Git will remember your credentials after the first clone if you have a credential helper set up (macOS Keychain, Windows Credential Manager, or git config --global credential.helper store on Linux).

Make changes and deploy

Edit files locally, then push — your site updates immediately after each push.

# Edit your files, then:
git add .
git commit -m "describe your change"
git push origin main
Every push to main deploys automatically. Files are live within a few seconds of the push completing.

Connecting an existing local project

If you already have a local git repository you want to connect instead of cloning:

git remote add origin https://cp.karajohnhosting.com/git/yourdomain.com.git
git push --force origin main
Using --force replaces everything in the remote repo with your local files. Only do this if you want your local project to become the source of truth for the site.

What gets deployed

Everything in the repository root is deployed to your site’s public_html/ folder. Put your index.html, CSS, JS, images, and PHP files at the top level of your repo.

Git deploy works best for static sites and custom code. For WordPress sites, use the dashboard file manager or WordPress admin panel instead — WordPress stores uploads and settings in the database which git doesn’t manage.

How backups work

Backups run automatically on a schedule that depends on your plan. Every backup captures both your files and your database. You can restore from any backup in one click using the calendar view in your dashboard.

Backup schedule by plan

PlanAutomatic scheduleWhat's backed upHow far back
Basic / StarterEvery Sunday at 2 AMFiles + database4 weeks
Standard / BusinessEvery day at 2 AMFiles + database30 days daily, then weekly up to 3 months
ProEvery day at 2 AM + DB-only at midnight, 6 AM, noon & 6 PMFull backup daily · database-only every 6 hoursSame as Standard for full backups · last 7 days for DB snapshots
All backup times are UTC. Times shown in the dashboard are converted to your local timezone.

Retention — how many backups are kept

Basic / Starter — weekly
One backup per week is kept for 4 weeks, plus one per month for the past 2 months. After that, older backups are automatically removed. Maximum ~6 snapshots on disk at any time.
Standard / Business — daily
One backup per day for 30 days. Beyond 30 days, one per week for up to 8 weeks, then one per month for up to 3 months. You can go back up to ~3 months. Maximum ~37 snapshots.
Pro — daily files + 6-hour DB snapshots
Same full-backup retention as Standard/Business. In addition, database-only snapshots run every 6 hours — the last 28 are kept (7 days of coverage). These appear as a separate section in the calendar view so you can restore just the database to any 6-hour checkpoint within the past week.

The backup calendar

Open your domain and click the Backups tab. You'll see a monthly calendar. Each day that has a backup shows a coloured dot:

Full backup (files + database)
DB-only snapshot (Pro)

Click any day with a dot to expand a panel below the calendar showing the exact backup time and restore buttons. Use the arrow buttons to navigate to previous months.

Manual backups

Click Back up now at any time to create an on-demand backup. Manual backups capture files and database just like automatic ones.

Manual backups are not pruned immediately — they're kept alongside your scheduled backups until the next automatic run, which then applies your plan's retention policy.

Restore from a backup

1
Open your domain → Backups tab
Go to your dashboard, open the domain, and click the Backups tab in the domain navigation.
2
Find the date on the calendar
Click on any day that has a coloured dot. A panel appears below the calendar showing the backups for that day.
3
Choose what to restore
Click Files to restore website files only, or DB to restore the database only. You can restore either independently.
4
Confirm
Read the warning — it shows exactly what will be replaced and the date/time of the snapshot. Click Yes, restore to proceed.
Restoring a backup overwrites your current files or database with the snapshot version. Any changes made after that snapshot will be lost. There is no undo — if unsure, create a manual backup first.

Upgrade or downgrade your plan

Change your plan at any time from your domain detail page. Billing is prorated automatically.

How to change your plan

1
Open your domain
Go to your dashboard and click on the domain you want to change.
2
Click the Plan tab
Click Plan in the domain navigation. All available plans are listed with your current one highlighted.
3
Click Upgrade or Downgrade
Confirm your choice in the popup. Upgrades redirect to Stripe for immediate payment of the prorated difference. Downgrades take effect immediately with a credit on your next invoice.

How proration works

Upgrading
You pay only for the remaining days of the current billing period at the higher rate. Payment is collected immediately via Stripe.
Downgrading
The credit for unused time on the higher plan is applied to your next invoice automatically.

Sites in a bundle

If you bought several sites together (3 or more sites get 15% off, 5 or more 20%, 10 or more 25%), they share one subscription. Changing one site's plan changes only that site's part of the subscription: you keep the bundle discount, and the difference is prorated as above. Deleting one site takes it off the bundle; its unused time is credited to your next invoice.

Pro plan

The Pro plan is set up together with you. Use Request on the Plan page (or on our website), tell us about your site, and we'll email you the details.

Node.js apps

Run an Express, Next.js, Nuxt, NestJS or any other Node.js app on your domain. It runs on its own with your plan's memory and CPU, and restarts automatically if it stops.

Set it up

1
Install Node.js
Open your domain → Overview → 1-click installs → Node.js, and pick a version. This replaces the files in public_html with a small starter app.
2
Upload your app
Put your app in public_html with its package.json, using Files, SFTP or Git push-to-deploy. Don't upload node_modules.
3
Install packages
On the App tab, click npm install. For apps that need a build step (Next.js, Nuxt, TypeScript), run npm run build too.
4
Restart
Click Restart. The status shows Running when your app is up.

Your app must listen on PORT and HOST

The server tells your app where to listen through two environment variables. Use them instead of a fixed port:

app.listen(process.env.PORT, process.env.HOST)

Next.js: set the start script to next start -p $PORT -H $HOST in package.json. NODE_ENV is set to production.

Versions

VersionStatus
Node.js 22LTS, security fixes until April 2027
Node.js 24LTS, security fixes until April 2028, recommended
Node.js 26Current, the newest features (becomes LTS in late October 2026)

Switch versions on the App tab at any time. Security updates within a version are installed automatically every week.

Start command

By default the app starts with npm start (the "start" script in package.json). You can instead give a file, for example server.js or dist/index.js.

Adding packages

On the App tab, type a package name (for example express, express@4 or @scope/name) and click Add package. It is installed and saved to package.json. Remove takes it out again. Restart the app afterwards.

Logs

Everything your app prints (console.log, errors) appears under Logs → App output.

Keep secrets such as API keys out of your code: use environment variables.

Environment variables

Give your Node.js or Streamlit app settings and secrets (API keys, database URLs) without putting them in your code or in files.

Add a variable

1
Open the App tab
Open your domain → App.
2
Add variables
Under Environment variables, click Add variable, then enter a name (letters, digits and _, for example STRIPE_KEY) and its value.
3
Save
Click Save variables. Your app restarts with the new values.

Read them in your app

AppCode
Node.jsprocess.env.STRIPE_KEY
Streamlit (Python)os.environ["STRIPE_KEY"]
Values are stored encrypted and given only to your app; they are not in your website's files, so they can't leak through a download or a Git push. PORT, HOST, PATH and HOME are set by the server and can't be changed. Up to 100 variables per site.

Composer (PHP packages)

Laravel and other PHP projects install their libraries with Composer. You can run it from the App tab: no command line needed.

Install your project's packages

After you upload a project with a composer.json to public_html, open the App tab and click composer install. This creates the vendor folder. composer update updates the packages to the newest versions your composer.json allows.

Add or remove a package

Type the package as vendor/name, optionally with a version, for example guzzlehttp/guzzle or guzzlehttp/guzzle:^7.8, and click Add package. The packages in composer.json are listed with a remove button.

Composer runs as your site's user with your site's PHP version, so packages match what your site runs. Each run can take up to 15 minutes. WordPress plugins are installed from WordPress itself, not with Composer.

Staging site

A private copy of your website where you can try changes (a new theme, plugin updates, a redesign) without touching the live site. Included on Standard plans and above.

Create it

1
Open the Staging tab
Open your domain → Staging → Create staging environment.
2
Wait about 2 minutes
Your files and database are copied to staging.yourdomain.com, with its own SSL certificate.
3
Sign in
The staging site is password-protected (so search engines don't index it). The username and password are shown on the Staging tab.

Work on it

The staging files are in the staging folder (Files tab); the live site stays in public_html. WordPress addresses are changed to the staging address automatically.

Publish your changes

Push staging → production copies the staging files to the live site. Tick Also replace production database to copy the database as well (this overwrites all live data, such as new orders or comments, so use it with care). Website addresses are changed back to your domain automatically.

Sync production → staging does the opposite: it refreshes the staging copy with the current live site.

Take a backup before pushing a database to production. Pushing can't be undone.

DNS records explained

DNS records control where your domain points and what services are associated with it. Here's what each type does.

Common record types

TypeWhat it doesExample
APoints your domain to an IP address@ → 167.233.110.62
CNAMECreates an alias pointing to another domainwww → yourdomain.com
MXDirects email to your mail server@ → mail.karajohnhosting.com
TXTStores text data (SPF, DKIM, DMARC, verification)v=spf1 mx -all
Some records are locked and cannot be deleted — these are essential for your site and email to work correctly (A, MX, SPF, DKIM, DMARC).

TTL (Time To Live)

TTL controls how long DNS servers cache your records. A lower TTL (e.g. 300 seconds / 5 minutes) means changes spread faster but adds more DNS queries. The default of 3600 (1 hour) is fine for most records.

Email records

SPF
Tells receiving servers which IPs are allowed to send email for your domain. Prevents spoofing.
DKIM
A cryptographic signature added to every outgoing email. Proves the email wasn't modified in transit.
DMARC
Policy that tells receivers what to do with emails that fail SPF or DKIM checks. We set this to p=quarantine for you.

Troubleshooting

Solutions to the most common issues.

Site not loading after changing nameservers

Cause: DNS propagation takes time — usually 1–2 hours, sometimes up to 24 hours.

Check: Visit dnschecker.org and enter your domain to see if the nameservers have updated globally.

Fix: Wait. Once NS records propagate, your dashboard status will update to Active automatically.

SSL certificate error

Cause: SSL is issued after nameservers propagate. If you see a certificate warning, the domain likely hasn't fully propagated yet.

Fix: Wait for the domain to go Active in your dashboard. SSL is issued automatically — no action needed.

Email going to spam

Cause: New domains have no sending reputation. Email providers are cautious about new senders.

Fix: Ask your recipients to mark the email as Not Spam. After 2–4 weeks of consistent sending, your domain builds a reputation and inbox placement improves.

Can't log in to email on iPhone

Check these settings:

SettingCorrect value
Incoming hostmail.karajohnhosting.com
Incoming port993
Incoming SSLOn
Outgoing hostmail.karajohnhosting.com
Outgoing port587
Outgoing SSLOn (STARTTLS)
UsernameFull email address

Forgot WordPress admin password

Go to your dashboard → open your domain → find the WordPress Admin section → click Reset admin password. A verification code is sent to your email.

File manager shows permission denied

Each website runs as its own user, and its files belong to that user. You can read, edit, and upload files through the dashboard file manager, SFTP or Git. Direct SSH access is not available.

Node.js app shows an error page or "Not running"

Check: open Logs → App output. The most common causes are missing packages (click npm install on the App tab, then Restart), an app that doesn't listen on process.env.PORT and process.env.HOST, or a start command pointing to the wrong file.

My mailbox says "Sending paused"

See Email accounts → Sending paused.

Still stuck?

Click the chat button at the bottom right, or email us at support@karajohnhosting.com, and we'll help you out.