Known Issues

Here are all the known issues with OttoFMS.

Name	Status	Description
OttoFMS Offsite File Browser does not work with s3 locations without the listAllBuckets permission	backlog
OttoFMS does not work unless using the full admin account	backlog	OttoFMS will not work if using external authentication or Local Directory accounts to log in. While these accounts work with the admin console, they do not work properly with the fmsadmin tool, which OttoFMS is using behind the scenes to run a significant portion of its functionality. Please ensure that you are logging in with the full admin account in OttoFMS. We see this issue primarily on hosting providers who provide their customers with other accounts, like Soliant Cloud.
Filenames containing non-Unicode characters cannot be deployed on Windows	backlog	The fmsadmin tool on windows is not returning non-Unicode characters in its output to OttoFMS, causing deployments of these files to fail.
Webhook Receiver doesn't have a way to do confirmations	backlog	Some webhook providers require a confirmation step before you can send webhooks. OttoFMS webhooks do not support this natively, although it can be set up using Webhook Responses. Check out the Webhooks docs for more information.