Sign in
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Can't login

  • By Saj
  • on 08/15/2020

Even after using login id, the authentication is failing, should instance id is with i- or without i- ? A better way to give document is give sample page for instructions


  • By love neo4j, hate its auth
  • on 08/04/2023

I'm having the same issue... no solution yet (neo4j/neo4j or neo4j/i-instance)

  • By jocon
  • on 03/12/2021

Although the instructions say to log in as neo4j/instance, that did not work. Try neo4j/neo4j and that did the trick - it takes you to the change pws screen.

  • By Someone that no longer likes neo4J
  • on 10/05/2020

same here. I am not sure what to do, and there is no documentation. I spun up another instance a few weeks ago and it worked just fine. The password was the instance id. I am going to try to ssh in and disable auth. But this is a pretty annoying issue. Already exploring alternative dbs to use.

  • By Krey
  • on 09/25/2020

The password is not being set so the info is the default neo4j password of "neo4j"

  • By Krey
  • on 09/25/2020

I have been having the same problem. Have you found the fix for it?

  • By Anthony
  • on 09/11/2020

I'm having the same problem. I try to log in with the instance ID, and I get: "Neo.ClientError.Security.AuthenticationRateLimit: The client has provided incorrect authentication details too many times in a row." This occurs after just one or two attempts using either the neo4j+s:// or bolt+s:// attempts. I create the Instance from the AMI, and assign an ElasticIP to it. I've also SSH'd into the new VM and done the password reset .sh script to ensure that the default password is the instance ID, and I still cannot connect to the database(s). I've terminated and recreated instances probably a dozen times and attempted to connect, but no luck. I'm certain I've pasted the Public IP Address of the node into the connection URI, and that the port(s) are correct depending on neo4j or bolt protocols. Additionally, I cannot see any way to reset the attempt count for the neo4j account, so that basically leaves me with a dead instance that I can't connect to. I've seen people say to blow away the database entirely and let neo4j recreate it, but there should be some administrative scripts accessible through SSH that a sudo su superuser could execute to override the "too many times in a row" and unlock an account for subsequent attempts. I've not found anywhere online that explains if that's even possible somehow. Very frustrating, spent all day messing around with this and no luck.