AnsweredAssumed Answered

Enabling SSL on FMNet connections on FMSA10 on OS X causes intermittent server failures

Question asked by PointInSpace on Apr 15, 2009
Latest reply on Apr 16, 2009 by PointInSpace

Summary

Enabling SSL on FMNet connections on FMSA10 on OS X causes intermittent server failures

Description of the issue

This is a longstanding bug that we've been seeing since at least FMSA9.  If we use secure connections on FileMaker Network Sharing connections with FMSA10 on OS X, we experience intermittent server failures.  FileMaker Product(s) involved: FileMaker Server 10 Advanced Operating System(s) involvedOS X Server 10.4Detailed description of the issue If we use secure connections on FileMaker Network Sharing connections with FMSA10 on OS X, we experience intermittent server failures.  Every couple days to multiple times a day the failures occur.  When they happen, the following occurs: - IWP connections return "Forbidden You do not have authorization to access this server." message in browser.- "FM Web Publishing    -    -    wpc1  Error: 403"  error is reported in pe_application_log.txt- XML connections return a 956 error- FileMaker Admin gui tool does not connect.- fmsadmin command line tool does continue to work- At least in 9, new FileMaker Network connections fail (not sure in 10) Exact steps to reproduce the issueEnable secure connections on FileMaker Network Sharing Expected ResultDoesn't fail Actual ResultOccasionally fails Exact text of any error message(s) that appearedSee above Any additional configuration information/troubleshooting that is relevant to the issueThis has always happened consistently on all of our FMSA9 and FMSA10 installations, requiring us to disable SSL on FMNet connections Any workarounds that you have foundRestarting server clears the problem, but then it occurs again  I have reported this bug in the past, but I never received any replies and it's never been addressed.  Obviously, it is a big deal.  I have a feeling it is related to particular database files or clients or something, as it seems to have a threshold that under a certain number of files on the server work OK.   However, it's not definite specific databases, as (as stated) we've seen this happen on numerous installations with different unique files on each.

Outcomes