Loading Profile...
Error connecting with new Cocoalicious 1.0b45
Hi Buzz, first off - I really like Cocoalicious and I really appreciate that you've written this software and made it freely available to the world - very very cool! While reviewing your site, I noticed your Feb 15 2008 blog entry about the update so I downloaded and installed the new Cocoalicious v1.0b45 from your website.
I thought you'd like to know that when I started this new release of Cocoalicious I encountered this error:
HTTP Error: server error (0)
Cocoalicious encountered an error while trying to communicate with the server. The problem is most likely on the server side.
Once I press [OK] my bookmarks load (presumably from the cache file) but it doesn't appear that I'm communicating with the del.icio.us website. I verified that the new Del.icio.us API url was set in Preferences and that I can get to https://api.del.icio.us/v1/ using curl
When I attempt to Refresh using the menu item, Cocoalicious crashes (I saved the error text if you are interested).
Have you seen this problem?
It could be that there is some other network issue causing this problem and that Cocoalicious is just fragile due to some external network issues - or it could be something you want to explore.
I re-installed the old Cocoalicious v1.0b43 and it doesn't crash, but it now does not seem to properly submit new entries to Del.icio.us.
I thought you'd like to know that when I started this new release of Cocoalicious I encountered this error:
HTTP Error: server error (0)
Cocoalicious encountered an error while trying to communicate with the server. The problem is most likely on the server side.
Once I press [OK] my bookmarks load (presumably from the cache file) but it doesn't appear that I'm communicating with the del.icio.us website. I verified that the new Del.icio.us API url was set in Preferences and that I can get to https://api.del.icio.us/v1/ using curl
When I attempt to Refresh using the menu item, Cocoalicious crashes (I saved the error text if you are interested).
Have you seen this problem?
It could be that there is some other network issue causing this problem and that Cocoalicious is just fragile due to some external network issues - or it could be something you want to explore.
I re-installed the old Cocoalicious v1.0b43 and it doesn't crash, but it now does not seem to properly submit new entries to Del.icio.us.
I’m curious
11
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hello,
Change the api URL with this one :
http://api.del.icio.us:443/v1
It worked for me (I discovered this by doing a curl https://api.del.icio.us/v1 )
1 person says
this solves the problem
-
Inappropriate?I have seen this a bit (not all the time, but occasionally). I will have to look into it.
-
Inappropriate?I too get a server error, but relaunching the app repeatedly eventually connects so I think this is more a problem with load on their servers.
The url supplied above seems to make this a bit more reliable, though errors do still occur for me.
I’m patient
-
Inappropriate?Hi all - I too found the alternate del.icio.us url that Thomas suggested above but when I tried it I had similar results to metafeather. After a little review of the Del.icio.us API help page, I decided that maybe the re-direct document is incorrect and we should be explicitly using the "https" protocol rather than "http" - so I changes the url to this:
https://api.del.icio.us:443/v1
Cocoalicious seems to be working much better now - so maybe this was the problem?
Isn't the https url above with port 443 the equivalent of an https url without explicitly using the port?
I’m unsure
-
Inappropriate?I think a lot of this has to do with Yahoo's servers being increasingly temperamental. I have some inside info from the Delicious team that I think might help me with this, so I'll be working on a new release to hopefully fix those problems.
-
Inappropriate?Buzz, Thanks for looking into this issue.
I wonder whether other API users are also experiencing this issue - it seems like intermittent behavior, but your mention of contact with the Delicious team suggests it may be more widespread.
Regardless of the cause - any resolution would be much appreciated.
I’m hopeful
-
Inappropriate?I think the problem is related to delicious' new rules of waiting between queries or something. I read on their website that the 503 error that I get is due to being throttled by delicious for breaking their rules. -
Inappropriate?I've tried all of these solutions and have not gotten it to work once on my MacBook 10.5.2 -
Inappropriate?I'm not using Leopard yet - so there may be some other problem that is Leopard-specific. Is anyone else having Cocoalicious problems with Leopard?
Also are you using version 1.0 (43) or 1.0b45?
You might also try:
* make sure your API URL is set as above in Preferences
* shutdown Cocoalicious
* move/rename or backup and delete your local Cocoalicious cache directory:
~/Library/Application Support/Cocalicious.app (where "~" is your home directory)
* restart Cocoalicious - it should rebuild your cache
As recently as two weeks ago, I found that I was not able to use Cocoalicious to make new additions (they'd add in Cocoalicious but not online in Del.icio.us); backing up and nuking my cache directory and restarting fixed the problem.
Of course, anything added in Cocoalicious prior to nuking the cache is gone - since I have a backup I used diff to figure out what was missing, but I didn't find an easy way to sync the "Offline" updates with Del.icio.us online.
** Buzz - this Offline Sync capability would be a good feature - I'd be happy to prototype it!
I’m hopeful
-
Inappropriate?Yesterday it didn't work. Today it does. Did nothing different. Go figure.
-
Inappropriate?I have the same problem with Leopard 10.5.2 and b45.
Somehow I found a 1.1 version. Is it unofficial or what?
Anyway, same behavior with this version -
Inappropriate?The 1.1 version is unofficial. As I said before, these problems are largely caused by the fact that del.icio.us has started really throttling clients aggressively. Again, I have some info that might help with this, but I have about three other projects that take precedence over Cocoalicious now, so it may be awhile before I can look at this. Sorry.
-
Inappropriate?I just recently started having this problem. I'm using version 1.0/45. All it took to solve this problem for me was to add a trailing backslash on the URL. I copied the URL from the del.icio.us API page, pasted into the Cocoalicious preferences and it started working again. The trailing backslash was the only difference in the URLs. Odd, eh? -
Inappropriate?Oops. Nevermind. I followed the wrong link. The problem I was having is getting a 503 error from del.icio.us.
-
Inappropriate?I have this problem, "HTTP Error: bad gateway (502)", and have never been able to connect with Cocoalicious.. but I would really like to!
Anyone have any ideas?
-
Inappropriate?b46 fixes this i think -
Inappropriate?I just found this app today, and it sounds very nice. I downloaded ver 1.0b46a, and have not been able to connect. Is yahoo still throttling things down, or is there a different url to use?
thanks in advance -
-
Inappropriate?While it's not quite definitive, this approach may work: http://getsatisfaction.com/scifihifi/...
I’m hopeful
EMPLOYEE
