Then you would have been given the opportunity to set a root password (otherwise a random one would've been generated). The root password is what you use for logging into Webmin and SSH.

If you haven't got any data in there yet then I'd just destory your current instance and start a fresh one via the Hub. If you do have data, then you may be able to find the random password by looking through the console output (from when the EC2 instance was started). Another option (if you have data in) may be to do a backup via TKLBAM and restore that to a new instance.

I have lodged a bug report.

Although I may be wrong...

Workarounds may be to manually set a root user password (which IIRC will mean that you can also login to your server with this same password - defeating the security advantages of using keys). Or I think that you can manually set (reset?) a Webmin user account apssword from the commandline. Although TBH I have never done it nor know how to... Hopefully google might turn up an answer for you...

You could try using the TurnKey archive; although you're probably better off going for upstream...

It might be best to ask your question on the Webmin forums? We possibly have a different version to what you're using and we definitely have a non-standard initial config so it might get a bit confusing, especially if you're new to it...

Perhaps it's not based on TurnKey anymore?

If they are different versions (e.g. v13.0 to v14.1) then there are probably a number of things that you will need to consider. Please have a look at this doc page. The webmin specific bits are noted under a sub-heading, however some of the other info may also be relevant.

If that is irrelevant, then I am not really sure what might be the issue. Webmin not starting because of authentication seems weird to me. You can't authenticate until it's running so it not starting because of incorrect password seems unlikely...?!

Actually I just checked on a server that I had running and when Webmin is restarted that is reporting a similar thing:

pam_unix(webmin:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=root

PS Doh, I just realised that we had already spoken recently! :)

I suggest that you start a new thread and provide the following information:

TBH, I'm not at all sure. But a wild guess is that it's a browser update that has broken things. Have you tried different web browsers? I suggest that you try different browsers (e.g. Firefox and Chrome, etc) and see if that makes any difference.

Another possibility is security updates, although I think that's much less likely as Debian Wheezy (the basis of v13.x) LTS reached EOL earlier in the year (see also Debian LTS) and is now only getting updates for a small subset of packages (and unfortunately, I'm not at all sure what packages they are).

If your server is available via the public internet, I'd strongly urge you to look at migrating or upgrading to a supported TurnKey and/or Debian version. Even if it's not publicly accessible, then you are still better off moving to a supported OS.

For historical context, IIRC, the web UI we provided for Fileserver v13.0 was "AjaXplorer". But that changed name to Pydio. We briefly looked at using Pydio for the Fileserver appliance in v14.0, but IIRC we had issues getting it installing properly in v14.0. Also, whilst the new incarnation looked pretty, it had evolved and included lots of additional bells and whistles and was a much heavier application which we thought was overkill for the Fileserver appliance. We always intended to create a standalone Pydio appliance, for users that explicitly wanted that, but have never circled back around to that. After searching for a more simple WebUI for the somewhat generic Fileserver appliance, in v14.0 (& v14.1 too IIRC) we included SambaDav, but it was a bit buggy and it's since become abandonware. So since v14.2 (inc v15.0) we've been including WebDAV-CGI.

Having said that, the history lesson is probably of limited value to you right now...

Depending on the nature of your use of the Fileserver, ownCloud or it's popular fork Nextcloud may be viable alternatives? Although they don't include Samba by default and are more like a private Dropbox type setup, with a pretty WebUI. If you use the Windows file shares of the Fileserver app, then that's probably not going to cut it for you (at least not by default - although you could also install Samba).

TBH, I think that you should really consider some significant maintenance on your fileservers. Exactly which path you take will depend on your current usage and what you need to achieve. If you'd care to share more about your current usage, I'm more than happy to share some thoughts. I'm also happy to assist as much as possible in getting you from here, to where you need to go, but obviously it'll be a "best effort" type scenario...

If you want to push ahead with that, I suggest that you start a new thread (although you may need to be a logged in user to do that?). Please feel free to cross post a link back to your post here if you want. I'll see your new post regardless, although feel free to post back here with a link to your new thread if you want.