Does anyone use FileMaker PHP on IIS with SSL. Im trying to get the FileMaker sample working on my test machine and I just get errors.

I can give you details on everypart of the configuration as it is on my test machine and not our production environment.

The test cerficate I am using is generated by the IIS 6 resource kit if anyone needs to know, but the installation itself is producing EXACTLY the same error as our real server machine.

When the Sample PHP test page tries to connect I get an error 22.... any help would be much appreciated.

Thanks

Jalz

Jalz,

Error 22 is bad credentials - either the user name or password.

Separately, if you are having trouble getting the FM PHP code to talk to your server over SSL, you may want to try setting the cURL flag CURLOPT_SSL_VERIFYPEER to false. You can do this two ways:

$fm = new FileMaker( ... );

$fm->setProperty('curlOptions', array(CURLOPT_SSL_VERIFYPEER => false));

Or, in /FileMaker/conf/filemaker-api.php you can uncomment the following line:

$__FM_CONFIG['curlOptions'] = array(CURLOPT_SSL_VERIFYPEER => false);

You can read more about CURLOPT_SSL_VERIFYPEER at php.net.

Thankyou, I have done this in the filemaker-api file in the conf folder. Im still getting the same error.

I'll post image of my settngs, does anything stand out?

If you're still getting error 22, that's a bad user name or password - that shouldn't have anything to do with your SSL connection (in fact you wouldn't be able to connect and get error 22 if SSL was getting in the way).

Recheck that the FileMaker username/password you're using is correct for your test server.

Thanks

Do you know where I can find a list of these unknown errors. Im double checking my credentials and I'll post back (I haven't altered any code for the Sample database.....)

Jalz

OK,

Just checked the FMSample database. Its only got the Admin username (Password is blank).

I have not altered any php code for the sample database, so the credentials should be the originals.

Are there some other credentials I should be looking at?

I forgot where I found what error 22 means - I think I may have put in bogus info and see what it returned.

You might want to try creating a new account with both a user name and password and try that. Also make sure that the "Access via PHP Web Publishing - FMS only (fmphp) Extended Privilege is turn -ON-. I think for [Full Access] accounts it's off by default.

Hello again.

Made sure I've got the php extension enabled on the admin account. Deliberatly changed the password details, and when I run the page it produces an error 22.

I've put the correct password in, and again it produces error 22.

Anything else you/anyone think I can try? This PHP installation is 5.2.4 (from FileMaker Server 9.0 v3) using SSL on IIS

Thanks

I'll post image of my settngs, does anything stand out?

Uncheck the basic HTTP authentication option and see what happens.

Steven

Hi Steven,

Its doesn't make a difference its still producing an error 22.

I've now removed the certificate, and the php sample file works absolutely perfectly under http.....

I'm going to install the self self cert on my using the following guides. http://geekswithblogs.net/jimiz/archive/2007/02/11/106006.aspx

Many thanks for all f you that respond, Im sure Im not the only one that wants to serve pages using SSL on IIS.

Jalz

I've been investigating this further. Its seems as though after I've installed the certificate, the Sample database works fine with HTTPS.

However, as soon as I go to properties of the default website --> Directory structure --> Edit Secure communications and apply 128 bit encryption , I get the error 22 on the test php page.

Any help much appreciated.

I am having a similar problem - except I get an error: "Notice: Undefined index: message.error.fm.60 in C:Program FilesFileMakerFileMaker ServerWeb Publishingweb-server-supporttestfmi-testphptest.php on line 36" when using the Example.fp7 database with an SSL installed. Any ideas?

Absolutely no ideas,

Im banging my head against a brick wall with this. Have you altered any php code?

Right so this is half a year old, but meh... Off the top of my head, 22 is a connectivity issue, not necessarily a username / password issue - it's a general and not all too useful error, just tell's you something is wrong.

Interested to know if you sorted that - was your connection string specifying the correct port for the connection i.e 443?

I have struck the same problem as well. PHP working fine until I assigned a certificate. Now PHP fails to authenticate, even after removing the certificate. I know enough to play with config files bu t sadly nothing seems to fix the issue. Will be rolling the server back to the way it was before the certificate was installed. Will keep you all informed about any solutions I find.

Very annoying. I guess i will have to contact filemaker support, not a happy prospect ;)

I found this bit of information in the help file included in FileMaker Server 9:

http://localhost:16000/admin-help/en/wwhelp/wwhimpl/js/html/wwhelp.htm

If you enable SSL on the web server, then you must use the Deployment assistant to configure FileMaker Server to use the HTTPS protocol to communicate with the web server. The Deployment assistant tries to detect your web server using the HTTP protocol, so if your web server uses HTTPS, the Deployment assistant fails to detect the web server and prompts you for more information. In the Deployment assistant’s Web Server Test Failed step, select HTTPS and continue. See Changing a FileMaker Server deployment.

So if you already have Web Publishing setup,

1. Open the Admin Console.

2. Select the 'Edit Server Deployment' link.

3. Keep web server turned on with SSL and have the Deployment Assistant 'try' to detect the web server. It will keep searching.

4. Stop the web server to trigger the 'cannot find web server' window.

5. Select the HTTPS radio, enter the server's IP address, and enter the https port (443).

6. Start the web server.

7. If you get errors, restart FileMaker Server.

Edited October 7, 201015 yr by Guest

This information is somewhat out of date. Please review the processes described in the Server 11 Getting Started Guide and the Configuration Guide.

Steven