[FX.php List] Can't connect with manually installed php on Windows 2008 Server

[Chris Hansen]

Hi Jonathan,

Given the version of FileMaker, I'm not sure that it's a known issue (FMS 13 is where things really seem to have gotten messy if you don't like FM's built in web server.)  That said, I know that FMS has its own custom version of Tomcat running under the hood, and it does a lot of talking to itself on various ports.  (Peter Wagemans of SHpartners has more knowledge of that than anyone I know outside of FileMaker, though he may have moved on to other areas these days.)

The cURL issue could be any number of things, though log entries should give you a hint.  For that matter, exactly what cURL error are you seeing?

All that said, there's a fair amount of voodoo going on under the hood, and I don't think that trying to make FileMaker dance to a tune other than what it wants is going to make either it or you very happy...  And what happens when you have to upgrade something?  More of what you're going through now?  I shudder to think.  I'd agree with what's already been said: put FileMaker on its own machine.  It's really a better idea to have a database server living behind the web server anyway.

Best,

--Chris

On Jul 21, 2014, at 7:37 PM, jschwartz <jschwartz at exit445.com> wrote:

> Hi Joel,
> 
> Long time.
> 
> 
> Answer is….
> 
> One Machine.
> 
> I suppose that I could ask them to spin up a separate virtual IIS web server, but why?  I haven’t been paying attention.  Is this a “known issue”?
> 
> Jonathan
> 
> 
> On Jul 21, 2014, at 6:33 PM, Joel Shapiro <mail at jsfmp.com> wrote:
> 
>> Hey Jonathan
>> 
>> Is this a one- or two- machine config?
>> 
>> Could you, as people here have been commenting, have a vanilla web server on its own machine, and have all FMS components -- including the WPE -- on the non-PHP Database server?
>> 
>> -Joel
>> 
>> 
>> On Jul 21, 2014, at 5:18 PM, jschwartz <jschwartz at exit445.com> wrote:
>> 
>>> Hi Folks,
>>> 
>>> I had a perfectly fine fx.php system working under OS X 10.6.8, but the system would not pass a PCI security scan, so I agreed to move it to Windows 2008. Another guy is handling the Windows side. When I first installed the system under FMS 11, all was good the Web Publishing side.  The Windows guy had to continue plugging security holes to pass the PCI scan.  His last step was to replace PHP because the PCI scan complained about the embedded PHP version inside FMS 11.
>>> 
>>> That’s when fx.php stopped talking to FileMaker.  I got the cURL error, although password and connect info was correct..  I redeployed the Web Publishing Engine…twice. Each time, the deploy whacked IIS to the point that IIS stopped recognizing php files.
>>> 
>>> The Windows gut isn’t too happy.  We’re both wasting a huge amount for time just to to placate the credit card guys.
>>> 
>>> Are there any secrets I should know?
>>> 
>>> Thanks
>>> 
>>> Jonathan_______________________________________________
>>> FX.php_List mailing list
>>> FX.php_List at mail.iviking.org
>>> http://www.iviking.org/mailman/listinfo/fx.php_list
>> 
>> _______________________________________________
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
> 
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>