Skip to content
← Docs

Enable HTTPS on your VPS

There are three ways to get the padlock, from easiest to most hands-on. For most people, option 1 or 2 is all you need — and you don't have to touch certificates at all.

First, the thing that confuses everyone: on our standard plans your VPS shares a public IP with other servers, so hitting https://YOUR_IP directly gives a TLS error. That's expected — it's not your server being broken. HTTPS works through a name (a URL or a domain), not the raw shared IP. Here's how.

Option 1 — Use your free public URL (easiest)

Every VPS ships with a free HTTPS URL like k7m4x.aiccloud.online, with the certificate handled for you. Just make sure your app is serving on port 80 inside the VPS — the URL is on your VPS overview. Nothing to configure.

Full details: Free public URL.

Option 2 — Point your own domain (recommended for production)

Use your own domain and get automatic TLS — no certificate files, no renewals to remember:

  1. In the dashboard, open your VPS and add your domain under Domains / custom domain.
  2. At your DNS provider, add a CNAME for your domain pointing to the target we show you (or an A record to your VPS IP if you're using a dedicated IP — see option 3).
  3. Wait for DNS to propagate (usually minutes). We issue and renew a Let's Encrypt certificate automatically.

Your app just needs to be serving on port 80 inside the VPS — we terminate HTTPS in front of it.

Option 3 — Dedicated IP (full control)

Want to run your own web server with your own certificates on port 443 directly — or need a fixed IP for other reasons? Add a dedicated IPv4 (a small monthly add-on) from your VPS page. It routes all ports — including 80 and 443 — straight to your VPS, bypassing the shared edge. Point an A record at it and run Nginx/Caddy/Apache with Let's Encrypt exactly as you would on any server.

Still seeing “Not secure”?

  • Are you visiting the URL/domain rather than the raw IP? HTTPS only works via the name.
  • Is your app serving on port 80 inside the VPS (options 1 & 2 expect that)?
  • Just added a domain? Give DNS a few minutes, then reload. Certificates issue automatically once DNS resolves.

Still stuck? Open a ticket with your domain and we'll get it live.

Chat with us

We reply within minutes