iTunes Error

[DJTaurus]

Any fix for the itunes port 443 error?

port 443 error itunes

 

[hazey]

Im receiving the same error AS WELL as a message saying "The item youve requested is not currently available in the US store" every time I try to click on the Itunes store tab, it wont even show the store main page.

 

[odoy]

Great! i get this message every minute.
the good, im not alone. And again! spent 1h with clicking, searching, logging in/out and at the end, its apples fault 😡 AGAIN! 😡 FU!

 

[bmauter]

Is this the error you're getting? I get this repetitively and I haven't changed or installed anything. I just got it on the latest 10.11.2, but I started seeing it maybe a couple weeks ago.

 

[mcvaughan]

Seeing the same, as well as missing music and playlists. Running 10.10.5 over here.

 

[DJTaurus]

Is this the error you're getting? I get this repetitively and I haven't changed or installed anything. I just got it on the latest 10.11.2, but I started seeing it maybe a couple weeks ago.
View attachment 604649

yeap thats it...

 

[PinkyMacGodess]

Is this the error you're getting? I get this repetitively and I haven't changed or installed anything. I just got it on the latest 10.11.2, but I started seeing it maybe a couple weeks ago.
View attachment 604649

Mine just started post 10.11.2 update. VERY ANNOYING!!!

No idea of a fix?

COME ON APPLE, IS IT REALLY THAT HARD TO TEST YOUR UPDATES BEFORE RELEASING THEM TO THE PUBLIC???

 

[PinkyMacGodess]

Apple Support thread is saying that there is no way to fully kill this error.

There is another thread here about this error...

 

[PinkyMacGodess]

Nevermind...

 

[Weaselboy]

SO I'm saying that if you haven't done the 10.11.2 update, DO NOT DO IT!!!

I don't think it has anything to do with 10.11.2. I you look a couple posts up there is a user on 10.10.5 also having this issue. I'm guessing it is a configuration issue on Apple's end.

 

[PinkyMacGodess]

I don't think it has anything to do with 10.11.2. I you look a couple posts up there is a user on 10.10.5 also having this issue. I'm guessing it is a configuration issue on Apple's end.

My post was a reaction to the problem starting after the .2 update. Yes, it looks like a configuration issue at the far end, and, so far at least, all is working as expected here now...