All but 1 or our servers are not accessible anymore

All of our servers are showing disconnected ( except 1 that is an older PC running FMSv19.3.1 All other server running newer versions, are no longer connected ( there is a plug icon with a slash thru it. Clicking them and then clicking reconnect server / Refresh Connection gives an “Connection Error 401” / We can however login to the Claris FMS console, but NOT the OttoFMS Console ( it just sits at the login screen after imputing the login. ( well unless you put in the wrong login, then it shows an error, but with the correct info. just does nothing after sign in )) / all of them have OttoFMS Version 4.11.0 but are in different data centers and locations with various version of FMS ( 19.6.3 / 21.0.2 / 20.3.4 ) So I can’t see that this is an issue with any firewalls or configuration.

Hello,

Are these Ottomatic servers or your own servers?

If they are your own, is the FileMaker license or your ssl cert expired?

Todd

All the servers are OUR own servers or client owned servers that we manage. They are at multiple data centers or on-site at client, all are fully licensed with current SSL certs. All of them WERE working but now, all but one ( the oldest PC server ) wont re-connect ( most of the servers are Macs ) / I tried deleting one, and re-adding it, but then get stuck at the API key step. ( If I select to make it, it fails, and when I click get one from OttoFMS, the login comes up, but then just sits there after the proper login is entered. ( does not continue in to the interface like it used to do )

Did y’all recently change the admin credentials for the server or something similar?

-Kyle

No admin credentials were changed on any of the servers. Again, they were all working before and they are at different locations. I even tried logging in from a virgin computer to the OTTO manager while at a client, to make sure it wasn’t something to do with my office internet or computers. Even tried removing and re-adding, but then get stuck at the API Key step. ( we are talking about 8 different servers at different locations with different OS & FMS versions, they don’t have much in common and the only recent change was installing OTTO ). I am perplexed why OTTO would all suddenly stop working on all but a single, Windows server ( ie: the oldest server we manage )… We do love this product, so I am very bummed it stopped working…

If you uninstall OttoFMS and install the new version does it work?

-Kyle

hum, uninstall? I thought that automatically does that… I just went to one of the Mac servers, and opened terminal and pasted… “sudo curl -sSL “https://downloads.ottomatic.cloud/ottofms/install-scripts/install-mac.sh” | bash” / it goes thru the process, and I see that it says it is “uninstalling” and installing… Is that what you mean, or is there another process?

Yes, that script automatically does the uninstall.

Just did it on another server ( FMSv20 Otto 4.12), all of them do the same thing… Like when I click the button to go make a Key with OTTOFMS, the login dialog comes up, but when I login, it just sits at the login screen… ( if I use the wrong password, it tells me that the credentials are wrong in red, text… but if I put in the Correct info. it just does nothing… ). I could send videos of what I am experiencing to ??

I believe you, If you go to the network tab on your browser console (right click, inspect, network), what happens when you click that button? I suspect what you’re seeing is that it does one call which succeeds and then makes a call to something something /verifySession which fails. Is that what happens?

-Kyle

If you want to work through it with us feel free to sign up for Office Hours as well: Support | OttoFMS
-Kyle

Info / login / getStatus - white… verifySesson goes red { “error”: “Too many admin sessions, redirecting to login” }

Hi, sorry if I jump into the conversation — this happened to me a few months ago.
My scenario was all Mac servers, and the issue came from upgrading FileMaker Server without first uninstalling the previous version using the dedicated uninstaller. Some old files weren’t removed properly, which caused conflicts with newer components (probably permissions).

Also, older versions of OpenJDK (before 17.0.10) created problems with OttoFMS, but that was fixed with OttoFMS version 4.11.1.

What worked for me on Mac Server:

  1. Make a copy of your Database folder.
  2. Uninstall FileMaker Server completely using the dedicated uninstaller.
  3. Restart.
  4. Reinstall FileMaker Server from scratch.
  5. Reinstall the SSL certificate.
  6. Restart again.
  7. Copy your databases back into the dedicated folder.
  8. Propagate the main HD privileges and make sure fmserver has access on external hard drives. Re-propagate privileges if needed.
  9. Uninstall OttoFMS.
  10. Restart.
  11. Install OttoFMS from the dedicated installer or via terminal (now everything is clean).
  12. Check Disk Access to ensure the Otto extension is active. If you’re on Apple Silicon, verify that the correct binary (ottofms-macos-arm64) is active, and disable the x64 one if necessary.
  13. Restart again.
  14. Verify privileges — especially for external drives. If you see a spinning wheel next to the fmserver, delete and re-add the user, then re-propagate privileges on the external drive.
  15. Final restart.

At this point, everything should run smoothly!

My configuration (for reference):

  • Mac with Apple Silicon
  • macOS Sequoia 15.7
  • FileMaker Server 22.0.2.204
  • OpenJDK 17.0.13
  • OttoFMS 4.12

:warning: Tip: Sometimes Safari (privacy settings) causes issues when connecting to localhost/otto/. Use a Private Window or Google Chrome instead.

:point_right: If you’re on Windows, try adapting these steps — or better, ask Tood !

In any case, it takes some time, but it worked for me!

Hope this Help !

Ciao

OK, thanks for the specific instructions, I will give it a shot on one of the servers. FYI: Yes, they are all Mac Servers, with various OS and FMS version, at different locations and datacenters. Without any recent changes, they all dropped off OTTO, so I was thinking it had something to do with OTTO storage of my API keys, not my servers. But I will give this a shot anyway… Thanks Again…

What is the company that provide you the hosting your Mac Server ? Thank You