I’ve changed the FileMaker server password using the admin console. Now I can no longer log into OttoFMS dashboard. This persists after a complete restart of the server.
Otto v3 is also installed on the server and I can log into that without a problem.
Please help.
Hello Tobias,
Have you tried clearing your cookies on the OttoFMS console? I’d also recommend clearing your cache.
If that doesn’t work, do you see any errors in your browser console? You can look at these by right clicking anywhere on the screen in clicking “Inspect element” or something similar. Then just navigate to the Console tab to see any errors that may have happened.
Thank you!
-Kyle
I also had a situation where I was able to login to the FileMaker admin console with credentials, but doing the same from the OttoFMS login screen said username and password incorrect. The only solution I could find was to uninstall OttoFMS and re-install. Sorry I don’t have any screenshots or logs to contribute.
I also had Otto v3 install as well, so that may have been a factor.
It is also possible that you may have run out of admin api sessions attempting to validate the new username/password. You could try restarted the admin server from the command line, that should clear your sessions and let you try again
That’s an interesting possibility. I’m not able to recreate it again at the moment, but I did try doing a full server restart at the time and I still got the same issue.
When OttoFMS tries to login does the response from FMS provide any more information other than auth un-successful? If so it may be possible to provide a more detailed error to the user.
As I said I restarted the complete server. Still cannot log in. AdminAPI works fine.
I think I have to reinstall otto. That is really a bummer bug.
Sorry you’re hitting this issue Tobias! I’ll be testing it on my side and putting together a fix.
Hey Tobias,
I’ve tracked down the source of the issue. We are currently attempting to log out with your old admin api token before we log in with the new one. Unfortunately, this doesn’t work if the old token no longer exists and it fires an error that says your username and password are invalid.
I do have a fix put together for this that will be going out in a coming version, I’ll keep you updated on its progress.
Your options for fixing this are to either wait for the fix (should be sometime in the next couple of days, hopefully sooner) or to delete your OttoFMS database and restart OttoFMS. You can delete the database by deleting the db.sqlite file in your OttoFMS/data folder in the applications folder (opt on Linux, Program Files on Windows, Applications on Mac). Thanks for reporting this!
-Kyle
An easier way you could work around this is by changing your password back to your previous password, logging into the OttoFMS console, changing your password again, and immediately logging into OttoFMS. The admin session with your old password will still exist so we can update your credentials without hitting an error. That’s probably the easiest way to do this and you won’t lose your existing deployments and other information.
It looks like the fix will be coming out later this week or early next week (our timelines are slowed down a big since half of the team is at Engage). Thanks again!
-Kyle
Thanks for the fast turnaround. I will wait for the fix as this is a non critical system.
This fix was included in version 4.1.0!
-Kyle
Hi guys, i have an issue close to this one, i am not sure if i should open a separate ticket.
My OttoFMS Version: 4.3.5
My FileMaker Server Version: 20.3.3 205(01-24-2024)
My Server Version: Ubuntu 20.04.5 LTS (GNU/Linux 5.4.0-182-generic x86_64)
We have un-installed the previous version of Otto (Version 3.6.2) and used the link provided in the Installation Guide ( sudo curl -sSL “https://appupdates.proofgeist.com/ottofms/install-scripts/install-linux.sh” | bash ) to install the new version of OttoFMS.
Everything went fine, OttoFMS got installed and we can open the Home page where we can enter our FileMaker Server Admin Console credentials.
However, when we do that, we can not log into the OttoFMSW console (screenshot attached).
• The username and password are 100% correct and we can login to the FileMaker Server with the same credentials.
• I cleared the cache and cookies on my browser.
• we have restarted the server and re-installed OttoFMS several times.
• The SSL certificate is valid.
• There is enough room on the disk.
Why could this be?
Hello,
We welcome to the community 
If you certain you are using the correct password, there is a possibility that OttoFMS can’t handle your specific password, if it has some special characters in it. They should be escaped properly but it’s possible something got missed.
You could test this easily by changing the password using the the Admin Console to something simple, and then try to log in with OttoFMS.
You could also try escaping any special characters in the password with a backslash. For example. If your password was fir$t. you could try fir\$t.
Let us know if you find a character that isn’t escaped properly so we can make sure it is handled in future versions.
Other possibilities are that FileMaker server is not running properly. In particular the Admin Server might be unresponsive. You can could try restarting the Admin Server with fmsadmin restart adminserver on the command line.
Let us know what you discover.
Thank you
Todd
Thank you Todd,
yes, it works with the dum password, so it is about the special characters. We had #,~,:,%,? and . We will put escape on these and try if that works as the management would not accept passwords without special characters. I will report back how it worked.
THE OUTCOME: We managed to work around the issue in the way that Todd suggested - we changed the passwords on the FileMaker Server Admin Console and OttoFMS console placing the escape "" forward slach before the each special character like the following (this is not our real password of course): yUiBGhjk25ft$GtrwSHVPfdAs8HjkyUi#QU7Vc2dFgh7Ijuyet5HjkUyte0tfGhjTY. The escape forward slash can not be seen here but it is there before the $ and the #.
And it worked , hurray.
Thanks for the update! We’ll see if we can build that in for you.
-Kyle
