Closed cubar closed 3 years ago
The certificate errors you are seeing are not a problem. We use self-signed certificates for Signal servers, instead of the standard set of certificate trust providers that your web browser uses.
The error on startup is a known issue with v1.40.0-beta.6
. Please try v1.40.0-beta.7
.
@scottnonnenberg-signal : thanks for you answer. I did "git pull" in my local repository which I had cloned from github to be sure I had a fresh copy, followed by: git checkout tags/v1.40.0-beta.7 to checkout the version you mentioned. I am on Linux, but i have no experience with Electron which looks something like a node.js framework. What to do next to compile or start the application? Thanks again, Chuck
$ wget https://textsecure-service.whispersystems.org/v1/config --no-check-certificate --2021-02-13 15:24:38-- https://textsecure-service.whispersystems.org/v1/config Resolving textsecure-service.whispersystems.org (textsecure-service.whispersystems.org)... 13.248.212.111, 76.223.92.165 Connecting to textsecure-service.whispersystems.org (textsecure-service.whispersystems.org)|13.248.212.111|:443... connected. WARNING: cannot verify textsecure-service.whispersystems.org's certificate, issued by ‘CN=TextSecure,OU=Open Whisper Systems,O=Open Whisper Systems,L=San Francisco,ST=California,C=US’: Self-signed certificate encountered. HTTP request sent, awaiting response... 401 Unauthorized
Thanks, Chuck
After your last mail I also downloaded "https://gitlab.com/rahmiac/signal-desktop-appimages/-/blob/master/Signal-1.39.6.AppImage" from your repository, installed nodejs and nvm, restarted the terminal session, ran nvm install, nvm run and as shown above finally ./AppRun, resulting in the messages above.
Among these messages we get as mentioned before: {"name":"log","hostname":"de","pid":5511,"level":50,"time":"2021-02-13T20:25:30.908Z","msg":"GET https://textsecure-service.whispersystems.org/v1/config 401 Error","v":0}
In short, this result is very similar to what I got after installing with apt install from the official repository: First, the "config" page cannot be downloaded because of the certificate being self signed. Second, the signal-desktop window is completely empty
I think it would help if the domain *.whispersystems.org would use a genuine certificate (which already has been requested as I understand from @scottnonnenberg-signal). I would recommend Letsencrypt as it's free.
Regards, Chuck
Hello Rahmi, I am running on debian and also tried on ubuntu. I followed the instructions on the official site to install signal-desktop as well as a compiled version in a local git clone after checking out the version with tag v1.40.0-beta.7. All attempts resulted in the same result: running the app gives an empty app window and the config url unreachable because of the certificate problem.
It seems that the v1.40.0-beta.7 version has the same problem as the version on the official page: https://signal.org/download/linux/. We may have to wait for the certificate to be no longer self signed. Thanks so far, Chuck
Hello Rahmi,
Success using the --no-sandbox option with the beta version! It turns out that I ended up with two versions of signal-desktop: One in "/opt/Signal/" and another in "/opt/Signal Beta/".
I am not sure which beta version it is, couldn't quite find out using grep -ril on the folder. To start signal from the command line I use signal-desktop-beta --no-sandbox
Anyways, thank you very much for your help. Cheers, Chuck
In the future, when attempting to run the application in development mode, use the forums to work with the community to get things working. I'm going to close this.
I get this error: {"name":"log","hostname":"de","pid":13187,"level":50,"time":"2021-02-12T21:12:30.594Z","msg":"GET https://textsecure-service.whispersystems.org/v1/config 401 Error","v":0}
so I tried to get the page in Chromium and get "Your connection is not private":
Your connection is not private Attackers might be trying to steal your information from textsecure-service.whispersystems.org (for example, passwords, messages, or credit cards). Learn more NET::ERR_CERT_AUTHORITY_INVALID
Wget https://textsecure-service.whispersystems.org/v1/config gives:
--2021-02-12 21:22:20-- https://textsecure-service.whispersystems.org/v1/config Resolving textsecure-service.whispersystems.org (textsecure-service.whispersystems.org)... 13.248.212.111, 76.223.92.165 Connecting to textsecure-service.whispersystems.org (textsecure-service.whispersystems.org)|13.248.212.111|:443... connected. ERROR: cannot verify textsecure-service.whispersystems.org's certificate, issued by ‘CN=TextSecure,OU=Open Whisper Systems,O=Open Whisper Systems,L=San Francisco,ST=California,C=US’: Self-signed certificate encountered. To connect to textsecure-service.whispersystems.org insecurely, use `--no-check-certificate'.
Tried it on debian and on ubuntu with the same result. Seems to be some problem with the ssl certificate. What can I do about this?