chopper's dashboard

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

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!

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....

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

My ISP is http://www.shaw.ca/. DNS Server: 192.168.15.1

HTH.

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

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.

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.

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.

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!

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.

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!

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.

Same problem here.

The domain api.rescuetime.com resolves correctly.

OS/X 10.5.2

Thanks for the update Matto, that helps narrow down where the error might be.

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!...)