P.S.'s picture

I am a total newbie here. I setup a Micro Redmine account. The Webmin will not let me login. Any super simple step-by-step instructions out there?

Forum: 
Jeremy Davis's picture

Using the root password you set on launch (assuming you set one) you should be able to log in to all these services using the same username and password. Ie

Username: root

Password: <set on launch>

Note that the Redmine Admin account login will be different (unless of course you set it as the same password - although the account name will still be different).

Moe's picture

Hello,

I'm a newbie too.

Accessing my account using "root" as my username and no password is not possible.

Im using AWS and Im not sure which password I had put. Is there a way to reset or retrieve my Webmin password through the EC2 console or something?

MB

Jeremy Davis's picture

The TKL Hub is a very nice Web front end for TKL appliances on AWS. It allows you to preseed the root password (as well as other important passwords and other cool stuff like setting a domain name with HubDNS).

So assuming that you haven't got very far yet, then destroying your instance, signing up for the Hub and starting with a new instance would be my recommendation.

However if you wish to persevere with your current instance then you can look over your VM log and find the randomly generated root password there (it hopefully shouldn't be too hard to find...).

Warren's picture

I loaded a LAMP stack intance and was able to login last night, but cannot login this morning. I can log into the myphpadmin, but not the webadmin. Same root and password.

I am trying to upload file via sftp. I am able to log into the server via sftp, again using the same root and password, but It does not allow me to upload anything. I get teh following error.

"Could not upload "index.html"
Make sure you have permissions to modify this file."

Any clues on what I need to do.

Trying to log into webadmin but cannot now.

Jeremy Davis's picture

That seems very strange... By default Webmin on TKL uses PAM authentication (i.e. Linux user credentials), which will be the same as SFTP (as that also uses Linux user account(s)). Whilst MySQL uses a root account it is not the same as the root account as the system (it is a specific MySQL account which is also named 'root', i.e. they can be different passwords).

The only thing that I could guess is that when you set up the system you intended to use the same password but actually didn't. Unless you have changed something there is no reason that I am aware of that the password should have changed.

woj's picture

That was my first instance, so I may have clicked on something I wasn't supposed to.

So I installed a new instance, same LAMP server, and it's working no problem now.

This is super cool. I'm ready to move all my sites from my dedicated server to the amazon platform. Saving money and never running out of disk space again.

Thanks,

woj

Jeremy Davis's picture

Glad to hear that you are up and running! :) Good luck with it!

Dan Kelley's picture

I have a brand new Turnkey LAMP instance and was able to set up the admin user (I read its not root for AWS)  I am able to log in to SFTP but unable to upload files... as I get a permissions denied error. I noticed all files are set to user/group: root/root in the /var/www directories. How can I log in as root and upload my own files? or should I be logging in as "admin" and uploading files and if so how to enable "admin" to upload files to /var/www ?   Thanks!  
Jeremy Davis's picture

You are correct in that AWS Marketplace instances have root disabled (and use admin instead). There are a few different ways you could go. The two that spring to mind (log in via SSH):

  • Enable root, and upload as root user - then everything will just work. You can do that like this (this will disable the 'admin' account and re-enable the 'root' account and copy across any existing use config from the current 'admin' account):
    sudo turnkey-sudoadmin off
  • Grant ownership of the /var/www filesystem tree to 'admin':
    sudo chown -R admin:admin /var/www
  • Beyond those, there are plenty of other ways you could go, such as creating a custom user for the purpose (could be useful if you want the web app you plan to run to have write access to the directory; or plan to use composer, etc).

    If you want to share more about your "grand plan" for the LAMP server, I'm happy to share more specifics.

    Add new comment