I just updated my Lightroom version from 5.4 to 5.6. I'm using a PC and have the Adobe CC Photographers package. After upgrading, my Book module will not sign into Blurb. This was never a problem in version 5.4. It just hangs in the Sign In window forever. I also noticed when I try to sign in to Lightroom Mobile, it says that "Your computer does not appear to be connected to the internet". I am able to search the web without issue (and post to this forum) so I do not think that is the case. I'm thinking this might be related to the issue signing in to Blurb.
I have tried restarting Lightroom, and my computer. I have tried turning off my firewall. I also read the following similar thread which has not been resolved. Similar to the last poster, I tried the links provided and got to a web page that simply says "Nothing to see here. You want the Adobe Revel site instead."
I'm not really sure what to do here so any help would be greatly appreciated. My main concern is being able to log into Blurb to upload a book. Logging into Lightroom Mobile is not my concern at this time, I just thought that might be part of the problem.
I downgraded to version 5.5 and that solved my Blurb login issue. Still does not answer this question though as I'd like to be on the most recent version.
I have lightroom 5.6 standalone and am having the same problem, very frustrating. Some things works (flickr upload) some things don't (behance) my computer is clearly connected to the internet and has not connectivity issues for anything else - so at the very least that is an embarrassingly inaccurate error message for lightroom. Would love it if adobe could actual solve this issue. I have also tried the links one is supposed to need access to only to discover I do have access https://api-lr.adbecrsl.com/ and https://imageup-lr.adbecrsl.com/ with the same message: "Nothing to see here. You want the Adobe Revel site instead." Which makes it feel like like some kind of transition issue where they are moving urls but don't have redirects working properly, or they have a few misconfigured servers behind a load balancer.