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

[Bug]: The client is unauthorized due to authentication failure #352

Open
thiagoscodelerae opened this issue Sep 23, 2024 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@thiagoscodelerae
Copy link

Contact Details

[email protected]

What happened?

I'm following this quickstart guide to deploy a Neo4j standalone instance to kubernetes cluster (AWS EKS), but when I try to connect to Neo4j instance I got the following error:

kubectl run --rm -it --namespace "neo4j" --image "neo4j:5.23" cypher-shell -- cypher-shell -a "neo4j://my-neo4j-release.neo4j.svc.cluster.local:7687" -u neo4j -p "v5g4h5gL56dsq"
If you don't see a command prompt, try pressing enter.
The client is unauthorized due to authentication failure.

Quickstart link: https://neo4j.com/docs/operations-manual/current/kubernetes/quickstart-standalone/

I already tried custom password in values or no custom password (auto generated by neo4j)

Chart Name

Neo4j Standalone (v4.4.x)

Chart Version

5.12.0

Environment

Amazon Web Services

Relevant log output

Chat version: neo4j-5.23


Changed password for user 'neo4j'. IMPORTANT: this change will only take effect if performed before the database is started for the first time.
2024-09-23 13:27:10.746+0000 INFO  Logging config in use: File '/config/user-logs.xml/user-logs.xml'
2024-09-23 13:27:10.840+0000 INFO  Command expansion is explicitly enabled for configuration
2024-09-23 13:27:10.949+0000 INFO  Starting...
2024-09-23 13:27:18.425+0000 INFO  This instance is ServerId{11b38503} (11b38503-747a-4747-b30f-2ddaad68cb45)
2024-09-23 13:27:26.330+0000 INFO  ======== Neo4j 5.23.0 ========
2024-09-23 13:27:38.546+0000 INFO  Anonymous Usage Data is being sent to Neo4j, see https://neo4j.com/docs/usage-data/
2024-09-23 13:27:38.741+0000 INFO  Bolt enabled on 0.0.0.0:7687.
2024-09-23 13:27:43.636+0000 INFO  HTTP enabled on 0.0.0.0:7474.
2024-09-23 13:27:43.638+0000 INFO  Remote interface available at http://localhost:7474/
2024-09-23 13:27:43.645+0000 INFO  id: 5BFCD27230B47E24D034475D96DAC0628801E1D5D957661CBA95E20792190868
2024-09-23 13:27:43.646+0000 INFO  name: system
2024-09-23 13:27:43.646+0000 INFO  creationDate: 2024-09-19T19:25:04.922Z
2024-09-23 13:27:43.647+0000 INFO  Started.
2024-09-23 13:39:36.024+0000 WARN  [bolt-288] The client is unauthorized due to authentication failure.
2024-09-23 13:45:14.843+0000 WARN  [bolt-425] The client is unauthorized due to authentication failure.
2024-09-23 13:45:26.719+0000 WARN  [bolt-430] The client is unauthorized due to authentication failure.
2024-09-23 13:45:36.968+0000 WARN  [bolt-435] The client is unauthorized due to authentication failure.
2024-09-23 13:45:56.775+0000 WARN  [bolt-444] The client is unauthorized due to authentication failure.


### Code of Conduct

- [X] I agree to follow this project's Code of Conduct
@thiagoscodelerae thiagoscodelerae added the bug Something isn't working label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants