Every time I try to download these files, I get this; "NSPOSIXErrorDomain: 100"

Discussion in 'OS X Yosemite (10.10)' started by wdw_, Jul 28, 2014.

Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.
  1. wdw_ macrumors regular

    wdw_

    Joined:
    Aug 18, 2002
    #1
    Ok, I'm going to be upfront. This only happens when I download torrent files from this one private torrent site. A site I've been going to for YEARS.

    Whenever I click to download a torrent file from this site, I get the "NSPOSIXErrorDomain: 100"

    And this is a straight-up direct link. It's not some redirect.

    When I open the same link in Firefox it just says, "Not Found. Sorry pal :("

    When I open the link in a file downloader like JDownloader, it doesn't work.

    When I input the URL directly into my torrent app, it won't work either.

    Ok, now the weird part. The ONLY way I've gotten it to work, is pasting the link into Google Chrome. Chrome has NO problem downloading the file.

    So, Chrome has been my crutch for he past few months. I've been waiting for the problem to just go away as the new betas have been released, but no luck so far. I should probably just stop using Safari, but I'm used to it, and I'd like to actually fix the problem.

    So what's the connection?

    What changed with Yosemite? What makes Chrome so special? What makes this site such a pain, when I've had absolutely no other problems like this?

    The clues are all there, but it's beyond my skill set.
     
  2. kode54 macrumors newbie

    Joined:
    Jan 15, 2014
    #2
    It also happens when Safari force redirects me to the https version of e621.net, which is a site you probably don't want to browse from work. Try the e926.net work safe version instead, if that is the case.
     
  3. wdw_, Aug 4, 2014
    Last edited: Aug 4, 2014

    wdw_ thread starter macrumors regular

    wdw_

    Joined:
    Aug 18, 2002
    #3
    Hmm. That does bring the same error. Interesting...Thanks!
     
  4. CaffeinatedNoms macrumors member

    CaffeinatedNoms

    Joined:
    Jun 8, 2014
    Location:
    Northeast England
    #4
    I can't speculate on a solution, but I think I can guess at the problem.

    Are the 'block fraudulent sites' options turned on in both Safari and Firefox? I only ask because I remember a few years ago Safari started acting all strange and giving me all sorts of errors because my ISP was force-redirecting every page to the "omg your bill is 0.03nanoseconds overdue" page - and Safari for some reason identified the billings page as a fraudulent site!
     
  5. kode54 macrumors newbie

    Joined:
    Jan 15, 2014
    #5
    I was mentioning a terrible web site that also was having problems with Safari last time I tried it. It stopped doing that after I paved and reinstalled 10.9.4.
     
  6. wdw_ thread starter macrumors regular

    wdw_

    Joined:
    Aug 18, 2002
    #6
    Nah. I've seen it warn me about that, and that's not what it's doing. Plus, disabling that option doesn't make a difference.

    Now, Kode54 mentioning HTTPS has gotten me somewhere. I found out that if I simply remove the S from the HTTP in the address, it just works. So I haven't really solved my problem, but we've discovered a workaround that's achievable without opening Chrome. yay!
     
  7. kode54 macrumors newbie

    Joined:
    Jan 15, 2014
    #7
    You're welcome for that reminder, but I probably should have mentioned, it doesn't work for the booru site I reported, as their http site simply redirects to https.

    The fact that it worked for you to discover that it was a booru site means that the error does not occur for everyone. Or it went away. Or you accessed it with Chrome, which I verified works under Yosemite.

    I stopped using Yosemite for now anyway, as I'm a Hackintosh user foremost, and probably half of the issues I had with Yosemite were related to having non-spec hardware in my system.

    I do plan to buy a 15" rMBP with discrete graphics in a month or two, and make that my full time Mac development platform, but until then, I have this PC desktop, and Mavericks works just fine.

    Plus I'd rather not switch to a platform that makes iCloud useless to older software just yet, especially if it means I have to update my two iDevices to iOS 8 beta to interoperate, since I need those devices for development and testing.
     
Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.

Share This Page