This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Help

Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.

New PWD Is Not Working in Neo4 Desktop 4.1.0

renatospaka
Graph Voyager

‎08-18-2020 09:44 AM

Hello folks.

This is another chapter of my learning path for Neo4j. My goal here is to complete the Twitch series for Building Web Applications with Neo4j and TypeScript

In the past 2 days, I was struggling with the loading process of the Movies dataset (small-medium) to Neo4j Desktop, which I finally finished yesterday.
2X_5_526d2c74bd0e7ee9917bae6a9a0483dbcc4de530.png

To test my development environment, I had to provide user & pwd to connect to my Graph in the code, and I just forgot the pwd I setup in the 1st place, so I change it to a new one in the Administration console of the Desktop and restarted the database.

From this point on, nothing seems to work. I cannot login to my graph. The bolt port has changed to a new one (and I don't know the reason). The problem could be just a mistyping of the pwd, so I changed it a few more times and failed every login attempt.

Below you can find the exact point in time when I changed the pwd, restarted the database and...bam! Got stuck again

2020-08-18 00:59:54.755+0000 INFO  Starting...
2020-08-18 01:00:01.093+0000 INFO  ======== Neo4j 4.1.0 ========
2020-08-18 01:00:14.424+0000 INFO  Called db.clearQueryCaches(): Query cache already empty.
2020-08-18 01:00:24.009+0000 INFO  Sending metrics to CSV file at C:\Users\Renato\.Neo4jDesktop\neo4jDatabases\database-efd6656e-a0a8-4575-b51e-bc8fe30c50c9\installation-4.1.0\metrics
2020-08-18 01:00:24.076+0000 INFO  Bolt enabled on localhost:7687.
2020-08-18 01:00:26.129+0000 INFO  Remote interface available at http://localhost:7474/
2020-08-18 01:00:26.133+0000 INFO  Started.
2020-08-18 01:00:38.904+0000 INFO  Note that since you did not explicitly set the port in dbms.connector.bolt.advertised_address Neo4j automatically set it to 11004 to match dbms.connector.bolt.listen_address. This behavior may change in the future and we recommend you to explicitly set it.
2020-08-18 01:00:38.910+0000 INFO  Note that since you did not explicitly set the port in dbms.connector.http.advertised_address Neo4j automatically set it to 11005 to match dbms.connector.http.listen_address. This behavior may change in the future and we recommend you to explicitly set it.
2020-08-18 01:00:38.911+0000 INFO  Starting...
2020-08-18 01:00:47.069+0000 INFO  ======== Neo4j 4.1.0 ========
2020-08-18 01:01:01.233+0000 INFO  Called db.clearQueryCaches(): Query cache already empty.
2020-08-18 01:01:10.650+0000 INFO  Sending metrics to CSV file at C:\Users\Renato\.Neo4jDesktop\neo4jDatabases\database-efd6656e-a0a8-4575-b51e-bc8fe30c50c9\installation-4.1.0\metrics
2020-08-18 01:01:10.701+0000 INFO  Bolt enabled on localhost:11004.
2020-08-18 01:01:12.767+0000 INFO  Remote interface available at http://localhost:11005/
2020-08-18 01:01:12.768+0000 INFO  Started.
2020-08-18 01:01:14.152+0000 WARN  The client is unauthorized due to authentication failure.
2020-08-18 01:02:10.191+0000 WARN  The client is unauthorized due to authentication failure.
2020-08-18 01:02:20.408+0000 WARN  The client is unauthorized due to authentication failure.
2020-08-18 01:02:45.674+0000 WARN  The client is unauthorized due to authentication failure.
2020-08-18 01:02:59.454+0000 WARN  The client is unauthorized due to authentication failure.
2020-08-18 01:03:08.163+0000 WARN  The client is unauthorized due to authentication failure.
2020-08-18 01:28:21.692+0000 WARN  The client is unauthorized due to authentication failure.
APOC couln't set a URLStreamHandlerFactory since some other tool already did this (e.g. tomcat). This means you cannot use s3:// or hdfs:// style URLs in APOC. This is caused by a limitation of the JVM which we cannot fix. 
2020-08-18 15:43:35.123+0000 INFO  Note that since you did not explicitly set the port in dbms.connector.bolt.advertised_address Neo4j automatically set it to 11004 to match dbms.connector.bolt.listen_address. This behavior may change in the future and we recommend you to explicitly set it.
2020-08-18 15:43:35.127+0000 INFO  Note that since you did not explicitly set the port in dbms.connector.http.advertised_address Neo4j automatically set it to 11005 to match dbms.connector.http.listen_address. This behavior may change in the future and we recommend you to explicitly set it.
2020-08-18 15:43:35.127+0000 INFO  Starting...
2020-08-18 15:43:35.123+0000 INFO  Note that since you did not explicitly set the port in dbms.connector.bolt.advertised_address Neo4j automatically set it to 11004 to match dbms.connector.bolt.listen_address. This behavior may change in the future and we recommend you to explicitly set it.
2020-08-18 15:43:35.127+0000 INFO  Note that since you did not explicitly set the port in dbms.connector.http.advertised_address Neo4j automatically set it to 11005 to match dbms.connector.http.listen_address. This behavior may change in the future and we recommend you to explicitly set it.

Now I have no authorization to login to my graph and really don't know what is going on...

This is it. I need help.

Thanks in advance.

Labels:
0 Kudos
Reply
0 REPLIES 0
Nodes 2022
Nodes
NODES 2022, Neo4j Online Education Summit

All the sessions of the conference are now available online

Watch replays