Please feel free to cross post a link back to your post here if you want. 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?). 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'd care to share more about your current usage, I'm more than happy to share some thoughts. Exactly which path you take will depend on your current usage and what you need to achieve. TBH, I think that you should really consider some significant maintenance on your fileservers. 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). Having said that, the history lesson is probably of limited value to you right now.ĭepending 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. So since v14.2 (inc v15.0) we've been including WebDAV-CGI. 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. We always intended to create a standalone Pydio appliance, for users that explicitly wanted that, but have never circled back around to that. 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 briefly looked at using Pydio for the Fileserver appliance in v14.0, but IIRC we had issues getting it installing properly in v14.0. Even if it's not publicly accessible, then you are still better off moving to a supported OS.įor historical context, IIRC, the web UI we provided for Fileserver v13.0 was "AjaXplorer". 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. Firefox and Chrome, etc) and see if that makes any difference.Īnother 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). Have you tried different web browsers? I suggest that you try different browsers (e.g. But a wild guess is that it's a browser update that has broken things. PS Doh, I just realised that we had already spoken recently! :) If Webmin isn't available on port 12321 and you are definitely using HTTPS then my guess is that you need to adjust setting as per my link above. However I can log in fine, so I suspect that is a red herring. Pam_unix(webmin:auth): authentication failure logname= uid=0 euid=0 tty= ruser= rhost= user=root You can't authenticate until it's running so it not starting because of incorrect password seems unlikely.?!Īctually I just checked on a server that I had running and when Webmin is restarted that is reporting a similar thing: Webmin not starting because of authentication seems weird to me. If that is irrelevant, then I am not really sure what might be the issue. The webmin specific bits are noted under a sub-heading, however some of the other info may also be relevant. v13.0 to v14.1) then there are probably a number of things that you will need to consider. are you restoring a backup from one version of TurnKey to the same appliance but a different version of TurnKey? Firstly, is this a simple backup/restore, or is it a migration? I.e.
0 Comments
Leave a Reply. |