Search the Community

I seem to be having a weird issue with issuing API keys after a fresh install of 3.5.2.0. It seems that API keys are somehow not persistent and are only valid for one-time use. After creating an API key, I am able to successfully use it once, but if I try again it fails and the API key had disappeared from the API key list immediately after the first successful use. For some context: I'm in the process of upgrading from Warden jail plugins to iocage jails. Everything seems to be running as normal and I am just trying to connect Sonarr and a custom written web interface that use API keys. I'm currently on FreeNAS 11.2-STABLE train with a fresh 11.2-Release FreeBSD iocage jail, with Emby installed with the new FreeBSD pkg. I don't see a reason for it to be a FreeNAS/FreeBSD issue so I am posting on General topics. On my previous Warden Plugin Jail, originally created on FreeNAS train 9.10.2-U4 and running 3.4.1.0, in the context of API keys, worked perfectly fine and normal. After the fresh install of 3.5.2.0, I did do a restore of users, settings, etc. from 3.4.1.0 with the Emby backup & restore plugin. Attached is my log. Last thing I did was create an API key and use it for one http post and now it no longer shows on the API list. The http post was done through my web interface, I attempted to login via AuthenticationByName with user Guest and was successful. Log.txt