What you will set up
By the end, your offshore website will load over HTTPS with a working padlock — using a free SSL certificate from Let’s Encrypt.
An SSL certificate is what turns http:// into https:// and shows the little padlock in the browser. It encrypts the traffic between your visitor and your server, so passwords and form data can’t be read in transit. The good news: with Let’s Encrypt it is completely free, and you can renew it forever.
Do one step at a time. Finish a step, check it works, then move on.
Before you start
The goal: install a free SSL certificate on your offshore hosting so your site runs on secure HTTPS with the padlock.
Take a backup first. Before changing server settings, make a snapshot or backup you can roll back to. If a website is already live, back up its files and its database.
- Keep your domain login ready (in case you need to fix DNS).
- Keep your hosting or server panel login ready.
- Keep the server IP, username, and password (or SSH key) ready.
- Open a notes file and write down every change you make.
- Keep one terminal window open until testing is done, so you don’t lock yourself out.
One shortcut worth knowing: if your offshore plan uses a panel like cPanel or aaPanel, you can usually issue a free SSL with one click in the SSL section — no commands needed. The steps below cover the manual Nginx way, which works on any VPS.
Where does each change happen?
Each kind of change lives in a different place. Here is the simple rule:
- Domain records (DNS) → your domain or Cloudflare panel.
- The SSL certificate → on the server, over SSH (or one click in your panel).
- Website content → your CMS dashboard (for example wp-admin).
- Web server & HTTPS redirect → over SSH or your server control panel.

The steps
Run these only on your own server. If your server uses a managed panel, check with support before changing system-level settings.
Step 1: Make sure your domain points to this server
The certificate check (the “challenge”) only works if your domain already points to this server. So add or confirm the A record for your domain pointing to your server’s IP first.
dig +short yourdomain.com
Check: the IP shown matches your offshore server’s IP. If it doesn’t, fix the A record and wait for it to update before moving on.
Step 2: Install Certbot
Certbot is the free official tool that talks to Let’s Encrypt and sets everything up for you. This installs it with the Nginx plugin on an Ubuntu/Debian server.
apt install certbot python3-certbot-nginx -y
Check: running certbot --version prints a version number.
Step 3: Get and install the certificate
This one command requests the certificate, installs it, and sets up the HTTPS redirect so visitors are automatically sent to the secure version of your site. Use your real domain (list both the bare domain and the www version).
certbot --nginx -d yourdomain.com -d www.yourdomain.com
Check: Certbot says “Congratulations” and your site now opens on https:// with a padlock.
Step 4: Confirm auto-renewal works
Let’s Encrypt certificates last 90 days and renew automatically in the background. This command does a practice run so you know renewal will succeed when the time comes — it doesn’t change your live certificate.
certbot renew --dry-run
Check: the dry run finishes without errors. Your certificate will now keep itself renewed.
Extra commands you may need
Run these only on your own server. If your server uses a managed panel, check with support before changing system-level settings.
Confirm the site responds over HTTPS
curl -I https://yourdomain.com
This should return 200 over HTTPS. If it returns an error, the certificate or the web server config still needs a look.
List installed certificates and expiry
certbot certificates
This shows every certificate Certbot manages, the domains it covers, and the exact expiry date.
Keep short notes as you go
While you work, jot down each change: the old value, the new value, the time, and whether the test passed. For example: “Pointed A record to 2.2.2.2 at 10:30, ran Certbot, padlock works, dry-run renew passed.” It sounds small, but it saves a lot of confusion if something breaks.
If you run server commands, paste the output into your notes too. Then if you ask support for help, you can show the exact command, the exact error, and the exact time.
If a step fails, how to undo it
Always have a way back. For DNS, put the old record back. For SSL, you can remove the forced-HTTPS redirect until the certificate works, then re-add it. Don’t change ten things at once — fix and test one thing at a time.

How to test after setup
- Open your homepage in a private browser window — the URL should start with
https://. - Look for the padlock and make sure there is no browser warning.
- Type the
http://version of your site — it should redirect tohttps://on its own. - Open an inner page, a blog post, and a service page; check each one is secure.
- Run
curl -I https://yourdomain.comand confirm a 200 response. - Check that key pages return 200 and redirects are 301, with no redirect loops.
Quick troubleshooting
| Problem | Likely reason | What to do |
|---|---|---|
| Challenge failed | Domain not pointing to this server, or port 80 is blocked | Fix the A record so it points here, open port 80 in the firewall, then run Certbot again |
| Mixed-content warning | The page loads some files over http:// |
Force HTTPS and update any http:// links/images to https:// |
| “Not secure” still shows | Old cached version or redirect not applied | Clear the cache, reissue if needed, and make sure the HTTPS redirect is on |
Final checklist
- Domain points to this server.
- Certbot installed.
- Certificate issued and HTTPS redirect on.
- Padlock shows with no warnings.
- Auto-renewal dry run passed.
OffshoreKaka offers privacy-friendly offshore web hosting where you can issue free SSL in a few clicks and keep your site secure.
FAQ
Is the Let’s Encrypt certificate really free?
Yes. Let’s Encrypt is free and trusted by all major browsers. It lasts 90 days and renews automatically, so you never pay and you never have to remember to renew by hand.
Will adding SSL improve my Google ranking?
HTTPS helps — it’s a small ranking signal and it builds visitor trust. But it won’t put you at #1 on its own. Your content and backlinks still decide where you rank; SSL just gives you a solid, secure base.
What should I send to support if something breaks?
Send your domain name, server IP, the exact error message, a screenshot, the last change you made, and whether the trouble started after a DNS, SSL, or firewall change.