Ssh Tunnelling Worked In 5.18, But Not In 5.20

[tyrathect]

I had set up SSH Tunnelling on Version 5.18 and it worked well. In the Community Version, the Connection Test worked, and in the Trial Enterprise Edition, it connected ok.

Now, with the exact same settings in Version 5.2 (Community as well as Enterprise Trial), it does not work and I get “FATAL ERROR: Network ERROR: connection timeout”. In the end, I even copied the sqlyog.ini from 5.18 to 5.20, but still with no results. I also tried HTTPS tunnelling, but the same error occurs.

What's going on, I wonder? ^^;;;

[peterlaursen]

Quote:

What's going on, I wonder? ^^;;;

Well, I wonder too. There is absolutely no intentional difference between the two in this respect!

But I can confirm the issue with 5.2 and SSH-tunnelling (I have no option to test HTTPS at the moment).

So yes .. beta trouble. Every bit of code has been moved around and something went wrong it seems!

It is likely that it is a trival bug! Will be fixed of course.

HTTP-connection works OK here. Can you confirm this?

Thanks for beta-testing!

[peterlaursen]

ooooops!

The PLINK that was shipped with the 5.2 installer is the wrong version. It is the one we used before 5.15. A 'last moment mistake'. The PLINK that ships with 5.18 works with 5.2 too. You can copy it. Will be fixed in Beta2 of course (planned for the end of the week).

We cannot reproduce the HTTPS problem however! You write:

Quote:

I get “FATAL ERROR: Network ERROR: connection timeout”. In the end, I even copied the sqlyog.ini from 5.18 to 5.20, but still with no results. I also tried HTTPS tunnelling, but the same error occurs.

Do you seriously mean that you get “FATAL ERROR: Network ERROR: connection timeout” with HTTPS too?

[tyrathect]

peterlaursen wrote on Sep 5 2006, 09:46 AM:

We cannot reproduce the HTTPS problem however!

Do you seriously mean that you get “FATAL ERROR: Network ERROR: connection timeout” with HTTPS too?

Well, here is more weirdness. I re-installed SQLyog today to re-check this. Now, SSH tunnelling and HTTPS tunelling works fine, and so it does on the other machine I tried it on yesterday (and it didn't work there, either). So I installed it on a third machine today (first time there), and I got the SSH/HTTPS tunnelling errors there. I'll try again on that machine tomorrow, if it does work there then, it seems to be a bug in the trial expiration calculation…

[peterlaursen]

Quote:

it seems to be a bug in the trial expiration calculation…

If it has expired it willl tell you so!

[tyrathect]

peterlaursen wrote on Sep 5 2006, 11:19 PM:

If it has expired it willl tell you so!

It has not expired, I installed SQLyog on the mentioned computers in the past two days. Problem is, on the first day I installed it (1st day of trial, 30 days left), it did not work, but on the second day (2nd day of trial, 29 days left), it does.

[peterlaursen]

Quote:

it did not work

You will have to be more specific in describing the possible error. It is NOT a miscalculation in the verirication of the trial period, because then it would have displyed something like “Your trial period has expired …”

You are quite sure it was not an 'error 40' ?

[tyrathect]

peterlaursen wrote on Sep 6 2006, 07:42 AM:

You are quite sure it was not an 'error 40' ?

I have installed SQLyog on 3 computers (4 since today, see below). The error message is “FATAL ERROR: Network ERROR: connection timeout”, nothing else.

peterlaursen wrote on Sep 6 2006, 07:42 AM:

You will have to be more specific in describing the possible error.

Ok, here's again what happens. When installing the trial version and trying to connect via SSH tunnelling, I get “Connection Timeout” errors, no matter what I do. But if I try again the next day, everything works perfectly. This behavior occured on two computers with Win98 and another one with Win2k. However, as I found out today, with WinXP it works from the first day already.

peterlaursen wrote on Sep 6 2006, 07:42 AM:

It is NOT a miscalculation in the verirication of the trial period, because then it would have displyed something like “Your trial period has expired …”

Well, ok, I can't really know ^^; I just thought it might be, since the connection test works from the start in the community edition, and it works after a day has passed in the trial edition.

[peterlaursen]

Quote:

This behavior occured on two computers with Win98 and another one with Win2k. However, as I found out today, with WinXP it works from the first day already.

I do not believe that the OS should nmake any difference. I think there was a server problem!

[tyrathect]

peterlaursen wrote on Sep 7 2006, 11:17 AM:

I do not believe that the OS should nmake any difference. I think there was a server problem!

No, there wasn't. I was connected to the server that was used as tunnel with putty at the same time, and connected to the database server with phpMyAdmin, also at the very same time. It hosts part of the live system, too, so we would have been flooded with customer's complaints if the server would have been unreachable. I think I can fairly guarantee that there was no problem with the servers.

Our local network is ok, too, nothing was changed there, anyway (I am one of two people who would can change any settings, so…)

Aside from that, SQLyog was already working on one machine (which was on day 2 of the trial period), while at the same time it was not working on the computer right next to it (which was still on day 1 of the trial period).

Anyway. I'm quite out of computers now to install SQLyog on (without annoying people in the company, that is), so there's no more testing from me. Either you believe me, or you don't.

Aside from this, SQLyog is great and I will recommend the purchase of some licenses for our company after a few more days of testing. The described bug (if it is one) doesn't bother much, it might be solved with the full version in the best case.

Besides, there's something I couldn't find in the documentation and merely found out by coincidence. The SSH tunnel server uses private/public key authentification. Actually, I was quite surprised to find out SQLyog was working with this server as tunnel at all, since there are no settings for specifying a key. On the 3rd and 4th machine I installed SQLyog on then, I finally got authentification errors. I finally found out that the computers where I could connect through the tunnel had saved Putty Sessions (with the required key file specified) on them that had the same name as the server specified in the Tunnel Server setting in SQLyog, while the computers where I could not authenticate did have Sessions for the tunnel server, but saved with a different (abbreviated) name.

If this is addressed somewhere in the documentation, I could not find it…

[peterlaursen]

Quote:

Either you believe me, or you don't.

We will have to look into if there is some difference with the TCP implementation on XP compared to previous versions that could have this effect.

Quote:

If this is addressed somewhere in the documentation, I could not find it…

nope it is not adressed. I also do not think we support this authentication. There is no setting for entering the PRIVATE KEY info either.

I will call in assistance here! 🙂

[tyrathect]

peterlaursen wrote on Sep 7 2006, 03:29 PM:

nope it is not adressed. I also do not think we support this authentication. There is no setting for entering the PRIVATE KEY info either.

I will call in assistance here! 🙂

Well, if you ever do support it, it will be a nice feature. Until then, “my” Putty workaround can be applied to achieve public/private key authentication for SSH tunnelling.

In any case, thanks for bearing with me 🙂 This kind of nice and polite assistance is quite rare, and is another reason why I decided SQLyog is the right tool for our company 🙂

[Rohit]

@tyrathect:

You are right. PK authentication is not supported right now. However, we plan to build it in near future.

[Author]

Posts