Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error sending request #189

Closed
Phantop opened this issue Oct 27, 2022 · 5 comments · Fixed by #190
Closed

Error sending request #189

Phantop opened this issue Oct 27, 2022 · 5 comments · Fixed by #190

Comments

@Phantop
Copy link

Phantop commented Oct 27, 2022

Trying to run the latest release on Linux (Solus) gives me this error:

Error: libsignal-service sending error: Error sending request: error trying to connect: invalid certificate: UnknownIssuer

Caused by:
    0: Error sending request: error trying to connect: invalid certificate: UnknownIssuer
    1: Error sending request: error trying to connect: invalid certificate: UnknownIssuer
@ephemer4l
Copy link
Contributor

Same here running on Gentoo.

@gferon
Copy link
Collaborator

gferon commented Oct 27, 2022

Sorry for that, the CA certificate we embed in libsignal-service-rs wasn't correct anymore and we fixed it this morning. I'll open a PR for gurk right away.

@gferon
Copy link
Collaborator

gferon commented Oct 27, 2022

@Phantop / @ephemer4l if you want to try the patch out before #190 is merged (and if you have Rust installed), you can run:

cargo install --git https://github.com/boxdot/gurk-rs --rev 77afa89e866f357178cf03b23b96d8ead1ed6f35 --locked --force gurk

@Tachi107
Copy link

Tachi107 commented Nov 1, 2022

Hi, could you please tag a new point release? This is a fairly severe issue, making gurk unusable; also, not everybody has rustc/cargo installed on their own system.

Thanks!

Edit: it'd be nice if the CI jobs would allow users to download build artefacts, so that they could easily try out the latest master

@boxdot
Copy link
Owner

boxdot commented Nov 1, 2022

Edit: it'd be nice if the CI jobs would allow users to download build artefacts, so that they could easily try out the latest master

I guess it is a good idea to add a nightly job which also produces a dist release (see #195)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants