NSURLErrorDomain : Messages has stopped sending photos

I can no longer receive or send imessage photos within Yosemite Messages App. Standard txt messages work fine but Photo's do not. I recieve the following error when sending our receiving photos in the File Transfer window :


NSURLSession error: The operation couldn't be completed (NSURLErrorDomain error - 1202.) ((null))


I've tried logging in and out of my iMessage account. Has not fixed anything.


Anyone know how to fix this?

Mac Pro, OS X Yosemite (10.10.1)

Posted on Dec 11, 2014 3:17 PM

Reply
14 replies

Dec 11, 2014 6:06 PM in response to paul.foley

Please read this whole message before doing anything.

This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

Step 1

The purpose of this step is to determine whether the problem is localized to your user account.

Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

Test while logged in as Guest. Same problem?

After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

Step 2

The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

Please take this step regardless of the results of Step 1.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

Dec 11, 2014 10:00 PM in response to paul.foley

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

The title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar at the top of the screen. Click the Clear Display icon in the toolbar. Then try to send an attachment. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Dec 12, 2014 11:48 AM in response to Linc Davis

Thanks for you help here is the log:


12/12/14 11:46:40.199 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

12/12/14 11:46:40.249 AM com.apple.photostream-agent[1185]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9813)

12/12/14 11:46:40.250 AM com.apple.photostream-agent[1185]: <MSASStateMachine: 0x7ffa31f310e0>: Failed to retrieve server-side configuration. Error: NSURLError:

Domain : NSURLErrorDomain

Code : -1202

Desc : The certificate for this server is invalid. You might be connecting to a server that is pretending to be “p03-sharedstreams.icloud.com” which could put your confidential information at risk.

Sugg : Would you like to connect to the server anyway?

UserInfo: {

NSErrorClientCertificateStateKey = 0;

NSErrorFailingURLKey = "https://p03-sharedstreams.icloud.com:443/190395914/sharedstreams/configuration";

NSErrorFailingURLStringKey = "https://p03-sharedstreams.icloud.com:443/190395914/sharedstreams/configuration";

NSErrorPeerCertificateChainKey = (

"<SecCertificate 0x7ffa31c6ab30 [0x7fff7cbbecf0]>",

"<SecCertificate 0x7ffa31c8f860 [0x7fff7cbbecf0]>",

"<SecCertificate 0x7ffa31c50500 [0x7fff7cbbecf0]>"

);

NSLocalizedDescription = "The certificate for this server is invalid. You might be connecting to a server that is pretending to be \U201cp03-sharedstreams.icloud.com\U201d which could put your confidential information at risk.";

NSLocalizedRecoverySuggestion = "Would you like to connect to the server anyway?";

NSURLErrorFailingURLPeerTrustErrorKey = "<SecTrust 0x7ffa31c422a0 [0x7fff7cbbecf0]>";

NSUnderlyingError = "Error Domain=kCFErrorDomainCFNetwork Code=-1202 \"The certificate for this server is invalid. You might be connecting to a server that is pretending to be \U201cp03-sharedstreams.icloud.com\U201d which could put your confidential information at risk.\" UserInfo=0x7ffa32340f20 {NSErrorFailingURLStringKey=https://p03-sharedstreams.icloud.com:443/190395914/sharedstreams/configuration, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFNetworkCFStreamSSLErrorOriginalValue=-9813, kCFStreamPropertySSLPeerCertificates=(\n \"<SecCertificate 0x7ffa31c6ab30 [0x7fff7cbbecf0]>\",\n \"<SecCertificate 0x7ffa31c8f860 [0x7fff7cbbecf0]>\",\n \"<SecCertificate 0x7ffa31c50500 [0x7fff7cbbecf0]>\"\n), _kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrust 0x7ffa31c422a0 [0x7fff7cbbecf0]>, NSLocalizedDescription=The certificate for this server is invalid. You might be connecting to a server that is pretending to be \U201cp03-sharedstreams.icloud.com\U201d which could put your confidential information at risk., _kCFStreamErrorDomainKey=3, NSErrorFailingURLKey=https://p03-sharedstreams.icloud.com:443/190395914/sharedstreams/configuration, _kCFStreamErrorCodeKey=-9813}";

"_kCFStreamErrorCodeKey" = "-9813";

"_kCFStreamErrorDomainKey" = 3;

}

...Underlying error:

__NSCFError:

Domain : kCFErrorDomainCFNetwork

Code : -1202

Desc : The certificate for this server is invalid. You might be connecting to a server that is pretending to be “p03-sharedstreams.icloud.com” which could put your confidential information at risk.

Sugg : Would you like to connect to the server anyway?

UserInfo: {

NSErrorFailingURLKey = "https://p03-sharedstreams.icloud.com:443/190395914/sharedstreams/configuration";

NSErrorFailingURLStringKey = "https://p03-sharedstreams.icloud.com:443/190395914/sharedstreams/configuration";

NSLocalizedDescription = "The certificate for this server is invalid. You might be connecting to a server that is pretending to be \U201cp03-sharedstreams.icloud.com\U201d which could put your confidential information at risk.";

NSLocalizedRecoverySuggestion = "Would you like to connect to the server anyway?";

"_kCFNetworkCFStreamSSLErrorOriginalValue" = "-9813";

"_kCFStreamErrorCodeKey" = "-9813";

"_kCFStreamErrorDomainKey" = 3;

"_kCFStreamPropertySSLClientCertificateState" = 0;

kCFStreamPropertySSLPeerCertificates = (

"<SecCertificate 0x7ffa31c6ab30 [0x7fff7cbbecf0]>",

"<SecCertificate 0x7ffa31c8f860 [0x7fff7cbbecf0]>",

"<SecCertificate 0x7ffa31c50500 [0x7fff7cbbecf0]>"

);

kCFStreamPropertySSLPeerTrust = "<SecTrust 0x7ffa31c422a0 [0x7fff7cbbecf0]>";

}

12/12/14 11:46:40.326 AM logind[72]: -[SessionManager getClient:withRole:inAuditSession:]:241: ERROR: No session dictionary for audit session 100064

12/12/14 11:46:40.326 AM logind[72]: _SMGetSessionAgent:73: ERROR: __SMGetClientForAuditSessionAgent failed 2

12/12/14 11:46:40.326 AM IMRemoteURLConnectionAgent[4769]: SACShieldWindowShowing:925: ERROR: NULL response

12/12/14 11:46:40.328 AM com.apple.SecurityServer[57]: Session 100063 created

12/12/14 11:46:40.372 AM IMTransferAgent[4768]: [Warning] TRUST validation failed with result 5

12/12/14 11:46:40.372 AM IMTransferAgent[4768]: [Warning] IDSiMessageServerBag: URL bag data invalid (not valid)

12/12/14 11:46:40.849 AM IMTransferAgent[4768]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9813)

12/12/14 11:46:41.141 AM IMTransferAgent[4768]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9813)

12/12/14 11:46:46.902 AM IMTransferAgent[4768]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9813)

12/12/14 11:46:52.660 AM IMTransferAgent[4768]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9813)

Dec 12, 2014 12:42 PM in response to paul.foley

I'm getting similar errors when iphoto tries to sync photo's from icloud:


12/12/14 12:40:42.966 PM com.apple.photostream-agent[5082]: MMCS reported an error: __NSCFError:

Domain : com.apple.mmcs

Code : 38

Desc : NSURLSession error: The operation couldn’t be completed. (NSURLErrorDomain error -1202.) ((null))

UserInfo: {

NSDescription = "NSURLSession error: The operation couldn\U2019t be completed. (NSURLErrorDomain error -1202.) ((null))";

NSLocalizedDescription = "NSURLSession error: The operation couldn\U2019t be completed. (NSURLErrorDomain error -1202.) ((null))";

NSUnderlyingError = "Error Domain=NSURLErrorDomain Code=-1202 \"The operation couldn\U2019t be completed. (NSURLErrorDomain error -1202.)\" UserInfo=0x7fe20b629020 {NSURLErrorFailingURLPeerTrustErrorKey=<SecTrust 0x7fe20b719080 [0x7fff7cbbecf0]>, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9813, NSUnderlyingError=0x7fe20b718a40 \"The operation couldn\U2019t be completed. (kCFErrorDomainCFNetwork error -1202.)\", NSErrorPeerCertificateChainKey=(\n \"<SecCertificate 0x7fe20b71d6c0 [0x7fff7cbbecf0]>\",\n \"<SecCertificate 0x7fe20b71efc0 [0x7fff7cbbecf0]>\",\n \"<SecCertificate 0x7fe20b71f200 [0x7fff7cbbecf0]>\"\n), NSErrorFailingURLKey=https://p03-content.icloud.com:443/190395914/authorizeGet, NSErrorFailingURLStringKey=https://p03-content.icloud.com:443/190395914/authorizeGet, NSErrorClientCertificateStateKey=0}";

}

...Underlying error:

NSURLError:

Domain : NSURLErrorDomain

Code : -1202

Desc : The operation couldn’t be completed. (NSURLErrorDomain error -1202.)

UserInfo: {

NSErrorClientCertificateStateKey = 0;

NSErrorFailingURLKey = "https://p03-content.icloud.com:443/190395914/authorizeGet";

NSErrorFailingURLStringKey = "https://p03-content.icloud.com:443/190395914/authorizeGet";

NSErrorPeerCertificateChainKey = (

"<SecCertificate 0x7fe20b71d6c0 [0x7fff7cbbecf0]>",

"<SecCertificate 0x7fe20b71efc0 [0x7fff7cbbecf0]>",

"<SecCertificate 0x7fe20b71f200 [0x7fff7cbbecf0]>"

);

NSURLErrorFailingURLPeerTrustErrorKey = "<SecTrust 0x7fe20b719080 [0x7fff7cbbecf0]>";

NSUnderlyingError = "Error Domain=kCFErrorDomainCFNetwork Code=-1202 \"The operation couldn\U2019t be completed. (kCFErrorDomainCFNetwork error -1202.)\" UserInfo=0x7fe20b610c80 {_kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrust 0x7fe20b719080 [0x7fff7cbbecf0]>, _kCFNetworkCFStreamSSLErrorOriginalValue=-9813, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9813, kCFStreamPropertySSLPeerCertificates=(\n \"<SecCertificate 0x7fe20b71d6c0 [0x7fff7cbbecf0]>\",\n \"<SecCertificate 0x7fe20b71efc0 [0x7fff7cbbecf0]>\",\n \"<SecCertificate 0x7fe20b71f200 [0x7fff7cbbecf0]>\"\n)}";

"_kCFStreamErrorCodeKey" = "-9813";

"_kCFStreamErrorDomainKey" = 3;

}

...Underlying error:

NSError:

Domain : kCFErrorDomainCFNetwork

Code : -1202

Desc : The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -1202.)

UserInfo: {

"_kCFNetworkCFStreamSSLErrorOriginalValue" = "-9813";

"_kCFStreamErrorCodeKey" = "-9813";

"_kCFStreamErrorDomainKey" = 3;

"_kCFStreamPropertySSLClientCertificateState" = 0;

kCFStreamPropertySSLPeerCertificates = (

"<SecCertificate 0x7fe20b71d6c0 [0x7fff7cbbecf0]>",

"<SecCertificate 0x7fe20b71efc0 [0x7fff7cbbecf0]>",

"<SecCertificate 0x7fe20b71f200 [0x7fff7cbbecf0]>"

);

kCFStreamPropertySSLPeerTrust = "<SecTrust 0x7fe20b719080 [0x7fff7cbbecf0]>";

}

Dec 12, 2014 1:40 PM in response to paul.foley

This could be a complicated problem to solve, as there are several possible causes for it.

Back up all data, then take each of the following steps that you haven't already taken. Stop when the problem is resolved.

Step 1

From the menu bar, select

 ▹ System Preferences... ▹ Date & Time

Select the Time Zone tab in the preference pane that opens and check that the time zone matches your location. Then select the Date & Time tab. Check that the data and time shown (including the year) are correct, and correct them if not.

Check the box marked

Set date and time automatically

if it's not already checked, and select one of the Apple time servers from the menu next to it.

Step 2

Triple-click anywhere in the line below on this page to select it:

/System/Library/Keychains/SystemCACertificates.keychain

Right-click or control-click the highlighted line and select

Services Show Info

from the contextual menu.* An Info dialog should open. The dialog should show "You can only read" in the Sharing & Permissions section.

Repeat with this line:

/System/Library/Keychains/SystemRootCertificates.keychain

If instead of the Info dialog, you get a message that either file can't be found, reinstall OS X.

*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. Open a TextEdit window and paste into it by pressing command-V. Select the line you just pasted and continue as above.

Step 3

Launch the Keychain Access application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad. Click Utilities, then Keychain Access in the icon grid.

In the upper left corner of the window, you should see a list headed Keychains. If not, click the button in the lower left corner that looks like a triangle inside a square.

In the Keychains list, there should be items named System and System Roots. If not, select

File Add Keychain

from the menu bar and add the following items:

/Library/Keychains/System.keychain

/System/Library/Keychains/SystemRootCertificates.keychain

Open the View menu in the menu bar. If one of the items in the menu is

Show Expired Certificates

select it. Otherwise it will show

Hide Expired Certificates

which is what you want.

From the Category list in the lower left corner of the window, select Certificates. Look carefully at the list of certificates in the right side of the window. If any of them has a blue-and-white plus sign or a red "X" in the icon, double-click it. An inspection window will open. Click the disclosure triangle labeled Trust to disclose the trust settings for the certificate. From the menu labeled

Secure Sockets Layer (SSL)

select

no value specified

Close the inspection window. You'll be prompted for your administrator password to update the settings.

Now open the same inspection window again, and select

When using this certificate: Use System Defaults

Save the change in the same way as before.

Revert all the certificates with non-default trust settings. Never again change any of those settings.

Step 4

Select My Certificates from the Category list. From the list of certificates shown, delete any that are marked with a red X as expired or invalid.

Export all remaining certificates, delete them from the keychain, and reimport. For instructions, select

Help Keychain Access Help

from the menu bar and search for the term "export" in the help window. Export each certificate as an individual file; don't combine them into one big file.

Step 5

From the menu bar, select

Keychain Access Preferences... Certificates

There are three menus in the window. Change the selection in the top two to Best attempt, and in the bottom one to CRL.

Step 6

Triple-click anywhere in the line of text below on this page to select it:

/var/db/crls

Copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select

Go Go to Folder...

from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.

A folder named "crls" should open. Move all the files in that folder to the Trash. You’ll be prompted for your administrator login password.

Restart the computer, empty the Trash, and test.

Step 7

Triple-click anywhere in the line below on this page to select it:

open -e /etc/hosts

Copy the selected text to the Clipboard by pressing the key combination command-C.

Launch the built-in Terminal application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.

Paste into the Terminal window by pressing command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting. A TextEdit window should open. At the top of the window, you should see this:

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost

If that's not what you see, post the contents of the window.

Dec 12, 2014 2:42 PM in response to Linc Davis

None these things solved my problem...


Step 1 : Yes time was set to automatic already.


Step 2 : Read only was on both files for “Everyone”


Step 3 : Is a bit confusing as you do not mention the category but not the keychain that I should be looking in. In any case I did not find anything with red”X” or blue and white plus sign.


Step 4 : I deleted and re-imported my certificates.


Step 5 : I changed bottom setting to CRL


Step 6 : i deleted the files and rebooted.


Step 7 : I had already checked my hosts file its fine.


Other things I have already tried include re-installing OSX Yosemite and Repairing Permissions and Disk.

Dec 15, 2014 9:09 AM in response to Linc Davis

Ok so, Keychain Access > Repair Keychain did not fix anything. However I did get it to work finally!!.. Heres what i did. I did a search with the keychain access tool under certificates and system roots for "apple" I first exported all the certificates found and then deleted every certificate that came up in the search results. Immediately i was able to log back into iCloud and send photo's with messages again!


There are a lot of people on these discussions with the same problem as I and never found a solution. Hopefully this helps someone else!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

NSURLErrorDomain : Messages has stopped sending photos

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