Security 9 min read ·
SSL Certificate for an IP Address: Free HTTPS Without a Domain
Get a free SSL certificate for an IP address from Let's Encrypt: HTTPS without a domain using Certbot, the 6-day lifetime, auto-renewal and nginx.
Yes, you can now get a free, publicly trusted SSL certificate for a bare IP address. Let's Encrypt made IP address certificates, for IPv4 and IPv6, generally available on 15 January 2026, but only as short-lived certificates that last 160 hours, just over six days. With Certbot 5.3 or newer you request one with --ip-address and --preferred-profile shortlived, and automatic renewal replaces it every few days.
That means HTTPS on a VPS before you buy a domain, or for an endpoint that never needed one. This guide covers who it suits, what the six-day lifetime changes, the Certbot commands for standalone and webroot mode, an nginx setup, renewal checks, and when a cheap domain is simply better. Commands are for Ubuntu 24.04 and Debian 13, as of 15 November 2026.
Can you get an SSL certificate for an IP address?
Yes, from Let's Encrypt and free of charge. Its announcement of 15 January 2026 says that "IP address certificates must be short-lived certificates", because IP addresses change hands more often than domain names. You select the shortlived profile, which Let's Encrypt's profiles page lists as the only one that accepts IP addresses.
Let's Encrypt has to reach the address to check you control it. Its challenge types page says HTTP-01 and TLS-ALPN-01 can validate IP addresses, but DNS-01 "cannot be used to validate IP Addresses", and HTTP-01 "can only be done on port 80". So the server needs a public IP with port 80 open: an address like 192.168.1.10 on your home network can't be validated.
| Let's Encrypt certificate | For a domain (default profile) | For an IP address |
|---|---|---|
| Lifetime | 90 days | 160 hours (about 6 days) |
| Validation | HTTP-01, DNS-01 or TLS-ALPN-01 | HTTP-01 or TLS-ALPN-01 only |
| Certbot renews it | With a third of its life left, about every 60 days | With half its life left, about every 3 days |
| Certbot sets up nginx for you | Yes, with --nginx | No, you edit nginx yourself |
The 90-day default is itself shrinking: Let's Encrypt moves to 64 days in February 2027, as our guide to SSL certificate validity in 2026 explains. Browsers trust the IP certificate like any other Let's Encrypt certificate; the address sits in the certificate's subject alternative name field.
Who needs HTTPS on a bare IP?
TradingView webhooks to your own bot. TradingView's webhook help page accepts only ports 80 and 443, doesn't support IPv6 and cancels requests that take longer than three seconds. It doesn't say a domain is required, but it does say "Always use secure, authenticated endpoints and encrypt sensitive data". Your alert message carries a secret, and on port 80 it travels unencrypted. An IP certificate on port 443 fixes that. TradingView doesn't document whether it accepts an IP-based https:// URL, so send a test alert and check the Webhook status column before you rely on it. Our TradingView webhook guide builds the receiver.
n8n before you buy a domain. n8n's security settings turn on N8N_SECURE_COOKIE by default, which "Ensures that cookies are only sent over HTTPS". Open n8n over plain HTTP and it shows the error "Your n8n server is configured to use a secure cookie, however, you are visiting this via an insecure URL". Switching the setting off sends your login cookie in the clear. An IP certificate lets you leave it on until you pick a domain. Our n8n guide covers the rest of a self-hosted setup. Services that call your n8n webhooks may have their own rules, so check each one.
APIs, dashboards and admin panels that only you or your own systems use. OpenAlgo is the exception: its official installer asks for a domain and fetches the certificate itself, so a domain is the supported route there (see our OpenAlgo setup guide). An IP certificate suits a quick test or a manual install.
What the six-day lifetime means for you
- Renewal every few days. Certbot's documentation says certificates that last 10 days or less are renewed with half their lifetime left, so roughly every 80 hours.
- Little slack. If renewal breaks, say a firewall change closes port 80 or nginx fails to start, the certificate expires within days and clients refuse to connect.
- No reminder emails. Let's Encrypt ended its expiry emails on 4 June 2025, so add your own check (shown below).
- A reload after each renewal. nginx keeps the old certificate in memory until it reloads, so the renewal needs a deploy hook.
How to install a Certbot version that supports IP certificates
According to Certbot's changelog, --ip-address arrived in version 5.3 (February 2026) for the standalone and manual plugins, and webroot support followed in 5.4 (March 2026). The distribution packages are older: Ubuntu 24.04 ships Certbot 2.9.0, and both Debian 13 and Ubuntu 26.04 ship 4.0.0. Use the snap instead, which Certbot's instructions recommend; its stable channel had version 5.10.0 on 15 November 2026.
sudo apt remove -y certbot # the old distro package, if installed
sudo apt install -y snapd # already present on Ubuntu Server
sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/local/bin/certbot
certbot --version # needs 5.4 or newer for webroot
If you can't use snaps, Certbot's pip instructions install it into /opt/certbot with a cron job for renewal. The Certbot team supports that method on a best-effort basis.
How to get a Let's Encrypt certificate for your IP with Certbot
Open ports 80 and 443. Let's Encrypt doesn't publish the addresses it validates from, so port 80 must be open to everyone, at every renewal. If you've added rules in your VPS dashboard's firewall, allow both ports there too.
curl -4 https://ifconfig.me; echo # your public IPv4 address
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
The examples use 203.0.113.10; replace it with your own address. Add --dry-run to any of these commands first to test against Let's Encrypt's staging server without saving anything.
Standalone: nothing is listening on port 80
Certbot runs its own temporary web server on port 80, so nginx or Apache must not be using it:
sudo certbot certonly --standalone \
--preferred-profile shortlived \
--ip-address 203.0.113.10
Webroot: nginx is already running
Webroot mode drops the challenge file into a folder your web server serves, so nothing goes offline. Save this as /etc/nginx/sites-available/ip-cert:
server {
listen 80;
server_name 203.0.113.10;
location ^~ /.well-known/acme-challenge/ {
root /var/www/letsencrypt;
}
location / {
return 301 https://$host$request_uri;
}
}
sudo mkdir -p /var/www/letsencrypt
sudo ln -s /etc/nginx/sites-available/ip-cert /etc/nginx/sites-enabled/
sudo nginx -t && sudo systemctl reload nginx
sudo certbot certonly --webroot --webroot-path /var/www/letsencrypt \
--preferred-profile shortlived \
--ip-address 203.0.113.10 \
--deploy-hook "systemctl reload nginx"
Certbot saves the certificate in /etc/letsencrypt/live/203.0.113.10/ as fullchain.pem and privkey.pem. It saves the profile and the deploy hook in the certificate's renewal settings too, so every renewal reloads nginx. To cover your IPv6 address as well, add a second --ip-address; TradingView doesn't use IPv6, so IPv4 alone is enough for webhooks.
How to use the certificate in nginx
Let's Encrypt's Certbot announcement says Certbot "only supports getting IP address certificates, not yet installing them", and its nginx and Apache plugins "don't yet support IP addresses". Certbot's changelog up to 5.10.0 doesn't change that, so add the HTTPS server to /etc/nginx/sites-available/ip-cert yourself:
server {
listen 443 ssl;
server_name 203.0.113.10;
ssl_certificate /etc/letsencrypt/live/203.0.113.10/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/203.0.113.10/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
location / {
proxy_pass http://127.0.0.1:5678; # your app: n8n, a bot or an API
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade; # WebSockets, which n8n's editor needs
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
sudo nginx -t && sudo systemctl reload nginx
curl -v https://203.0.113.10/ 2>&1 | grep -i "verify ok" # run this from your laptop
Keep the app itself listening on 127.0.0.1, so it can only be reached through nginx. The port-80 block redirects everything except the challenge folder to HTTPS. TradingView counts redirects as errors, so put the https:// address in your alert, not http://.
How to check that renewal works
The snap installs a systemd timer that runs certbot renew on its own. Confirm it, then test a full renewal against the staging server:
systemctl list-timers | grep certbot
sudo certbot renew --dry-run
sudo certbot certificates # expiry date and days left
Because nobody emails you about expiry any more, add a check of your own. This line fails when the certificate has less than 48 hours left; run it daily from cron or your monitoring and alert on failure:
sudo openssl x509 -checkend 172800 -noout -in /etc/letsencrypt/live/203.0.113.10/fullchain.pem
If you started with standalone mode and later put nginx on port 80, standalone renewals will fail because the port is busy. Switch the certificate to webroot with certbot reconfigure, which test-renews against staging before it saves anything:
sudo certbot reconfigure --cert-name 203.0.113.10 \
--webroot --webroot-path /var/www/letsencrypt \
--deploy-hook "systemctl reload nginx"
When is a cheap domain the better choice?
An IP certificate is a good fit for one webhook receiver, a private dashboard or a quick test. A domain is better when:
- It's a website for other people. Nobody remembers an IP address. Our web hosting issues and renews free SSL certificates automatically once your domain points to us, from ₹99 a month, or about ₹82.50 a month when billed yearly.
- You might move servers. A new server means a new IP, so every webhook URL, bookmark and integration changes. With a domain you change one A record (see DNS records explained).
- You want slack. A domain certificate lasts 90 days today, so a broken renewal leaves you weeks to notice instead of about three days.
- Your tools expect one. OpenAlgo's installer and Certbot's automatic nginx setup both work with domain names.
A new .in domain costs ₹983 for the first year and the same to renew, and a subdomain of a domain you already own costs nothing. You can search for a domain in a minute.
For the IP route, any HostEthical Cloud VPS has a dedicated IPv4 address that stays the same through reboots and reinstalls, from ₹860 a month, or about ₹774.17 a month when billed yearly; Mumbai adds a small monthly location fee. For trading bots, Algo VPS Mumbai costs ₹1,510 a month, or about ₹1,325 a month when billed yearly and adds the static IP setup brokers ask for. Both are unmanaged, so the Certbot and nginx steps above are yours to run.
Frequently asked questions
Can I get an SSL certificate for an IP address?
Yes. Since 15 January 2026, Let's Encrypt issues free, publicly trusted certificates for public IPv4 and IPv6 addresses. They must use the shortlived profile, so each certificate lasts 160 hours, just over six days, and has to be renewed automatically. Let's Encrypt checks control of the address over HTTP on port 80, so the server needs a public IP that it can reach.
Does Let's Encrypt support HTTPS without a domain?
Yes, through IP address certificates. You request one with Certbot 5.3 or newer, using the --ip-address flag together with --preferred-profile shortlived, in standalone mode or, from Certbot 5.4, webroot mode. Certbot only obtains the certificate: you point nginx or your app at the files in /etc/letsencrypt/live yourself and reload it after each renewal.
How long is a Let's Encrypt IP certificate valid?
About six days. Let's Encrypt only issues IP address certificates under its shortlived profile, which gives 160 hours of validity. Certbot renews certificates that short when half their lifetime is left, so roughly every three days. Port 80 must stay open for each renewal, and Let's Encrypt no longer sends expiry emails, so it is worth adding your own expiry check.
Why does Certbot say --ip-address is not recognised?
Your Certbot is too old. The flag arrived in Certbot 5.3 in February 2026, and webroot support needs 5.4. As of November 2026, Ubuntu 24.04 packages Certbot 2.9.0 and Debian 13 packages 4.0.0. Remove the distribution package and install Certbot from the snap, whose stable channel had version 5.10.0 in November 2026, or follow Certbot's pip instructions. Then run certbot --version to confirm which version you have.
Can TradingView send webhooks to an IP address with HTTPS?
TradingView's help pages say webhooks go only to ports 80 and 443, don't support IPv6 and must answer within three seconds. They don't say whether a domain name is required, so send a test alert to your https:// IP address and check the webhook status in the alert log. An IP certificate on port 443 keeps the secret in your alert message encrypted.