johnbmcdonald's picture

Please pardon my nubiwness....

I looked through the docs, maybe not close enough? please point me to the corret doc/page?


is webmin part of the LAMP installation?

If so, how do I access it? I don't see anything in var/www

if not, how do I install it? is there a wget command or something to use?

Thanks for your help


Alon Swartz's picture

You will notice when the appliance has booted, you are presented with the Configuration Console explaining the different ways to access the appliance over the network (ie. Webmin =~ Admin Console).

Just point your browser to https://appliance_ip:10000 and log in with user 'root' (default password is blank).

If you have any other questions, just ask - thats what the forums are for.

johnbmcdonald's picture

having already installed to the hard drive, and booted from the hard drive, I don't receive the configuration console. It just boots to the command prompt. I do get the standard "It Works!" at and I can login via SSH at butI don't get a response at Thanks John
Alon Swartz's picture

The configuration console "should" be launched no matter if the system is installed or running live.

Webmin is listening on port 10000 not 1000, so give this a try:

Is it possible that you are using the old version of lamp (which doesn't have the configuration console or webmin)? The latest version is turnkey-lamp-2008.10.17-hardy-x86.
johnbmcdonald's picture

Firefox can't establish a connection to the server at The image I've got is: turnkey-lamp-2008.09.02-hardy-x86.iso I'll go download the latest one & see what happens. Thanks John
Liraz Siri's picture

The version you are using is the initial launch release in September, which didn't yet include the configuration console or web management interface.

Note that our news release regarding the usability improvements is from October.

Alon Swartz's picture

The configuration console and web management interface were introduced in the latest release, along with some other goodies... - you can see the release notes here:

If you come across any other issues, give us a shout!

Jeremy Davis's picture

If you are using TurnKey Linux then you should find Webmin via https on port 12321. E.g.

If that's not working, then please log in to your server and check that Webmin and Stunnel are running:

service webmin status
service stunnel4 status

If you aren't using TurnKey, then 10000 should be the default Webmin port, but I have no idea how you installed it etc. So I suggest that you either post on the support forum of your OS, or perhaps on the Webmin support forums? They will probably need some more info from you though, such as how you installed it.

marcelomiiji's picture

I signed the Turnkey service today and installed Magento on amazon ec2. The mysql password was generated but not the webmin! I can not access webmin. Neither the ssh terminal!

Please help me.


Jeremy Davis's picture

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.

Jeremy Davis's picture

I have lodged a bug report.

Alon Swartz's picture

The default bit-length in the inithook [1] which regenerates the SSL certificate on firstboot is set to 1024. I tested regenerating the certificate as well as increasing the bit-length, and I don't see any keygen issues.

$ openssl s_client -showcerts -connect localhost:12321 |grep 1024
Server public key is 1024 bit

The OP mentioned connecting to webmin on port 10000, but that hasn't been the default webmin port for years. Was webmin installed directly from upstream and using the default cert?

Any more info that you can provide would be great. Can someone reproduce/confirm the issue?

[1] /usr/lib/inithooks/firstboot.d/15regen-sslcert

Jeremy Davis's picture

Perhaps I was being a little over-zealous that day?!? 

Perhaps they had Webmin from somewhere else and just came across TKL in their travels and posted the issue?

Looks like maybe I jumped on it too quick (without asking enough questions...) I notice that I marked it as confirmed and normally wouldn't do that unless I either had come across a second report of the bug or could reproduce it myself, but I don't recall testing it...

My bad I think... Sorry!

Alon Swartz's picture

I marked the bug report as invalid for now, and we'll re-open if new information is submitted.

Jeremy Davis's picture

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...

Jeremy Davis's picture

A Linux server is essentially the same base OS as a desktop OS. They are just built with a different end goal. So the main difference is just that a server tends to have services that run in the background and only has CLI; where as a desktop has a GUI and is intended more for use with foreground apps...

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

Jeremy Davis's picture

Assuming you're using TurnKey then the default username is "root" and the password is whatever you set your root user password to be.
Jeremy Davis's picture

Besides it sounds like you aren't using TurnKey Linux?! TurnKey comes with Webmin pre-installed already (and this is our forums).

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...

i use root as  name  and  the  password  i entered  when installed the lamp stack turnkey-lamp-14.1-jessie-i386.iso

but  it says
Login failed. Please try again.

ok found  out 
my  linux  pc  has English  keymap and  my other  pc has Danish  thats  why  entering  password  fails

but  did not help cant  login from the  other  pc, strange

ok ok my bad was still not same keymap
so  solved it. 


Jeremy Davis's picture

FWIW we do have plans in the pipeline to make it easier to add alternate keymaps.
Jeremy Davis's picture

MineOS is a third party appliance which we don't have anything to do with. I did have discussions with the lead dev about making it an "official" appliance, but that stalled and I haven't ever got back in touch to see whether that's still an option.

Perhaps it's not based on TurnKey anymore?

Preston's picture


I just restored a production server from a backup to a fresh install of the MySQL app vmdk. I can no longer access webmin or ssh. When I try to manually activate webmin via "service webmin start", I get the following error: 

Job for webmin. service failed. See 'systemctl status webmin.service' and 'journalctl -xn' for details.

When I run "systemctl status webmin.service -l" I get errors suggesting webmin authentication failed. So I tried reseting the webmin root password using ./ /etc/webmin root NEWPASS and repeated the process. Didn't help. Any suggestions?




Jeremy Davis's picture

Firstly, is this a simple backup/restore, or is it a migration? I.e. are you restoring a backup from one version of TurnKey to the same appliance but a different version of TurnKey?

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
However I can log in fine, so I suspect that is a red herring. 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.

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

Jeremy Davis's picture

You are most welcome! :)
Jeremy Davis's picture

You'll need to provide more information before anyone will be able to help you.

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

  • what version of TurnKey you are using
  • which web browsers you have tried
  • more explict details of the error that is occuring
  • exact steps to reproduce the issue

    Please also consider including screenshots and/or copy/paste exact text from error messages. The better I can understand what your issue is, the easier it will be to help you.

  • Jeremy Davis's picture

    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.

    Jeremy Davis's picture

    Ah ha! Yes that would certainly explain it!

    Thanks for posting back with that info. Glad you go it sorted.

    Apologies on my apparently irrelevant essay! :)

    Add new comment