I'm trying to connect to oracle free cloud using mobaxterm but I'm receiving:
Unable to use key file "X:\\oracleCloud\\ssh-key-2020-10-11.key" (OpenSSH private key)
No supported authentication methods available (server sent: publickey,gssapi-keyex,gssapi-with-mic)
────────────────────────────────────────────────────────────────────────────────
Session stopped
- Press <return> to exit tab
- Press R to restart session
- Press S to save terminal output to file
I used the public ip + opc (as it's centos based machine), as well as the private key that was generated when I created the instance.
Any idea on what I am missing?
In order to be able to connect, I generated a ssh key pair using puttygen. Seems the generated ones from oracle were the problem.
I had the same problem in Mobaxterm 20. The key file worked fine in normal SSH, but with MobaXterm I received the same error message as you.
I've updated to MobaXTerm v 22.1 and it works fine
Related
When executing the cloudproxy file, while using the quickstart guide implementation, the script gets stuck after the following messages:
Listening on 127.0.0.1:3306 for ...:...:....,
Ready for new connections
Generated RSA key in 70.1684 ms
after which it just gets stuck without any error messages.
I can access the database just fine in the cloudshell environment, but I would like to access it using scripts that are running remotely.
UPDATE Feb 2022: this issue may have been fixed in more recent versions. See comments on the accepted solution.
Summary:
An existing connection to a remote database in Navicat was working using a domain name for the SSH > Host field. After building a new remote server and pointing the domain at the new IP address (and setting up the database and users, as well as adding your public RSA key to the new server), Navicat doesn't trust the key hash from the server. Replacing the entries in ~/.ssh/known_hosts doesn't help.
Steps to reproduce:
point the domain for a remote database at a new IP address
add your RSA public key to the authorized keys on the remote server
add the remote database and users on the remote server
in Terminal, ssh into the new remote server using the domain, and follow the prompts to add the new server to the known_hosts file
in Navicat (specifically Navicat Essentials for PostGreSQL, but this issue will apply to any app in the Navicat suite on Mac) edit an existing connection to the remote server
on the SSH tab in the "Edit Connection..." window, click 'Test Connection'
Expected:
Navicat uses the updated ~/.ssh/known_hosts file to authorize connection to the remote server
Actual:
Navicat fails to connect
Error:
The server key has changed. Either you are under attack or the administrator changed the key.
New server key hash:...
Question:
How to get Navicat to accept the new known_hosts data and authorize the connection?
Problem:
Navicat uses a different known_hosts file than the operating system does. So updating ~/.ssh/known_hosts doesn't affect the Navicat connection to the remote server.
Solution:
Optional workaround:
in Navicat, edit the database connection
on the SSH tab, change the Host field from a domain to the new IP address
Fix:
in Terminal, run sudo find ~ -name known_hosts
the results will include something like (using Navicat Essentials for PostgreSQL as an example):
/Users/<user>/Library/Containers/com.prect.NavicatEssentialsForPostgreSQL12/Data/.ssh/known_hosts
edit that file and remove the line starting with the domain for your remote server
return to Navicat and click Test Connection again. The connection should work.
If you see the error: Access denied for 'publickey'. Authentication that can continue: publickey,password (101203) or similar, check the Authentication Method selection and, if you're using 'Public Key' or 'Password and Public Key', click the 'Private Key' file navigator and re-select one of the private keys matching a public key that you've added to the remote server.
For a database course that I'm in, the professor has tasked us with setting up several VM MySQL servers and remote connections. I've found proper documentation to solve most of my problems, but I've pored over docs trying to find a solution to my latest issue.
I've set up an Ubuntu VM on the Google Cloud Compute Engine. I installed a MySQL server to this VM instance, and I need to log in remotely from my laptop. I've followed this documentation https://cloud.google.com/solutions/mysql-remote-access and this youtube video https://www.youtube.com/watch?v=f5qQDm3ciDg.
However, I still get an Unable to Connect to Server message when I test my connection. What could I be overlooking that will help me connect?
Thanks!
So, I slammed my head against a wall for long enough to realize that ssh will be an easier solution than a direct connection.
So, at least for my Windows machine, these are the steps I followed to make the connection:
Download the sql server (You don't need to add a user unless necessary, and you don't change the bind-address in the config file).
Use PuTTYgen to create a private public key pair. Export the private key as an openssh format (in the export options)
Click the edit button on your VM instance then scroll down to the SSH key section.
Paste the public key into the text box (be sure to change the last comment portion to a username on the Linus VM)
Use the SSH connection on MySQL Workbench. Use the external IP of your VM as the first (ssh) host name and localhost as the second (SQL) host name. Input all other info as it is asked for.
I need to set up MySQL database in my computer. I downloaded the Windows (x86, 32-bit), MSI Installer from here.
I run the installer. At the final stage, the installer reach Apply configuration stage.
But it stops at Starting Server. The log says:
MySQL error 0: Retrieval of the RSA public key is not enabled for insecure connections. Failed to connect to MySQL Server 8.0.11 after 10 attempts. Ended configuration step: Starting Server
I already entered a root and added a user and created a password for them. The passwords had yellow warning, meaning that they are not strong, but also not weak. The wizard accepted them so I proceeded.
Can you please help me identify the source of the problem and how to solve it?
EDIT:
I am using Windows 10. The server is my localhost.
I had the same problem after importing some new data into my DB.
Deleting and then recreating my MySql User worked for me.
I am trying to make the connection to a remote mysql database in CloverETL Designer (Community Version)
Documentation with examples on this subject seem fragmented so I have tried to piece the bits together but I'm not use if they are correct. I would be grateful for any suggestions or further clarification on this subject.
Here is what I have so far:
The SSL Certificate
As an alternative VPN connection the server guys passed me the raw CA certificate, which I saved as a .crt file in the conn folder of the CloverETL workspace.
CloverETL Connections
I created a new DB connection and tested it was working without SSL
In the graph window I created a simple graph
Switching to Source View I added the parameter attribute to the connection code like this:
<Connection database="MYSQL" dbURL="jdbc:mysql://hostname/database_name" id="JDBC0" jdbcSpecific="MYSQL" name="CPM" parameters="ssl=${WORKSPACE}/conn/mysql_cpm_cert.crt" password="password" type="JDBC" user="username"/>
Then I tested the connection to the database by creating new metadata from a DB table
The problem is that I don't know if the connect is now secure or not.
Here's the list of resources that I used to piece together the information:
components:bulkloaders:mysql_data_writer [CloverETL wiki]
MySQL :: MySQL 5.0 Reference Manual :: 6.3.6.3 SSL Command Options
Thanks
CPM
Your setup almost certainly does not use ssl. Both links you posted are not usable - first describes bulk loader and second connection via command line client. But what you need is to configure JDBC. So I would use http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-configuration-properties.html section "Security."
I would set:
useSSL=true
requireSSL=true
You will do that by adding items in table (Custom JDBC properties) on second tab (Advanced) of Connection Wizard. In source it should appear like "jdbc.useSSL=true jdbc.requireSSL=true" not "parameters=".
Then connection should fail, because in your default java key store is missing your certificate. It can be imported via http://docs.oracle.com/javase/1.4.2/docs/tooldocs/windows/keytool.html section "Importing Certificates"
I hope this helps.