Mysterious credential failure

[darthfodio 0]

I configured an Emby server on a new instance of Ubuntu a few fours ago. I used WinSCP to upload content to the newly setup Emby server. Since the file was pretty large, I allowed the upload to work in the background while I did other things. After 45 minutes or so I check and realized that the upload stopped due to connectivity to the Emby server. I went back to the server and attempted to login (I saved my credentials saved and confirmed they worked several times prior) and now I get Invalid username and password. I haven't made any changes as I left the upload as it was. I tried to change the password, however nothing happens when I enter my username and click the submit button. I have tested in different browsers and get the same result. I'm trying to figure out why/how my credentials are failing. Can anyone assist me with this issue?

[Q-Droid 989]

Check your filesystems on the Emby server to see if any filled up during the copy.

[Luke 42078]

If your drive is out of disk space, then that could cause problems with your emby server database files. Please let us know if this helps. Thanks.

[darthfodio 0]

Thanks for your responses. You were both correct about the disk space. So is it safe to assume the disk space availability of my server will dictate whether or not the Emby server will work?

[Happy2Play 9780]

2 minutes ago, darthfodio said:

Thanks for your responses. You were both correct about the disk space. So is it safe to assume the disk space availability of my server will dictate whether or not the Emby server will work?

To a point yes, as you need space for the database, cache, metadata, transcode-temp and logs (3 days are maintained) to grow.  You can customize paths for cache, transcode-temp, and metadata.

Good example is my \metadata\people folder is 62Gb.  And depending on whether you save images and bif interval images with media or central can affect the \metadata folder also.

Transcoding-Temp will maintain and entire session and should be cleaned up once the session is stop, so you need to ensure you have the space for your total number of playback sessions that need transcoding and or remuxing.