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

Error No. 1 – Http Error. Could Not Connect To The Tunneling Url

forums forums SQLyog Using SQLyog Error No. 1 – Http Error. Could Not Connect To The Tunneling Url

  • This topic is empty.
Viewing 10 reply threads
  • Author
    Posts
    • #11754
      GeoffreyB
      Member

      I am at a bit of a loss. A couple of days ago I upgraded my Internet connection from an ADSL 1 package (speeds 1500/256) to an ADSL 2 package (speeds 20000/512). In doing so I also had to upgrade the firmware in my Speedstream 4200 modem.

      Ever since I have got this Error No. 1 – HTTP error. Could not connect to the tunneling url.

      I thought it might be the firewall so I turned it off and tried no luck.

      I have check all settings and even reuploaded the SQLyogTunnel.php file.

      Still no go.

      I would appreciate any help.

    • #30024
      peterlaursen
      Participant

      Please first tell if you can “connect to the tunnelling URL” with a web browser? And of course double-check that the URL/path in SQLyog HTTP-tab is correct.

    • #30025
      peterlaursen
      Participant

      You did not tell the program/SQLyog version you are using.

      If it is recent and if you are sure the URL is correct you can try experiment with the base64 option in HTTP tab/advanced options. Maybe a stupid idea but one possibility is that the new firmware has a problem with the XML data stream.

    • #30026
      GeoffreyB
      Member
      peterlaursen wrote on Nov 13 2009, 07:31 AM:
      Please first tell if you can “connect to the tunnelling URL” with a web browser? And of course double-check that the URL/path in SQLyog HTTP-tab is correct.

      Thanks Peter, Yes I can connect using a web browser.

    • #30027
      GeoffreyB
      Member
      peterlaursen wrote on Nov 13 2009, 07:37 AM:
      You did not tell the program/SQLyog version you are using.

      If it is recent and if you are sure the URL is correct you can try experiment with the base64 option in HTTP tab/advanced options. Maybe a stupid idea but one possibility is that the new firmware has a problem with the XML data stream.

      I am using V 8.17

      I tried the base64 option no different.

    • #30028
      peterlaursen
      Participant

      Does this device+firmware has some (like browser-interface) controls/settings you could check?

      Except for this I wish I knew how I could advice here – but I have no good ideas.

    • #30029
      peterlaursen
      Participant

      I sent you a PM with another URL you could try.

    • #30030
      GeoffreyB
      Member
      peterlaursen wrote on Nov 13 2009, 08:16 AM:
      Does this device+firmware has some (like browser-interface) controls/settings you could check?

      Except for this I wish I knew how I could advice here – but I have no good ideas.

      I have checked the setting in the modem control panel. Nothing that I can see that should affect this.

      An interesting thing though. I have a scheduled backup of my database using SQLyog, it has just started and is accessing the remote database properly. I would assume that the scheduled backup facility uses HTTP tunneling as well. Is this correct

      addendum: This process did complete however the screen and log file did report the “HTTP Error. Could not connect to the tunneling URL.” on one request only.

    • #30031
      GeoffreyB
      Member

      This is very weird. SQLyog is now working fine. I have not changed anything. I could be that me logging into the modem control panel even though I didn't change anything has fixed whatever the issue was.

      Thanks for you efforts

    • #30032
      peterlaursen
      Participant

      “I would assume that the scheduled backup facility uses HTTP tunneling as well. Is this correct”. How should we know? Please open the jobfile in an editor and see for yourself if it uses HTTP tunnelling.

      But pretty weird that the errors occurs and still job completes. I think you have setting 'abort on error' = NO?

    • #30033
      peterlaursen
      Participant

      I did not see your last post when writing my last post. I think rather it was a temporary issue with your hosting. But …. who can tell .. maybe the firmware upgrade was not complete .. or just Santa Claus was on vacation!

      We will consider this as closed unless you write here again. And the tunneller instance that I uploaded to our server will be deleted in 2 minutes.

Viewing 10 reply threads
  • You must be logged in to reply to this topic.