iPhone DAErrorDomain error 0

Hi

I have my Traveler Server setup and running using port 443. Everything is working perfectly until I try and install the profile on the iPhone - I get the error:

An error occurred while contacting server

Error Domain=DAErrorDomain Code=0 “Operation could not be completed. (DAErrorDomain error 0.)”

I have had the same error using the beta and could correct it by entering the correct hostname in the apple.xml file on the server. I have tried to do that but it doesn’t work (I am using 443 and not 80 as previously with the beta).

Here are the steps on the iPhone (so you know where I get the error):

  1. go to traveler homepage

  2. select “configure your apple iphone/ipod touch”

  3. select “generate” on the generate apple profile (correct user is displayed)

  4. on the Install Profile page select Install

  5. Select “Install now” on the “authenticity cannot be verified” dialog (I am using a self certified key so this is correct

  6. after entering my password and OKing the “verify certificate” dialog I get the error above

I have also checked the following:

  1. dns is working correctly and I can reach the domino server (my traveler server is in the dmz and talks to the internal domino server)

  2. I can replicate to and from the traveler server

  3. cleared the cache on the iphone

  4. I have tried to update the apple.xml file - this didn’t help this time :o(

Any ideas?

Thank you in advance

Ursus Schneider

Subject: Re: iPhone DAErrorDomain error 0

Hi Guys,

I have encountered this as well when setting up a new iPhone user. I have two Domino servers with the same release versions 8.5.1 FP2 and Traveler has the same version as well.

Domino A - I setup an iPhone without any issues by just following instructions

Domino B - I setup another iPhone user but this time, I encountered the DAErrorDomain error 0 after hitting the Install button.

I googled it out and found your thread forum. I understand that this can be resolved by editing the Apple.XML file located at \traveler\cfg\client directory and replacing the:

Host ILNT_HostNameILNT_HostPath

to

key>Host yourproxy.domain.com/servlet/traveler

I just want to validate if the above modification will be correct? This makes sense to our setup because in Domino A, our homepage or IP address for the Traveler server is:

http://domain.com/servlet/traveler (using the default)

While in Domino B, it is written:

http://domain.com:8080/servlet/traveler (using 8080 for http)

So can I modify the Apple.XML and enter http://domain.com:8080/servlet/traveler…?

Please note that :8080 is established in our firewall for the this Traveler address and also, Nokia S60 phones are working very well when setup using the above homepage. It’s just the iPhone that I’ve encountered such error (DAErrorDomain error 0). Thanks in advance

Subject: RE: Re: iPhone DAErrorDomain error 0

You are still on 8.5.1, so you will need to modify the Apple.xml. Make sure NOT to include the http:// part (that is controlled by the SSL XML value below it). Just enter domain.com:8080/servlet/traveler as the Host value.

If you were on 8.5.2, you would want to leave the Apple.xml alone and specify the External Server URL on the Lotus Traveler tab in the Server document instead. That URL is needed for a few things and is used by Apple.xml to avoid people needing to modify it. But you are still on 851, so you need to modify Apple.xml.

Subject: RE: iPhone DAErrorDomain error 0

The error you are encountering is when the Apple device is trying to validate the account. To validate the account, an OPTIONS HTTP request (not GET or POST HTTP request) is made to the server. Most likely, something is blocking this OPTIONS request.

The OPTIONS request must be allowed.

If you are using an Internet Site Document, you can check the Methods to make sure OPTIONS is allowed (in addition to at least GET and POST). If you are not using Internet Site Documents on your Domino server hosting Traveler, then it is something else.

If you have a firewall (most people do), make sure the firewall allows the OPTIONS request (the body is empty, if that helps you) to get to the server.

If you want to see if the OPTIONS request is getting to the server, you can turn on the http logs (tell http debug thread on) or run a network trace.

If the OPTIONS request is getting to the server, then you might be hitting a known limitation where the Apple device does not send properly formatted credentials. See the Setup and login section of http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=/com.ibm.help.lnt851.doc/Apple_limitations_and_restrictions.html

for more details.

Subject: Maybe the problem is port rewriting?

hi

Thank you for taking the time to answer my questions :o)

The OPTIONS request must be allowed.

as far as I can tell they are - I am using Internet Site Documents and that is working perfectly

If you have a firewall (most people do), make sure the firewall allows the

OPTIONS request (the body is empty, if that helps you) to get to the server.

yes, we are using a firewall :o)

I am not sure where to check for that but I have an feeling that that is not the problem as it was working perfectly UNTIL I switched from port 81 to port 443

I checked your link and think that the problem might be that I am “switching” ports - I need to use 4430 as the port but am rewriting it using the firewall to 443 (I have 2 servers that need 443). Maybe this is the problem? I’ll try and set the SSL port to 4430 in domino and see if that helps

I’ll report back here to let you all know the outcome!

Thanks again

Ursus