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

Connection to SpiceDB not possible #6

Closed
tafli opened this issue Dec 19, 2024 · 2 comments
Closed

Connection to SpiceDB not possible #6

tafli opened this issue Dec 19, 2024 · 2 comments

Comments

@tafli
Copy link
Contributor

tafli commented Dec 19, 2024

When running thumper (locally and/or docker) I am not able to connect to my SpiceDB instance. SpiceDB is running in a OpenShift cluster with self-signed certs for testing purposes.

However, connecting with zed works when adding the option --no-verify-ca as expeced. The same option seems not to have an effect in thumper.

Thumper-Output:

{"severity":"info","name":"write basic RBAC schema","time":"2024-12-19T10:59:56+01:00","message":"loaded script"}
{"severity":"info","script":"write basic RBAC schema","time":"2024-12-19T10:59:56+01:00","message":"running migration script"}
{"severity":"debug","step":0,"total":2,"time":"2024-12-19T10:59:56+01:00","message":"executing migration step"}
Error: error running migration scripts: error running script write basic RBAC schema: rpc error: code = Unavailable desc = last connection error: connection error: desc = "error reading server preface: EOF"

The error is the same, despite adding --no-verify-ca or not.

When running zed without this option, the output is:

11:06AM ERR terminated with errors error="rpc error: code = Unavailable desc = connection error: desc = \"transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate signed by unknown authority\""

Any hints on this how I could solve / debug this problem?

@ecordell
Copy link

ecordell commented Jan 9, 2025

Can you try with --insecure=false? The flag defaults to true, which can be confusing.

@tafli
Copy link
Contributor Author

tafli commented Jan 15, 2025

Thanks for your hint. Yes, this is definitely confusing. However, this has done the trick.

I've created a small PR #8 to change this default flag.

@tafli tafli closed this as completed Jan 15, 2025
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

No branches or pull requests

2 participants