Jeff Watkins's picture


I have recently installed the gantry frame work Joomla 3.2 on a turnkey Lamp amd container.
Basically this is the same style as rackette theme templates Rocketlauncher to in stall gantry frame work 4.1....

My question is I have made the php.config writable by using the command:

chmod -R a+rwX /var/www

Afterwards I checked the joomla installer and it showed it had been changed and I got the green light to go on...

I can access the backend admin. but trying to navigate to the front end .Just gives me a blank page.
the header tab indicates it is there.. but no site shows up..

any ideal waht can cause such a thing..


Jeremy Davis's picture

I'm not sure if it's the issue, but personally I'd just give ownership to the webserver (i.e. www-data). I suspect that that isn't your issue but probably a better way to go... Do that like this:

chown -R www-data:www-data /var/www

Beyond that I would check the Apache logs to see if there is anything there that might be the cause. IIRC Apache logs should be /var/log/apache2

Jeff Watkins's picture

Well after researching for days now.. I have learned quite a bit ...What I have done is started with a basic joomla site such as joomla 3.3...  I cannot use the turnkey joomla sites because of the components that I use are way further ahead on the joomla version scale and it seems that the transition joomla is going through at the moment is critical .. So what I am trying to do is plant my feet at at a level where all the extensions I have for joomla all are compatable .. and then start my development at this point and build sites at the 3.2 or 3.3 versions ...But what I discovered is that lamp doesnt have installed all the things I require.. as far as running joomla yes.. but not adding components such as kunena and jomsocial... which require curl and ffmpeg and imagemagick...ect.....

so I have Installed these via command line....


What i would like to know is there a way to have a interface to all the options such as wamp has for windows version.. say in the webmin .. to where I can turn these off and on as needed..and add the required extensions for the server via webmin...
In wamp I have a list of php extensions as well php settings.. Now I have found settings as far as php.ini Inside of webmin...But I dont know how to access php extensions from webmin...

Is there a module that I can install for webmin that will group these..and allow me to have more than one php version available....for testing .... Would adding virtualmin to this give me these options or will it make it impossible to upgrade when needed...It seems that the apt-get repositories are not the latest versions . cause even when I upgrade webmin still claims it is not the latest version..

or possibly a better option is to install possibly a full blown lamp setup and not the turnkey appliance that possibly has a small linux distro packaged with it just enough to run full blown lamp ....a bloated version . until such time I have it all done .. I have plenty of overhead


Do you have any Ideas on this.....?????????

What about building a server on the Kali distro ????

I have so many questions loloolol...

By the way I wrote the tutoral as requested . for the basic Installation of Proxmox
you can let me know what you think?





Jeremy Davis's picture

I've been so bogged down...

Firstly I'd like to say a massive thanks for the work you've done on that tutorial. Excellent! You rock! :)

As for Joomla, be a little wary of using the bleeding edge versions as they usually have much more limited support periods (i.e. you'll need to update much more regularly and you may well find that some of your extensions may lag with timely development and may not even be available for the newest version). They may not too, but I thought it was worth mentioning so that you are making an informed decision! My suggestion is to have a careful read of this. You'll notice that the version in TurnKey is 2.5 and whilst it is older, it is actually supported the longest. It is supported until the end of this year, whereas 3.2 is only supported until Oct and 3.3 looks like it is only supported until the release of 3.4 (which is anticipated to be next month!). Although I do note that they have released a new strategy which I haven't read properly so I'm not sure of the implications...

TBH I have never used WAMP and I have no idea how you could or would "turn them off" (other than removing access to them). Both curl and ffmpeg are programs that other than taking up space on your harddrive don't use any resources unless they are being used... However imagemagick is a php module and can be manually enabled/disabled (and perhaps the others you were talking about you were referring to php moudles for them too?). Generally the Debian way would be to install it (via apt) if you want it and remove it if you don't... You could manually enable it or disable it but IMO it's easier to just install or remove... Perhaps there's a better way but I'm unaware of it...

Linux doesn't really lend itself well to provide 'bleeding edge' versions. Like most things in life there is always a compromise and Linux (especially Debian - the basis of TurnKey) tends to favour stability and security over latest versions. The downside is that using 'bleeding edge' versions of stuff is a bit more painful, but IMO the rock solid stability and automated security updates (as pre-configured in TurnKey) more than make up for that. Having said that,if you are using this simply as a dev box (and aren't so worried about security concerns) then Dotdeb might be a good option?

As for your questions regarding VirtualMin TBH I can't say as I've never used it (nor tried. But if you have a crack and get stuck I'm more than happy to try to help you out.

Although TBH if I were you (with your grunty Proxmox server) I'd just make them separate servers, and just set each one up individually! That's what I do and it works well for me...

Jeff Watkins's picture

Ok Jeremy

Here is what I am dealing with now?

Little History first: "The Greatest CMS Combination Ever"

  1. We are using joomla 3.3.1(Installation is Gantry RocketLauncher/Joomla 3.2)Then Upgraded/3.3.1)
  2. Gantry Framwork is 4.1.24
  3. Kunena Forums 3.0
  4. Jomsocial
  5. WordPress For Joomla(By Core PHP)LatestVersion3.8) it installs as a component)Its Awesome........
    This Now gives you the most powerful CMS on the planet/Joomla and the most powerful blogging
    CMS/Word Press which happens to be the second most powerful CMS...Well Its all Debatable...LOL
  6. Akkeba Backup
  7. Akeeba Admin Tools
  8. Akeeba Cms Update
    Ok this is the core setup for the most stable and functional website after years of dealing with
    websites. this has made the List.. Minus a shopping cart for now...

Everything here functions perfectly and harmonously together..Say at Hostgator...
My issue I am having is that changing the htacces.txt to .htaccess so that I can access worpress
from my local Lamp server installation...
I am super close to having lamp configured perfect to run all of this perfect.

Which I will list what has to happen as far as Lamp extensions and php.ini stuff when I am finished.
So my issue is getting the server to allow this change from htaccess.txt to .htaccess..

I am getting a 500 error. when trying to access the site.
my site resides in /var/www/joomla
It is in a folder called joomla inside the root www...

I have made follow symlinks disabled.

In the rename .htaccess file
Not sure what I have to do with lamp to get this to fly?????

Any Ideas..


Jeremy Davis's picture

I love your enthusiasm and your willingness to share your journey and config. I love to see new TKL users as keen, engaged and willing to share their info as you are! So great work! :)

But as to your questions regarding your .htaccess file, I'm not really sure... My experience with .htacess files is quite limited. I know they are the only way to do things in a shared hosting situation and that some software requires them, but often when you are running your own server the config can be done directly in the Apache config files (which is essentially what a .htaccess file is). Obviously in some situations you may find the granular control available via multiple .htaccess files makes more sense, but I'm more of a tinkerer rather than a hard core developer in that sense and find that the clarity of using Apache 'sites' files (together all in the one place) easier to keep track of... In case you weren't aware, the config files can be found in /etc/apache2/sites-available. The ones listed in /etc/apache2/sites-enabled are the ones actually in use. They're actually just symlinks to the files in /etc/apache2/sites-available. You can manually create or remove the symlinks but the a2dissite and a2ensite commands are easier IMO. As an example to disable the default 'site':

a2dissite default && service apache2 reload

As for troubleshooting, you might get a better idea of what is actually causing the issue by having a peek in the Apache logs. You'll find them in /var/log/apache2

Add new comment