Skip to content
Browse documentation

Getting started

App updates and corporate networks

Keep Vopit up to date and connect through a company network that inspects HTTPS traffic.

Settings → Updates and Settings → Network apply to this installation of Vopit, across all projects on this computer. Both are also available from the Settings button on the sign-in screen, before you sign in or open a project, together with Account.

Check for updates

  • Automatically check for updates is on by default. Your choice is saved immediately on this computer.
  • Windows x64 installations from vopit.fr and the Linux x64 package check about ten seconds after startup, then every six hours. When a check is due, it also runs when the computer wakes or the Vopit window gets focus.
  • Check now runs a check at any time. Settings show the installed version, the last result and any error, such as “Could not check for updates. Check your connection and try again.”
  • Checks are anonymous: they send no account information. On other platforms, Settings show that update checks are available for Windows and Linux (.deb) x64 installations.

Install a new version

  1. When a new stable version is available, a notice shows “Vopit X is available”.
  2. Choose Download update to download the official installer, or the Linux package, through your browser. Vopit keeps working until you close it.
  3. Run the installer when you are ready. On Linux, open the downloaded package with your software installer, or run sudo apt install ./Vopit-linux-x64.deb in its folder; running curl -fsSL https://vopit.fr/install.sh | sh again also updates Vopit.
  4. Choose Later to hide that version. A manual Check now offers it again.

Import a company CA certificate

Some company networks, for example with Zscaler, inspect HTTPS traffic and present their own certificate authority. Vopit then cannot verify connections until it trusts that authority. Ask your IT team for the public CA certificate.

  1. Open Settings → Network and choose Import certificate.
  2. Select the file: PEM (including bundles of up to 32 certificates), CRT or CER, in PEM or DER format, smaller than 1 MB.
  3. Check the Subject, Issued by, Valid until and SHA-256 fingerprint shown against what IT gave you.
  4. Close and reopen Vopit to apply the change. Current connections keep their previous trust settings until restart.
  • Private keys, client or server certificates (anything that is not a CA) and expired or not yet valid CAs are refused.
  • Importing, replacing (Replace certificate) and removing (Remove) are saved immediately for this computer. Vopit keeps a local copy, so the original file can be moved.
  • The certificate is not part of projects or team exports, and it does not change the Windows certificate store.
  • If sign-in is blocked by the network, open Settings → Network from the sign-in screen.

What the certificate covers

  • Vopit’s HTTPS connections: account access, update checks, HTTP model providers and Crank API actions. TLS and server name verification stay on. The usual authorities and CA bundles inherited from your environment are kept.
  • CLIs launched by Vopit receive the bundle through NODE_EXTRA_CA_CERTS, SSL_CERT_FILE, REQUESTS_CA_BUNDLE and CURL_CA_BUNDLE. Whether a CLI uses them depends on that CLI.
  • Your external browser and connections that define their own CA keep their own settings.
  • This setting does not configure a proxy.

All documentation