- 3,741,217 Users
- 2,248,392 Discussions
- 7,861,679 Comments
Forum Stats
Discussions
Howdy, Stranger!
Categories
- 381.2K All Categories
- 2.1K Data
- 204 Big Data Appliance
- 1.9K Data Science
- 446.6K Databases
- 220.6K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 23 Multilingual Engine
- 511 MySQL Community Space
- 462 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 448 SQLcl
- 3.9K SQL Developer Data Modeler
- 185.6K SQL & PL/SQL
- 20.8K SQL Developer
- 291.8K Development
- 7 Developer Projects
- 117 Programming Languages
- 288.6K Development Tools
- 94 DevOps
- 3K QA/Testing
- 645.3K Java
- 18 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.7K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 12 Java Essentials
- 141 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 197 Java User Groups
- 23 JavaScript - Nashorn
- Programs
- 192 LiveLabs
- 34 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 165 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
MySQL Workbench could not connect to the SSH Server, how to solve?
I've recently had to change the SSH keys of my hosts, due to them being virtualized clones. The problem is that now I don't know how to make MySQL Workbench connect with SSH. It gives me a warning stating that the public key changed (correct), then it gives me a generic error: "Could not acquire management access for administration System Error:"
Testing the connection will instead simply state Test Connection ERROR.
So, how do I make the workbench acknowledge the new SSH key and fix the warnings?
Possibly important to state, before I changed the keys, I could connect without a problem with the workbench SSH.
Best Answer
-
The documentation wasn't helpful. After some messing around I found out that the problem was because I forgot to delete the line from my user's known_hosts file regarding the old fingerprint. (/home/username/.ssh/known_hosts)
Answers
-
Did you replace all the files? be sure to consult https://dev.mysql.com/doc/workbench/en/wb-mysql-connections-methods-ssh.html
-
The documentation wasn't helpful. After some messing around I found out that the problem was because I forgot to delete the line from my user's known_hosts file regarding the old fingerprint. (/home/username/.ssh/known_hosts)
