Hi. I've just installed the latest mediaWiki vm, which is running under VMWare Player. I've been through the initial steps that setup passwords etc and am faced with the MediaWiki Appliance Services menu within the Turnkey Linux Configuration Console. I'd like to do something more ! I presume that I should just be able to copy each of the URLs into my browser and start doing stuff - is that right ? I've tried this, but although I can ping the IP address, my browser (IE v 11) won't connect. Any suggestions would be very welcome.
I started a new server and ran moodle on it, but it jumped to 100% cpu usage and has been that way since. I tried rebooting the server to no avail, and also stopping the server and restarting it as was suggested in previous similar forum suggestions. Any thoughts?
I was attempting to resolve my "OTRS Scheduler" issue within my other post (here) and as I was browsing around Webmin, I went into MySQL and changed the IP Address from 127.0.0.1 to the Appliance IP Address (assuming this wouldnt break anything).
After I hit SAVE, it indicated that the permissions bound to 127.0.0.1 were lost and that I had to reauthenticate credentials to MySQL to proceed with the changes.
Does TKL support the lighttpd simple_vhost module? How do I install it? Sorry, I am new to the Debian platform, so do I need to add repos, or does that violate the support for TKL? Some distros are strict about this kind of thing, others not, so I don't want to make a move until I know one way or the other.
I'm using a TLKAPP server on AWS (via hup.turnkeylinux.org), and I've got an issue:
I'm getting charged for an un-used Elastic-IP.
Now this is what I've done:
Within the server section, I clicked on "Associate Elastic IP". This gave me an error, saying that my server is part of a VPC, and therfore can't have an elastic IP associated. I thought nothing more of it, until I got a bill.
Now I've looked through the EC2 section of AWS console and the VPC section, and neither seem to think that I've got an elastic IP allocated.
Today I tried the nginx v14 appliance for the first time, and SSL didn't work via nginx (default site and adminer), I think because the syntax for the nginx listen directive has changed slightly since the v13 version. I was able to fix with the following.