HTTPS certificate

Installing the web interface TLS certificate via Nginx

bg-dots
bg-dots

On Vinteo Server 40.x there is no SSL tab in the web interface. The HTTPS certificate for the web server is configured with the files referenced by Nginx.

By default, /etc/nginx/conf.d/vinteo.conf contains:

ssl_certificate     "/etc/ssl/certs/vcs-web.crt";
ssl_certificate_key "/etc/ssl/private/vcs-web.key";

The same paths are used in /etc/nginx/conf.d/localhost.conf. If the paths were overridden, check the current ssl_certificate and ssl_certificate_key values in the Nginx configuration.

Attention!
Perform the replacement as root. Back up the current certificate and key files before changing them.

Preparing the files

Two PEM files are required:

  • vcs-web.crt — the server certificate and intermediate CAs in one file;
  • vcs-web.key — the server private key.

The root CA of public authorities (Let’s Encrypt, GlobalSign) is usually not included in vcs-web.crt: the server certificate plus intermediates is enough. For Ministry of Digital Development National CA (NUTs Mintsifry) certificates (DV/OV via Gosuslugi), the same file layout applies on the server; client browser trust may differ (Yandex Browser and similar vs Chrome / Firefox / Safari without the Ministry root installed).

Building vcs-web.crt from separate files

CAs often issue several PEM files. Combine them into one vcs-web.crt in this order:

  1. the server certificate (for your domain / FQDN);
  2. the intermediate CA (if there are several files — from the one closest to the server toward the higher CA);
  3. the root CA — only if support or the CA documentation explicitly requires it in the Nginx chain.

Example: you have server.crt, one intermediate intermediate.crt, and key server.key.

cat server.crt intermediate.crt > vcs-web.crt
cp server.key vcs-web.key

If there are two intermediates:

cat server.crt intermediate1.crt intermediate2.crt > vcs-web.crt

For Let’s Encrypt the ready chain is already in fullchain.pem — copy it to vcs-web.crt and use privkey.pem as the key:

cp fullchain.pem vcs-web.crt
cp privkey.pem vcs-web.key

Each PEM block must keep its -----BEGIN CERTIFICATE----- / -----END CERTIFICATE----- lines (for the key — the matching BEGIN / END key type). Order matters: the server certificate always comes first.

Check how many certificates are in the assembled file:

grep -c "BEGIN CERTIFICATE" vcs-web.crt

Replacing the certificate

Step 1. Save backups:

cp -a /etc/ssl/certs/vcs-web.crt /etc/ssl/certs/vcs-web.crt.bak
cp -a /etc/ssl/private/vcs-web.key /etc/ssl/private/vcs-web.key.bak

Step 2. Copy the assembled files to the paths used by Nginx:

cp ./vcs-web.crt /etc/ssl/certs/vcs-web.crt
cp ./vcs-web.key /etc/ssl/private/vcs-web.key
chmod 644 /etc/ssl/certs/vcs-web.crt
chmod 600 /etc/ssl/private/vcs-web.key
chown root:root /etc/ssl/certs/vcs-web.crt /etc/ssl/private/vcs-web.key

Step 3. Test the configuration and reload Nginx:

nginx -t
systemctl reload nginx

nginx -t must complete without errors. If it fails, restore the .bak copies, then run nginx -t and systemctl reload nginx again.

Step 4. Open the web interface over HTTPS and confirm that the browser accepts the certificate and sign-in works.

Rollback

cp -a /etc/ssl/certs/vcs-web.crt.bak /etc/ssl/certs/vcs-web.crt
cp -a /etc/ssl/private/vcs-web.key.bak /etc/ssl/private/vcs-web.key
nginx -t
systemctl reload nginx

If needed, agree certificate issuance and chain contents with technical support (support@vinteo.ru).

Installing on an open distribution Licensing