Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Error enabling photo stream "iphoto was unable to connect to Photo Stream"

Whenever I try to enable Photo Stream, it times out after awhile, and I get the following error: "iPhoto was unable to connect to Photo Stream." (see below [1]). I "tcpdump" shows that the computer is trying to open connections to akamai (unrelated?) but not apple. I am using iPhoto 9.2 build 626.


There is one oddity in this scenario : I have one iCloud account that I am trying to use between three computers. I was able to register iPhoto on my mac book pro, but it is failing on my second.


thanks in advance,

-tom




User uploaded file




08:26:35.984082 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:37.417858 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46

08:26:38.032082 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:39.977873 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:42.025748 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:42.435600 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46

08:26:43.971461 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:46.019515 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:47.453197 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46

08:26:47.965198 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:49.606268 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 339

08:26:49.708805 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 348

08:26:49.811498 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 379

08:26:49.914098 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 405

08:26:50.016310 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 401

08:26:50.017171 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:50.118847 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 401

08:26:50.221214 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 393

08:26:51.958833 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:52.368490 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46

08:26:54.006909 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:55.004001 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [.], seq 187854:189302, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 1448

08:26:55.004213 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [.], seq 189302:190750, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 1448

08:26:55.004264 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [P.], seq 190750:191283, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 533

08:26:55.004415 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [P.], seq 191283:191688, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 405

08:26:55.035678 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 189302, win 4116, options [nop,nop,TS val 2280641050 ecr 1073825952], length 0

08:26:55.053470 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 190750, win 4116, options [nop,nop,TS val 2280641068 ecr 1073825952], length 0

08:26:55.060158 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 191283, win 4116, options [nop,nop,TS val 2280641074 ecr 1073825952], length 0

08:26:55.066460 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 191688, win 4116, options [nop,nop,TS val 2280641081 ecr 1073825952], length 0

08:26:55.209380 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [P.], seq 103254:103691, ack 191688, win 4116, options [nop,nop,TS val 2280641223 ecr 1073825952], length 437

08:26:55.209522 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [.], ack 103691, win 65535, options [nop,nop,TS val 1073826154 ecr 2280641223], length 0

08:26:55.952463 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35

08:26:57.386190 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46

iPhoto '11, Mac OS X (10.7.2)

Posted on Oct 17, 2011 5:33 AM

Reply
60 replies

Oct 17, 2011 11:25 PM in response to tbriggs6

I am getting the same error, and I'm only trying to activate a photostream between my iPhone 4S and my MBP. I've reset my photostream (via iCloud.com) and even turned off the photostream on my iPhone. Still getting the same error whenever I try to activate Photostream on my MBP.


The only thing I can think of is that I used to have a MobileMe account, and the MobileMe settings were still in my iPhoto "accounts" pref pane when I first tried to connect to my Photostream. I've since removed those old accounts, and deleted my iPhoto preferences. Still no luck.

Oct 18, 2011 12:07 AM in response to Daniel Richman

Three things...


1) I can activate the photostream from a pristine "Guest" account, but not my regular account.


2) If I create a new iPhoto library in my regular account, it doesn't help at all. The problem persists.


3) Not sure if this is related or not, but the folder that contains my iPhoto library is located on a separate hard drive (via a symbolic link). But, I don't think it's related to this problem. Thought I would mention that just in case.

Oct 18, 2011 2:43 PM in response to tbriggs6

User uploaded file


I too am getting the dreaded "iphoto was unable to connect to photo stream" message on my wife's iMac. Photo Stream enables fine on her iPhone, but refuses to connect on her iMac.


I've ditched all of 3ivx stuff that I've seen mentioned elsewhere yet iPhoto still will not connect. Anyone have thoughts on this weird occurence?

Oct 19, 2011 12:16 AM in response to ashiver

I have the exact same problem.


I have latest iPhoto installed. I also have 2 accounts iCloud now, former familypack MobileMe.

My original account is still a ".mac". When iPhoto makes me choose Turn on Photo Stream it shows my ".me" account, could this all affect? Do you also have more accounts on the same mac?

Should in preferences of iPhoto show the iCloud icon? I see only the basic Mail icon. I still have my original MobileMe account in the accounts list of iPhoto preferences.

I see my 2 accounts in System Preferences under the iCloud icon.

Further more, when I select in System P. the Photo Stream, it often desactivates itself later when I open the pane again...

Oct 19, 2011 11:03 AM in response to tbriggs6

Just wanted to chime in that I'm having the same issue. I have tried numerous fixes, all to no avail:


  • Logged out of MobileMe and iCloud in System Preferences, then back into iCloud only

    Various combinations of quitting and restarting iPhoto and System Preferences with all of the logging in and out

  • Deleted the MobileMe account from iPhoto under Accounts in Preferences
  • Changed my iCloud password (previous password had no capital letters and therefore didn't adhere to Apple's new policy)
  • My iPhoto library is also located on a separate drive and symbolically linked to my home directory; tried moving it back with no symbolic links
  • Created a new iPhoto library
  • Moved iPhoto and iLifePhotoStream preference files out of the way


The photo stream works just fine on the same iCloud account with:


  • My iPhone 3GS
  • Other user accounts on the same Mac - including Guest and an admin account (my normal account is not an admin account, but that doesn't appear to matter since Guest works)


So it appears to be a problem with my account on the Mac, since the same iCloud account works elsewhere. The only other thing I can think of is the fact that my unix userid is below 500 (legacy carried over from before OS X came out 10 years ago), and very occasionally, some Apple software doesn't like that.


I guess the next thing to try would be to move my entire Library folder out of the way and login with a fresh one, to see if it's something else in there that's causing the issue.

Oct 19, 2011 12:15 PM in response to Mike Heasley

Quick update: I tried moving my Library folding out of the way and logging back in. Still didn't work. Finally I moved my entire home directory out of the way and created a blank one from the default user template ("/System/Library/User Template/English.lproj"). Photo Stream worked.


So that means the problem is somewhere in my home directory, outside of the Library folder, and outside of the iPhoto library. It also means my unusual userid isn't the problem. When I get more time, I guess I'll start moving things out of the way, one by one, until I find what works.

Oct 20, 2011 5:49 AM in response to tbriggs6

I'm having the same troubles over here. I don't have 3ivx installed. When attempting to enable photostream on my iMac if fails. Checking /var/log/system.log when it is failing reveals the following:


Oct 20 23:45:38 optimus sandboxd[7258] ([7256]): PhotoStreamAgent(7256) deny file-write-create /Users/stevek/Library/Preferences/com.apple.iLifeAssetManagement.crash.plist.Dq dnrfB

Oct 20 23:45:38 optimus sandboxd[7258] ([7256]): PhotoStreamAgent(7256) deny file-write-create /Users/stevek/Library/Application Support/iLifeAssetManagement

Oct 20 23:45:47 optimus iPhoto[7207]: Timeout launching photo stream agent

Oct 20 23:45:47 optimus [0x0-0x3b13b1].com.apple.iPhoto[7207]: com.apple.photostream-agent: Already loaded

Oct 20 23:45:57 optimus iPhoto[7207]: Timeout launching photo stream agent


Permissions are all fine. It has me stumped.

Oct 20, 2011 11:16 AM in response to nifmus

Good catch, nifmus. I'm kicking myself for not checking system.log earlier! 😊 I have very similar messages in mine.


By any chance is your Library folder (or part of it) relocated to a separate disk? Or your entire home folder? I have part of my Library folder on a SSD for speed, but my home folder and some of the larger Library subdirectories are on a regular disk because they wouldn't fit on the small SSD. It's all tied together with symbolic links, and without problems... until Photo Stream came along and didn't like it.


I knew that sandboxd was involved somehow, but your post prompted me to focus on it. It's definitely the problem here. I found the following sandbox profile file inside the iPhoto application bundle:


/Applications/iPhoto.app/Contents/Library/LoginItems/PhotoStreamAgent.app/Conten ts/Resources/PhotoStreamAgent.sb


Inside this file are a bunch of definitions to control what PhotoStreamAgent is allowed to do. There are a bunch of lines under an allow-file-write* declaration which should allow PhotoStreamAgent to write to the above files listed in your log. Lines such as:


(home-regex #"/Library/Application Support/iLifeAssetManagement")

(home-regex #"/Library/Preferences/com\.apple\.iLifeAssetManagement\.crash\.plist(\.[^/]+)? $")


And many others. In my case, I suspect that the problem may be related to the fact that the final absolute path of those files may differ from what you'd get if you just substituted my home directory in for "home-regex" since I have stuff relocated around. Although since I was able to get it working with a blank home directory, also put in place via a symbolic link (so the final path differs), I'm not 100% sure of this.


What I do know right now is that there is a quick "hack" that fixed it for me. I don't like the hack and would strongly recommend against it, because it's likely to break the next time there's a software update for iPhoto. But it works until I can find a permanent solution.


To make it work, I edited the above file and changed the second line from "(deny default)" to "(allow default)". This, of course, defeats the whole purpose of the sandbox by allowing PhotoStreamAgent to do anything it wants, but it also allows stuff that is really supposed to be allowed but fails anyway for us.


If you want to try this, it helps to be familiar with the unix underpinnings of OS X. There's probably a way to do it in the normal graphical user interface, but as a longtime unix guy, I just jumped to the command line and did a "sudo vi (that long filename)". To do it via the gui method, you'll have to navigate to that folder in Finder (quickest way is to hit Cmd-Shift-G and copy/paste the path, or right-click iPhoto and "Show Package Contents", then drill down to the file), edit the file, save a copy (because you don't have permission to modify it), then copy the new version over the old (it will ask for an admin password).


Again, I don't recommend this because it's likely to break in the future and defeats the security that Apple intended with the sandbox, but it's a quick fix. I'll continue to investigate as I have time, trying to find out precisely what's causing the failure with the default sandbox profile.

Oct 20, 2011 3:36 PM in response to Mike Heasley

Mike, that's awesome. Your hack worked a treat.


And yes I have my home directory on the regular HD of my iMac and I symlink my Library folder back to the SSD for speed. I changed my home dir location via System Preferences->Accounts in the advanced section. I'm wondering if I left my Library directory on the regular HD would it work fine as there would be no symlinks involved.


Great, this is resolved and I had an inkling it would be symlink related. My next question now is, what happens after an iPhoto upgrade? I assume if theres no fix we'll have to edit this file again.


Thanks again Mike, excellent find.


Cheers,

Steve

Error enabling photo stream "iphoto was unable to connect to Photo Stream"

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.