Unsupported Screen Size: The viewport size is too small for the theme to render properly.

1045 Error With Ssh Tunneling

forums › forums › SQLyog › Using SQLyog › 1045 Error With Ssh Tunneling

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • January 15, 2007 at 8:48 am #10130
      swayne
      Member

      I am getting the 1045 error using the SSH tunneling. I have verified the database user name and password using the command line login in a shell.

      When I attempt to connect, it says I am trying to connect using @localhost.localdomain using password YES.

      I am not using password yes, and I am not connecting to localhost.localdomain but rather just localhost

      any ideas?

    • January 15, 2007 at 1:07 pm #23234
      peterlaursen
      Participant
      Quote:
      I am not using password yes, and I am not connecting to localhost.localdomain but rather just localhost

      basically this a a MySQL authentication issue – connection is OK!

      first:

      “using password = YES ”  just tells that you are using password.  MySQL will not send print the password in readable form on the screen, but use this 'metafor”

      next:

      “I am not connecting to localhost.localdomain but rather just localhost” .  Yes that is a problem with the configuration on certain variants of *nix!

      “database user name and password using the command line login in a shell”  Problem is that a shell logon is not tunnelling and the two may be treated differently by the OS.

      This FAQ has some similar discussions..

      http://www.webyog.com/faq/23_36_en.html

      Is it possible to create a 'user'@'localdomain' by using some alias or the ip?  What about 127.0.0.1 as host ??

      This 'localdomain' occurring form time to time can be tricky.  And I am naot the expert to answer it.

      Please post any solution that you may find – by studying configuration, experimenting or by the help of others.

    • January 15, 2007 at 6:04 pm #23235
      swayne
      Member

      I changed my hosts file to add the following entry:

      127.0.0.1 localhost

      and it worked. Thanks

  • Author
    Posts
Viewing 2 reply threads
  • You must be logged in to reply to this topic.