Deployment without domain

Announcements
1

OpenVidu v3 supports domain-free deployments using sslip.io. However, if you recently deployed without a domain and are experiencing a LetsEncrypt rate-limit, this is likely due to an ongoing rate-limiting problem with sslip.io (see cunnie/sslip.io#108).

Until this is resolved, we recommend using your own domain name instead.

3

When sslip.io (or any domain) fails to acquire a valid SSL certificate, your browser will display an ERR_SSL_PROTOCOL_ERROR when attempting to access the deployment URL.

image
image677×337 11.2 KB

To confirm this is the issue, check the Caddy logs on your Single Node or any Master Node. SSH into the node and run:

sudo su
docker logs caddy

You should see an error similar to this:

{"level":"error","ts":1770908645.276268,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"openvidu-cjuzkgrx-13-58-233-208.sslip.io","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 429 urn:ietf:params:acme:error:rateLimited - too many certificates (50000) already issued for \"sslip.io\" in the last 168h0m0s, retry after 2026-02-12 15:04:09 UTC: see https://letsencrypt.org/docs/rate-limits/#new-certificates-per-registered-domain"}
{"level":"error","ts":1770908645.276335,"logger":"tls.obtain","msg":"will retry","error":"[openvidu-cjuzkgrx-13-58-233-208.sslip.io] Obtain: [openvidu-cjuzkgrx-13-58-233-208.sslip.io] creating new order: attempt 1: https://acme-v02.api.letsencrypt.org/acme/new-order: HTTP 429 urn:ietf:params:acme:error:rateLimited - too many certificates (50000) already issued for \"sslip.io\" in the last 168h0m0s, retry after 2026-02-12 15:04:09 UTC: see https://letsencrypt.org/docs/rate-limits/#new-certificates-per-registered-domain (ca=https://acme-v02.api.letsencrypt.org/directory)","attempt":3,"retrying_in":120,"elapsed":187.594160281,"max_duration":2592000}

To resolve this, you can either wait for Caddy’s automatic retry to succeed, or restart your node.
The retry interval is a custom exponential backoff, you can check it here

If the issue persists, configure your deployment with a custom domain instead by modyfing the parameter DOMAIN_NAME of…

Single Node:

/opt/openvidu/config/openvidu.env

Elastic/HA:

/opt/openvidu/config/cluster/openvidu.env

… configure your DNS to point to your IP/Load Balancer and restart with …

systemctl restart openvidu