Release CryptBridge 0.8.2 · burnersen/CryptBridge

The Linux server setup no longer stops halfway when another web server is in the way, and it explains IP addresses right away.

Linux server setup

Another web server on port 80 or 443 is found first. A website running on the server (for example with nginx or Apache) used to stop the setup at the very end of the HTTPS step. The cryptbridge command and the desktop icons were then missing. Now the setup checks these ports right at the start, names the program and asks whether to stop it (default: no).
- Stop it: the setup goes on with HTTPS as usual.
- Keep it: everything else is set up (vault folder, cryptbridge command, desktop icons) and only HTTPS is skipped. Once the ports are free, run sudo cryptbridge setup.
IP addresses are explained. An IP address such as 157.173.96.238 gets no trusted certificate, so video players refuse the connection. The setup now says so at once and asks for a name again, for example a free one from DuckDNS. If you keep the IP anyway, the setup no longer waits 3 minutes for a certificate that never comes.
The HTTPS check says how long it may take ("up to 3 minutes"), so it does not look like a hang.

Server: download setup.sh again and run it. Answer y to Keep the cloud sign-in and vault keys from the last setup?:

curl -fsSLO https://raw.githubusercontent.com/burnersen/CryptBridge/main/linux/setup.sh && sudo bash setup.sh

Windows: nothing changes in the program itself (only its version number). Updating is optional.