Error #6

  • Question
  • Updated 6 years ago
When I try to verify my account I get:

Error: Failed to connect, check network connection. #6

Any ideas?
Photo of

  • 4 Posts
  • 0 Likes
  • frustrated

Posted 7 years ago

  • 9
Photo of Joe

Joe, Official Rep

  • 695 Posts
  • 136 Likes
With release 1.0, we changed the default network protocol to SSL, which sends data over port 443. The first thing to try is to disable this option, by going to the RescueTime preferences, select the Privacy tab, and unselect "Send updates using SSL".

After that option is turned off, go to the Basic tab and try to "Verify" your connection.

Let me know if that works for you!
Photo of

  • 4 Posts
  • 0 Likes
Thanks for the first tip, but when I was trolling through settings that was the first thing I turned off.

Still seems to have the same issue.

What's option 2? (Am I alone with this error?)
Photo of Joe

Joe, Official Rep

  • 695 Posts
  • 136 Likes
The error #6 indicates that RescueTime is unable to resolve the hostname of the web service.

The next thing to try is to see if you can reach the RescueTime web service from a regular browser.

- Check to make sure your machine is able to communicate with the RescueTime servers outside of the data collector. To do this, open a web browser and paste in the following URL:
http://api.rescuetime.com/api/handsha...
The result that should be returned back is: "login failure!"

- Next, do the same test but this time replace the test123 next to the email and password fields with the email address and password of your RescueTime account.
For example: http://api.rescuetime.com/api/handsha...
The result that should be returned back is "login success!"

Let me know if that works from your web browser, in the meantime I'll continue looking at other things that could be causing this issue.

Thanks!
Photo of

  • 4 Posts
  • 0 Likes
OK.

I did as instructed and received the appropriate 'login success!'

That was positive!
Photo of Joe

Joe, Official Rep

  • 695 Posts
  • 136 Likes
Well, that's interesting. I'm still digging into what could be causing it to work from a web browser, but it not working from the command line.

I know it's a pain, but one thing that would help would be if you could re-try RescueTime after rebooting your computer. There have been a couple of instances where unexplained issues were cleared up by this. I'm not real hopeful, but this is feeling like it could be one of those types of issues.

I'll post back when I've figured out what the next troubleshooting step is after that.

Thanks!
Photo of

  • 3 Posts
  • 0 Likes
Not alone i got the same issue
Photo of

  • 3 Posts
  • 0 Likes
Im on mac if that helps just downloaded the app going to try a restart as soon as my software updates!
Photo of Joe

Joe, Official Rep

  • 695 Posts
  • 136 Likes
Matto, did a restart do anything for you after the software installed? I have been unable to hunt down the cause of this issue.

Thanks!
Photo of

  • 3 Posts
  • 0 Likes
Hey yeah did the restart and same error comes up however the app is working sending the info to my account online. So its just when you click verify it says it cant but the app still works fine.
Hope this helps with the bug and if anyone else has the problem just ignore the verify and put in correct account details and it should work anyway :)
(P.S. Great app love the fact i can check the web app on my phone when im bored and away from computer! you should definitely think about looking at the iPhone SDK!...)
Photo of Joe

Joe, Official Rep

  • 695 Posts
  • 136 Likes
Thanks for the update Matto, that helps narrow down where the error might be.
Photo of

  • 4 Posts
  • 0 Likes
Same problem here.

The domain api.rescuetime.com resolves correctly.

OS/X 10.5.2
Photo of

  • 4 Posts
  • 0 Likes
1) Restart didn't help at all here.
2) This is my second time trying RescueTime. The 1st time was on my old G4 iBook and Rescuetime.app was hogging > 75% CPU. Now on my new Intel Macbook that problem doesn't exist but I simply can't login due to this error.
Photo of Joe

Joe, Official Rep

  • 695 Posts
  • 136 Likes
ATrerra, could you send an email to team@rescuetime.com with the email address you are using in RescueTime? I'd like to coordinate with you sometime tomorrow to watch your connections attempts in our incoming logs.

Also, if you are comfortable at the Unix/Terminal level of OS X, I'd like to have you try a couple of manual send commands to see if we can get more details on what is failing with the network connectivity.

Thanks!
Photo of

  • 3 Posts
  • 0 Likes
Just installed to try it out... same problem here... also on a new Intel Macbook. Debug shows failure to connect after each attempt to send file. I get a 404 when entering the URL above (?) Tried disabling SSL and restarting... nothing.
Photo of Joe

Joe, Official Rep

  • 695 Posts
  • 136 Likes
If there is anyone who is having this problem and comfortable with running a command or two at the Terminal level, I'd love to get some information from you.

Essentially, I'm trying to determine if there is more to the error than what we are capturing in RescueTime.

If you are comfortable with using Terminal and can consistently reproduce the Error #6 it would help if I could get some to do the following:

From the Terminal prompt paste in (all on one line):

/usr/bin/curl -k -d 'email=test@test.com&password=testpassword' https://api.rescuetime.com/api/handshake -m 10 -s

You should see something like the following:

System02:~ jhruska$ /usr/bin/curl -k -d 'email=test@test.com&password=testpassword' https://api.rescuetime.com/api/handshake -m 10 -s
login failure!System02:~ jhruska$

Where the important information is the "login failure!".

Paste back your results here or to me in an email at team@rescuetime.com

We'll try to beat this error into submission,

Thanks!
Photo of

  • 3 Posts
  • 0 Likes
Comfortable would be a bit of an overstatement :) But I copied and pasted the above into Terminal. It thought for a minute and then gave me the command prompt again - mycomputer:~ me$ . Nothing else.
Photo of Susheel Chandradhas

Susheel Chandradhas

  • 4 Posts
  • 0 Likes
i got the same reply as j-annastasia I did replace the email id and password as appropriate. I was just returned to the bash prompt.

I'd like to help if i can. I'm not adept with terminal, but i've done my bit of commandline operations.

Would love to co-ordinate with you if necessary. I'd love to beat this down in the next 24 hours if possible. Love your app's potential, if it works I'll be asking the management to use it for sure.
Photo of Susheel Chandradhas

Susheel Chandradhas

  • 4 Posts
  • 0 Likes
oh! i neglected to mention that I've followed the earlier mentioned steps with the same result as earlier people. the link supplied returns a 404 page not found... I've restarted, disabled ssl, all to no effect.

would love to hear from you.
Photo of Joe

Joe, Official Rep

  • 695 Posts
  • 136 Likes
Ok, here is an update for everyone on this issue.

First, I want to thank Susheel who has been great in volunteering many hours of assistance in tracking this issue down.

The short answer is that some DNS servers are not properly resolving the host api.rescuetime.com. The short term work around to this issue is to get your DNS requests from a provider like OpenDNS. See the steps at the end of this post.

The longer term fix is that we are trying to track down why some DNS servers are not correctly responding to cURL's request for domain resolution. This includes us directly contacting DNS support at ISP's where this is occurring. You can assist us by letting us know the following information:

1. Which ISP do you use - and the URL to their web site
2. Which DNS servers you currently have in your Network settings. This can be found on OS X by going to the Apple Menu -> System Preferences... -> Network and pasting in what is in the "DNS Server" line

In Susheel's case, we were able to resolve the issue by having him set his DNS servers to use OpenDNS - a public, popular and free set of DNS servers.

You can set your computer to use the OpenDNS servers by doing the following:

- Open the System Preferences (Apple Menu -> System Preferences...)
- Click on the Network settings and select your current network configuration (Built-in Ethernet or AirPort)
- Click the Advanced... button
- Click on the DNS tab
- Make note of the DNS entry that is currently there in case you need to revert back to your initial DNS entry
- Click the + on the DNS Servers list and add both 208.67.222.222 and 208.67.220.220 to the list
- Click OK and then Apply to make the DNS changes active

NOTE: Changing your DNS servers, especially if you are on a corporate network, might cause other issues with internal customizations. This work around is meant for individuals who are comfortable in making these changes and have the ability to revert the changes back to their previous settings.

Thank you
Photo of

  • 3 Posts
  • 0 Likes
My ISP is http://www.shaw.ca/. DNS Server: 192.168.15.1

HTH.
Photo of x10

x10

  • 1 Post
  • 0 Likes
Hey - I just did the update to AirPort that came down with OS 10.5.3 and it let me connect to Rescue Time for the first time!!!

Before I always got Error #6
Photo of

  • 4 Posts
  • 0 Likes
I don't know which update did it, but it works!

Yay!!!!!

My RescueTime account is finally receiving data, which is revealing that I appear to spend an inordinate amount of time using media players....
Photo of Joe

Joe, Official Rep

  • 695 Posts
  • 136 Likes
Earlier this week I requested reverse DNS entries for our api URLs, so that might have done the trick.

I've got a couple more people I want to have validate it's working before I call it resolved though.

Thanks for the updates guys!
Photo of

  • 4 Posts
  • 0 Likes
Everything working okay now (updated to lasted RescueTime plus 10.5.3 update). Sorry I haven't followed on my original complaint even though you guys tried emailing me to help figure it out.

It works now, good stuff - and thanks for all the effort to contact me and figure it out. Cheers.

Mark
Photo of

  • 1 Post
  • 0 Likes
Ok, so I'm on a weird networking setup here on campus:
- Normal wireless connection which blocks all traffic on all ports except 80 & 1723 for VPN connections.
- Authenticated VPN Session, set to forward all network traffic through the VPN, allows connections on all ports (theoretically).

I can't get RescueTime to verify login when I allow SSL in the RescueTime preferences. And then finally, once I do disable SSL, it will "verify" my login ok, but I won't be able to send updates (does nothing...)

OS is Mac 10.5.6 and RescueTime version 1.0.4