Debian 8.x SSH issue

Rikon · #1 07-07-2015, 05:53 PM

I committed a linux sin and ran an update without paying attention. I can now not get MySQL Workbench or any other database tool to connect to the server and I'm convinced it's SSH-related. I'm getting the following errors when I go to connect. I'm positive something in the upgrade changed how it works. I was on Debian 7.x prior.

Quote:

Authentication error, unhandled exception caught in tunnel manager, please refer to logs for details

Followed by.

Quote:

Failed to Connect to MySQL at 127.0.0.1:3306 through SSH tunnel at xxx.xxx.xxx.xxx:22 with user root

The server is still up (Loremaster), and players are on it. I just can't get to the DB.

demonstar55 · #2 07-07-2015, 06:09 PM

With the "user root" part is that referring to the MySQL user or SSH user? It's possible SSH has logging in as root disabled by default.

jpyou127 · #3 07-07-2015, 07:25 PM

Rerun the mysql command to allow root permission for 127.0.0.1?

**Shin Noir** · #4 07-11-2015, 12:31 AM

You also may want to look at.. logs like it notes?

provocating · #5 07-11-2015, 01:09 PM

I installed the newest Debian at work yesterday. For me to log in as root via SSH, you had to edit the ini file. You could log in as a different user and then su to root.

http://linuxconfig.org/enable-ssh-ro...n-linux-server

Rikon · #6 07-14-2015, 07:23 AM

Quote:

Originally Posted by provocating

I installed the newest Debian at work yesterday. For me to log in as root via SSH, you had to edit the ini file. You could log in as a different user and then su to root.

http://linuxconfig.org/enable-ssh-ro...n-linux-server

Thanks. I'll check this out.

Rikon · #7 07-14-2015, 07:47 AM

What am I doing wrong now? I can get to the mysql CLI via the server, but no access via workbench.

provocating · #8 07-14-2015, 09:01 AM

It says through SSH tunnel, is SSH running and can you SSH to localhost?

image · #9 07-14-2015, 09:03 AM

OS error code 61: No data available

you need to make sure mysql is even running (are you accessing it locally or remotely from this app, need to check what IP is appropriate and the port).. we can't connect to it.

Rikon · #10 07-14-2015, 09:09 AM

Yes, SSH is running. It's how I normally connect via terminal to my server. That's why it's frustrating to me. My server is a VPS, so I am connecting remotely.

N0ctrnl · #11 07-14-2015, 09:54 AM

A dumb question, but you're not trying to connect to 127.0.0.1 from your local machine without a tunnel or anything else setup, are you? 127.0.0.1 is localhost (loopback device), so unless you already have a tunnel forwarding port 3306 on your local box to 3306 on the remote, that's not going to work.

Rikon · #12 07-14-2015, 10:00 AM

No, the image I provided above purposely has my server (SSH) information covered up. The localhost is relative to the SSH host, which is the same server, albeit on port 3306 for MySQL. After provocating's suggestion, I can now get MySQL Workbench to connect to the server via SSH, but now the error pertaining to MySQL is my roadblock.

Edit to add: ls /etc/init.d shows that mysql is running.

Edit #2: nmap shows 3306 open as well on localhost.

Quote:

Starting Nmap 6.47 ( http://nmap.org ) at 2015-07-14 10:09 EDT
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000077s latency).
PORT STATE SERVICE
3306/tcp open mysql

provocating · #13 07-14-2015, 09:45 PM

Use HeidiSQL from another computer, just for kicks. Also, did you give root access to log in to the server remotely? If you are trying to connect to that server remotely via root, that is a security risk and normally has to be changed.

Rikon · #14 07-15-2015, 08:57 AM

Quote:

Originally Posted by provocating

Use HeidiSQL from another computer, just for kicks. Also, did you give root access to log in to the server remotely? If you are trying to connect to that server remotely via root, that is a security risk and normally has to be changed.

For now I am, until I can get this resolved. It won't be that way shortly. I appreciate the assistance. I'll try Heidi from my PC.

Rikon · #15 07-15-2015, 10:37 AM

Quote:

Originally Posted by provocating

Use HeidiSQL from another computer, just for kicks. Also, did you give root access to log in to the server remotely? If you are trying to connect to that server remotely via root, that is a security risk and normally has to be changed.

Wow, works flawlessly with HeidiSQL. No idea why. I guess I'll be using this from here on out.

I really appreciate everyone who chimed. I was pulling my hair out!