Is the php sample page working?
Did you enable HSTS?
What happens when you place the files in "FileMaker Server\HTTPServer\htdocs" with http or "FileMaker Server\HTTPServer\htdocs\httpsRoot" with https?
Where can I find the php sample page ?
SSL and HSTS are disabled.
I do not have an Httpserver/htdocs folder. When I access the root folder through the url, it points on the FileMaker Server\HTTPServer\conf folder. This is the default installation I had since WebDirect 13.
If i try to access the file http://mydomain/info.php with just this line in the file <?php phpinfo(); ?>, the file is not processed. I still get the message file not found, http error 404. Now if I call the url http://mydomain/my_image.jpg, the jpg file is displayed. I put both files in the FileMaker Server\HTTPServer\conf folder. Seems to be a php configuration or web server conf.
As I could not manage to run php file within WebDirect 16, I finally installed an apache/php server beside because users where waiting...
1 of 1 people found this helpful
Have you checked the permissions on the web folder containing your PHP files? Dumb question I know but this has bitten me in the past when upgrading/migrating servers, particularly on OS X.
I had. But anyway, I can access html, jpg files but not php ones. So it seams to me that it is a configuration of php and/or IIS which has been changed between V15 and V16. Maybe it was intentional to forbid php script.
Finally I found the problem :
First of all, the new installation of course removes the custom php.ini configuration as we have to unistall FMS 15 before installing FMS 16. So the extension I added was disabled. Then the install of FMS 16 sets in the php.ini file the folders to FMS as "c:\program files\...". But in my configuration, the root folder is located on E: drive. So I had to change the "php.ini" lines 506, 509 and 535. Last thing, I had to set a timezone on line 675 (date.timezone = Europe/Paris).
I think theses paths were correctly setted up with FMS15 because It was working without any modification from my part and it was installed on E: drive since FMS 13. (I did not check, so I can't be sure but it would not have been able to work otherwise).