I hope this is related..if not, sorry for interrupting...
I get the white screen on a desktop FMP-FMS connection when FMS is cloud hosted.
The connection to host is lost...but it takes a while for the client to realize it...and I get the white screen (hazy white cover that you can still see through) while the client figures out that it isn't connected...then it dumps.
Are you sure your communication connection is stable? It may have naught to do with WebDirect itself...dunno.
HTH a little bit...
As mentioned, the white screen of death only happens in WebDirect. While I do suspect a form of lost connection, we are unaware if this is the case as we get no message in the web browsers like we do with FileMaker Pro clients.
Is SSL turned on?
WHat is the OS and version Of the client machine?
What is the OS and version of the server?
What is the typical user count when the WSOD appears?
What do the FMS logs show happening around the same time?
SSL is on. OS and client versions vary: Safari, Chrome or IE on Windows, Mac OS and iOS. Server OS is Windows Server 2008 R2 Standard. FMS version is 126.96.36.1992. White screen of death happens from one to ten users - no typical user count. FMS logs show normal usage (closed connections, server side scripts, backup schedules, failed authentications, that sort of thing).
I've seen similar issues with SSL certs that were related to issues with web sockets. The scenarios were a bit different, but web sockets failing were the source of many issues.
Very interesting! How do I determine if web sockets are failing? Is this a client-side or server-side issue?
I thank you all for your comments. Here are the conclusions of this investigation: users misreported the white screen of death issue as there is a spinning wheel; waiting often resolves the issue; this is a common issue in the FileMaker community; there is little we can do to resolve this issue from a hardware, software or network perspective; the solution contains code that increases the likelyhood that the spinning wheel appears. We now know what to tell our users and what to do to reduce the occurence of this issue going forward.