Error 500 when viewing FileMaker Server

I read thru this thread, not seeing an answer… Here’s my experience …
Short:
The manager screen comes up for a few seconds, then a 500 error shows
“undefined is not an object (evaluating ‘i.messages[0]’)”

Long:
Installation went smooth, other than I had to manually go and add
the full disk access in the security panel per instructions ( bin folder )

I was able to insert the reg code and login, and the interface comes up.
HOWEVER, after a few seconds, I get an 500 ERROR
“undefined is not an object (evaluating ‘i.messages[0]’)”

If I click the refresh button, and immediately go between lets say,
“File Browser” and “logs”, it DOES stay connected, but clicking
a side tab like Dashboard or FMServer, shows for a few
seconds, but then results with the 500 error

Checked all the settings per the install instructions
and searched the community for that error, now
posting this, what am I missing?


ie: Both servers are doing the same thing.
Production Server
Mac Mini M2 24GB / Sonoma 14.5
FileMaker Server 21.1.1.40

Dev Server
Mac Mini M2 16GB / Ventura 13.2.1
FileMaker Server 19.6.3.302

yes, I did these
sudo launchctl bootout system /Library/LaunchDaemons/com.proofgeist.ottofms.plist
sudo launchctl bootstrap system /Library/LaunchDaemons/com.proofgeist.ottofms.plist

and also tried restarting from the setting panel in the interface & restarting the dev server.
( seems just the panels - Dashboard and FileMaker Server tabs get errors after 5 sec. )

Same results from multiple machines and browsers ( Safari & Chrome )

Hello

Welcome to the community :slight_smile:

Did you by any chance just install OttoFMS 4.11.0 using the downloadable installer?

One other note. FileMaker Server 19.6.3.302 is no longer supported.

Todd

Tried again today with different servers, and I used this link ( on TWO - MacMini M1 servers ) = sudo curl -sSL “https://downloads.ottomatic.cloud/ottofms/install-scripts/install-mac.sh” | bash
The on-prem server is working and I was able to add it to OTTO Console ( generating a key automatically, like you showed on RCC today. BUT the dev server, which is a near exact duplicate, Has the issue with the 500 error and also FAILS went trying to add to the OTTO Console ie: when generating a key. So it seems there must be something with the routing at my DataCenter, because all the servers in the rack have the same dropping connection issue (after about 5 seconds when going to tabs like Dashboard), no matter what the OS or FMS versions are. ie: so this doesn’t necessarily seem to be an OTTO problem. ( but any guidance to remedy would be greatly appreciated ) ie: 500 ERROR
“undefined is not an object (evaluating ‘i.messages[0]’)”

Hello,

Look in the OttoFMS /logs folder. What do you see in the otto-info.log? Any error messages?

Todd

here’s an excerpt from the info. log

2025-06-05T00:28:12.896Z error Error calling admin api proxy: certificate has expired
2025-06-05T00:28:13.891Z error Error calling admin api proxy: certificate has expired
2025-06-05T05:08:15.625Z info web app login successful
2025-06-05T05:08:17.121Z error Error calling admin api proxy: certificate has expired
2025-06-05T05:08:18.483Z error Error calling admin api proxy: certificate has expired
2025-06-05T05:08:20.805Z error Error calling admin api proxy: certificate has expired
2025-06-05T05:08:25.279Z error Error calling admin api proxy: certificate has expired

It looks like your cert has expired. That would do it, if it is.

Todd