Enable SSL/HTTPS
Serve your Victus-hosted app over HTTPS: the quick Cloudflare route, or a free Let's Encrypt certificate issued with Certbot for an Nginx site.
HTTPS encrypts traffic between your visitors and your app and is expected by browsers, logins and payment flows. There are two common ways to get it on a Victus-hosted app: let Cloudflare terminate SSL in front of your server (fastest), or issue a free Let's Encrypt certificate on the server itself with Certbot. Both require your domain to already point at the server — see "Point a custom domain/subdomain".
Option A — Cloudflare (no server config)
- 1Add your domain to Cloudflare and update your nameservers to Cloudflare's.
- 2Create the A/CNAME record for your app and keep the proxy ON (orange cloud).
- 3In SSL/TLS settings choose Full (or Full (strict) if you also have a valid cert on the origin).
- 4Enable Always Use HTTPS so visitors are redirected from http to https automatically.
Why Cloudflare is easiest here
Cloudflare issues and renews the public certificate for you and can front a non-standard app port, so visitors get https on 443 with zero certificate work on your server.
Option B — Let's Encrypt with Certbot (Nginx)
If you have shell/terminal access to the server (for example an Nginx App Hosting server or a Victus VPS running your reverse proxy) and your domain resolves to it on ports 80/443, Certbot can obtain and auto-renew a free certificate.
Ports 80 and 443 must reach the server
Let's Encrypt validates over HTTP on port 80 and serves HTTPS on 443. If your app only listens on a custom port, you need Nginx bound to 80/443 in front of it for Certbot to work.
Force HTTPS and verify
- Redirect all http traffic to https (Certbot can add this automatically; Cloudflare has "Always Use HTTPS").
- Load https://app.yourdomain.com and check for the padlock and a valid certificate.
- If you use both Cloudflare proxy and an origin cert, set Cloudflare SSL mode to Full (strict) to encrypt the whole path.
Certificate errors after setup?
A mismatch name means the cert was issued for a different hostname; a "not secure" warning behind Cloudflare usually means the SSL mode is set to Off/Flexible while the origin expects HTTPS. Confirm DNS resolves to the correct IP and that the SSL mode matches your origin setup.