Create a custom theme
2
Brought forward from my original posted article.
Progress on the test machine
Fedora 15 and ISPConfig 3
Original Author: Falko Timme from HowtoForge.com
Are you getting tired of paying High hosting prices and getting very little in return?
The test machine setup using Fedora 15 and ISPConfig 3 has been coming along very well.
The main purpose I have chose Fedora 15 for this project has mainly to do with its lack of fear staying on the cutting edge unlike other Linux distributions where Invison Power is concerned and the direction or future IPS is leaning to-wards.
For those of us that use Xampp or Wammp on our test systems already know the importance of the stability and the upgrade ability these two applications when it comes to the core features Apache Web Server, Mysql, PHP and Phpmyadmin. As we all know and learned without these factors your test boards could not operate.
Don't get me wrong I like CenTOS, Webmin and Virtualmin very well too! But when it comes to a few factors like usability and updates CenTOS falls a bit short especially where it come to updating the LAMP (Linux, Apache, Mysql, Php) packages and dependencies. Unless you know exactly how to compile and create these packages with their dependencies from scratch you will be just as screwed as I was. And if you are a born and bred Windows user like me Good Luck in the Linux forums.
Fedora 15 is boxed with all the current LAMP packages with dependencies.
* Apache/2.2.17
*Mysql Server version: 5.5.14
*Php 5 version: 5.3.6
*Phpmyadmin version: 3.4.3.1
The downfall to Fedora is not the lack of usability with Webmin per say but with its child products Virtualmin and Usermin.
***The installer should only be used on systems that are not currently running Webmin or hosting any websites. Ideally, it should be run on a system that has a fresh install of either CentOS 5, Debian 4.0, Ubuntu 8.04 or Solaris as at the moment those are the only supported operating systems. Further documentation on supported systems and install requirements is available on the Virtualmin download page. (see article)***
*** Fedora is a bit too much of a moving target to support as a viable server operating system. If you're interested in using an RPM-based distro, you might consider CentOS. CentOS 6 should be coming out soon, but even sooner than that, Virtualmin should be supporting Scientific Linux 6 (which is already out, and just needs to have the installer tweaked a bit to support it). (see article) ***
There is an article over at HowtoForge.com on how to setup the Perfect Server.
The Perfect Server - Fedora 15 x86_64 [ISPConfig 3]
But just like anything else that falls under the term "FREE" you have to understand that it too comes with a few quirks which I will go into in a bit.
By following the above tutorial you will soon be on to setting up your own web server but first things first.
First you need a FQDN (Fully Qualified Domain Name) this you can setup with any reputable registrar unless you are using this as a test server which in this case I would stick with Xampp or Wammp.
In the tutorial FalKo is using the computers local dynamic IP address 192.168.1.x and changing it to a local static IP of 192.168.100 which is fine and good if you are planning on using something like "No-IP.com" to convert your Dynamic IP into a usable Internet friendly Static IP address.
Unfortunately this too has its downfalls. One argument of mine is you have no idea who you are sharing an IP with. Those they assign you to may be upstanding people with reputable sites or you may be assigned an IP with a few predators you really don't know. You don't have a say where they assign you.
I have had in the past routers setup behind my DSL gateway's that worked fine. But today I am hooked up with AT&T's U-verse which has its own router and WAN system that does not seem to play well with either of my routers. This system is the main hub you might say to everything in the house communication wise. TV, Internet, VOIP Phone system and Washer and Dryer… OK so it won't wash or dry my clothes I was just checking if you were still here… Anyway due to the multi-functions of the gateway you can see why the router can create a few hick-ups in the system.
So with that said at some point before setting up your server it might be a good idea to check with your INTERNET provider about getting a block of static IP's. In my case you can only purchase them in blocks of 8 with 5 usable IP's for the first block. Why not all 8 you ask? The 1st,7th and 8th in a block of 8 IP's are pre-defined. The first is your router reference point. The seventh is your new public gateway IP and the eighth is your Broadcast IP being the last two get you out to be seen on the web.
Here is an example of my block of 16 to clarify:
108. xx.xxx.112 This is the router starting point from where it delegates which IP will be assigned to a particular computer or Nic.
108. xx.xxx.113 This is the first IP assigned in this case to my live web server.
108. xx.xxx.114 This is the IP assigned to my test server from where I am first setting up Fedora and ISPConfig3
108. xx.xxx.115 (Future)
108. xx.xxx.116 (Future)
108. xx.xxx.117 (Future)
108. xx.xxx.118 (Future)
108. xx.xxx.119 (Future)
108. xx.xxx.120 (Future)
108. xx.xxx.121 (Future)
108. xx.xxx.122 (Future)
108. xx.xxx.123 (Future)
108. xx.xxx.124 (Future)
108. xx.xxx.125 (Future)
108. xx.xxx.126 This is the IP assigned as the new public gate way not to be confused with your IPS DCHP Gateway IP.
108. xx.xxx.127 This is the Broadcast IP. Without it you will never broadcast to the outside world "Hello World!"
OK, we now have a FQDN and we have decided whether or not to use No-IP.com to convert our local IP to a static IP or we decided on purchasing a block of IP's from the Internet provider.
OK, Now for FalKo's Tutorial The Perfect Server - Fedora 15 x86_64 Don't let the title fool you it also will work on a 32 bit system as well.
So let’s get started
First go to the article read it and understand it. The following steps will come to light… on how to setup The Perfect Server - Fedora 15 x86_64 [ISPConfig 3].
To install such a system you will need the following:
• Download the Fedora 15 DVD iso image from a mirror near you (the list of mirrors can be found here: http://mirrors.fedor...list/Fedora/15/), e.g. http://ftp.tu-chemni...-x86_64-DVD.iso
There are a few small steps to make your life easier while installing Fedora 15 that the tutorial missed as I was saying earlier in this article.
In Step 3 Install The Base System
After you fill in the hostname of the server, it will be less confusing to configure your network now rather than later on while setting up packages in the upcoming step "Now we select the software we want to install."
After this step: "The hard drive is being formatted:" has been completed follow the next steps as FalKo mentions as far a setting up the Web Server. By configuring your network already there are a few steps you will bypass here. So you can go right to installing the two repositories needed and DO NOT FORGET THE "CUSTOMIZE NOW" RADIO BUTTON at the bottom!!! You need to go to this step.
We will now be sent to the customization page where you will select your packages
(Trust me, this did not work for me in the end results.)
Falko says:
"Now we must select the package groups we want to install. Select Editors, Text-based Internet, Development Libraries, Development Tools, DNS Name Server, FTP Server, Mail Server, MySQL Database, Server Configuration Tools, Web Server, Administration Tools, Base, Hardware Support, Java, System Tools (unselect all other package groups) and click on Next:"
Instead Select these Packages and you will have less headaches setting up your server. Again Trust me on this after many reformat and installs this is what works.
Now Select:
"Desktop Environment" and select Gnome (I will explain later).
"Applications" and select Editors, Text based Internet and system tools.
"Development" select Development Libraries, Development Tools.
"Servers" select Server Configuration Tools, Web Server.
"Base" select, Administration Tools, Base, Hardware Support, Java and System Tools.
Now (unselect all other package groups) and click on Next:
By selecting these packages this way you will find that there will be no install errors later. But don’t worry they will be installed later in the article and it will work without errors forcing you to start over from scratch.
Now wait for the install to complete and reboot.
The next step is pretty basic just answer the questions and reboot again.
OK here is the reason I had you choose Gnome as a desktop environment rather than strictly command.
If you are like me you were born and bred on Windows, but even this step can and will help the expert Linux Guru.
1st. You can physically see the files and their structure as well as how they tie into your system and web server.
2nd. If you find an error while using the terminal you can go back to the file in the file manager and see where the necessary repairs need to be made. Then using the terminal make the needed edits.
3rd. You are going to get errors after the whole setup is complete Reading the log file entries will give you a start on fixing those errors. As a normal user you won't have permission to access these files and logs.
So you can see where the GUI is an important tool.
While in the Terminal unfortunately just like Dos in the day or the MS Command line of today you can go on forever and never be notified of a small error that will screw up the works. And while logged in as normal user you will find out in a heartbeat you do not have permission to read or write to the effected files. Either way you need Super User (root) Access.
Now here is a good place where I really upset the apple cart when it comes to the expert guru’s… ROOT ACCESS TO THE GUI. That's right super NERD I am telling all so they don't have to make the same mistakes!!!!!
For me as my best example using the terminal and using su or sudo I have screwed up more than I care to talk about let alone get into a pissing contest over because some clown with a pocket protector told me I should not do this I can screw up the whole operating system and will need to reinstall it… Nice bit of warning but I have had to reinstall more times than I care to remember because of a command line error or a terminal error using sudo. I am also glad to announce since I figured out how to allow root as a GUI user I have not once had to reformat nor have I had to reinstall.
Now let's get on with it
To unlock root
This works in Gnome and it is the only reason I chose it.
Go into the terminal – su and type in the root password you gave in the beginning of the install.
In the /etc/pam.d/gdm comment out "auth required pam_succeed_if.so user != root quiet"
Then do the same with /etc/pam.d/gdm-password
Next you are free and clear all the way to step 5. Just follow Falkos Guide and you will be right with the world!
5 Adjust /etc/hosts
This is important to add after this next step, it will make sure your static IP stays static…
If it is not already here add ore replace: keeping in mind your IP's
7 Disable SELinux
8 Install Some Software
From here on you will follow the guide as it is
But further into this article you will see why we chose not to include certain packages to be added to the repository as originally stated.
There will be a few short articles that will be added to this in future episodes on other How To Fix’s
In the mean time this should get you going in the right direction.
Don't forget to make all the necessary changes with your registrar after you have setup ISPConfig3
1 Final Edit
After you have completed the ISPConfig 3 setup and you go to do an email test, you may find first email attempt will send from your new server but won't receive.
Here is a fix for this problem. (This you can do from the GUI as root)
Go into your file manager /etc/postfix/main.cf
change:
*** NOTE ***
I have now tested this on 3 separate drives and works without errors on each drive.
On to the Next! as Jay would say...
Next step installing to the live server.
*** One Last Note ***
During the ISPConfig 3 setup (System, Clients, Sites Ect...)
At some point before you setup the DNS Server first go to /etc/named.cf and comment out listen-on port 53 { 127.0.0.1; };
And yes I am running this system on the live server...
It has been working flawlessly since July of this year
Progress on the test machine
Fedora 15 and ISPConfig 3
Original Author: Falko Timme from HowtoForge.com
Are you getting tired of paying High hosting prices and getting very little in return?
The test machine setup using Fedora 15 and ISPConfig 3 has been coming along very well.
The main purpose I have chose Fedora 15 for this project has mainly to do with its lack of fear staying on the cutting edge unlike other Linux distributions where Invison Power is concerned and the direction or future IPS is leaning to-wards.
For those of us that use Xampp or Wammp on our test systems already know the importance of the stability and the upgrade ability these two applications when it comes to the core features Apache Web Server, Mysql, PHP and Phpmyadmin. As we all know and learned without these factors your test boards could not operate.
Don't get me wrong I like CenTOS, Webmin and Virtualmin very well too! But when it comes to a few factors like usability and updates CenTOS falls a bit short especially where it come to updating the LAMP (Linux, Apache, Mysql, Php) packages and dependencies. Unless you know exactly how to compile and create these packages with their dependencies from scratch you will be just as screwed as I was. And if you are a born and bred Windows user like me Good Luck in the Linux forums.
Fedora 15 is boxed with all the current LAMP packages with dependencies.
* Apache/2.2.17
*Mysql Server version: 5.5.14
*Php 5 version: 5.3.6
*Phpmyadmin version: 3.4.3.1
The downfall to Fedora is not the lack of usability with Webmin per say but with its child products Virtualmin and Usermin.
***The installer should only be used on systems that are not currently running Webmin or hosting any websites. Ideally, it should be run on a system that has a fresh install of either CentOS 5, Debian 4.0, Ubuntu 8.04 or Solaris as at the moment those are the only supported operating systems. Further documentation on supported systems and install requirements is available on the Virtualmin download page. (see article)***
*** Fedora is a bit too much of a moving target to support as a viable server operating system. If you're interested in using an RPM-based distro, you might consider CentOS. CentOS 6 should be coming out soon, but even sooner than that, Virtualmin should be supporting Scientific Linux 6 (which is already out, and just needs to have the installer tweaked a bit to support it). (see article) ***
There is an article over at HowtoForge.com on how to setup the Perfect Server.
The Perfect Server - Fedora 15 x86_64 [ISPConfig 3]
But just like anything else that falls under the term "FREE" you have to understand that it too comes with a few quirks which I will go into in a bit.
By following the above tutorial you will soon be on to setting up your own web server but first things first.
First you need a FQDN (Fully Qualified Domain Name) this you can setup with any reputable registrar unless you are using this as a test server which in this case I would stick with Xampp or Wammp.
In the tutorial FalKo is using the computers local dynamic IP address 192.168.1.x and changing it to a local static IP of 192.168.100 which is fine and good if you are planning on using something like "No-IP.com" to convert your Dynamic IP into a usable Internet friendly Static IP address.
Unfortunately this too has its downfalls. One argument of mine is you have no idea who you are sharing an IP with. Those they assign you to may be upstanding people with reputable sites or you may be assigned an IP with a few predators you really don't know. You don't have a say where they assign you.
I have had in the past routers setup behind my DSL gateway's that worked fine. But today I am hooked up with AT&T's U-verse which has its own router and WAN system that does not seem to play well with either of my routers. This system is the main hub you might say to everything in the house communication wise. TV, Internet, VOIP Phone system and Washer and Dryer… OK so it won't wash or dry my clothes I was just checking if you were still here… Anyway due to the multi-functions of the gateway you can see why the router can create a few hick-ups in the system.
So with that said at some point before setting up your server it might be a good idea to check with your INTERNET provider about getting a block of static IP's. In my case you can only purchase them in blocks of 8 with 5 usable IP's for the first block. Why not all 8 you ask? The 1st,7th and 8th in a block of 8 IP's are pre-defined. The first is your router reference point. The seventh is your new public gateway IP and the eighth is your Broadcast IP being the last two get you out to be seen on the web.
Here is an example of my block of 16 to clarify:
108. xx.xxx.112 This is the router starting point from where it delegates which IP will be assigned to a particular computer or Nic.
108. xx.xxx.113 This is the first IP assigned in this case to my live web server.
108. xx.xxx.114 This is the IP assigned to my test server from where I am first setting up Fedora and ISPConfig3
108. xx.xxx.115 (Future)
108. xx.xxx.116 (Future)
108. xx.xxx.117 (Future)
108. xx.xxx.118 (Future)
108. xx.xxx.119 (Future)
108. xx.xxx.120 (Future)
108. xx.xxx.121 (Future)
108. xx.xxx.122 (Future)
108. xx.xxx.123 (Future)
108. xx.xxx.124 (Future)
108. xx.xxx.125 (Future)
108. xx.xxx.126 This is the IP assigned as the new public gate way not to be confused with your IPS DCHP Gateway IP.
108. xx.xxx.127 This is the Broadcast IP. Without it you will never broadcast to the outside world "Hello World!"
OK, we now have a FQDN and we have decided whether or not to use No-IP.com to convert our local IP to a static IP or we decided on purchasing a block of IP's from the Internet provider.
OK, Now for FalKo's Tutorial The Perfect Server - Fedora 15 x86_64 Don't let the title fool you it also will work on a 32 bit system as well.
So let’s get started
First go to the article read it and understand it. The following steps will come to light… on how to setup The Perfect Server - Fedora 15 x86_64 [ISPConfig 3].
To install such a system you will need the following:
• Download the Fedora 15 DVD iso image from a mirror near you (the list of mirrors can be found here: http://mirrors.fedor...list/Fedora/15/), e.g. http://ftp.tu-chemni...-x86_64-DVD.iso
There are a few small steps to make your life easier while installing Fedora 15 that the tutorial missed as I was saying earlier in this article.
In Step 3 Install The Base System
After you fill in the hostname of the server, it will be less confusing to configure your network now rather than later on while setting up packages in the upcoming step "Now we select the software we want to install."
After this step: "The hard drive is being formatted:" has been completed follow the next steps as FalKo mentions as far a setting up the Web Server. By configuring your network already there are a few steps you will bypass here. So you can go right to installing the two repositories needed and DO NOT FORGET THE "CUSTOMIZE NOW" RADIO BUTTON at the bottom!!! You need to go to this step.
We will now be sent to the customization page where you will select your packages
(Trust me, this did not work for me in the end results.)
Falko says:
"Now we must select the package groups we want to install. Select Editors, Text-based Internet, Development Libraries, Development Tools, DNS Name Server, FTP Server, Mail Server, MySQL Database, Server Configuration Tools, Web Server, Administration Tools, Base, Hardware Support, Java, System Tools (unselect all other package groups) and click on Next:"
Instead Select these Packages and you will have less headaches setting up your server. Again Trust me on this after many reformat and installs this is what works.
Now Select:
"Desktop Environment" and select Gnome (I will explain later).
"Applications" and select Editors, Text based Internet and system tools.
"Development" select Development Libraries, Development Tools.
"Servers" select Server Configuration Tools, Web Server.
"Base" select, Administration Tools, Base, Hardware Support, Java and System Tools.
Now (unselect all other package groups) and click on Next:
By selecting these packages this way you will find that there will be no install errors later. But don’t worry they will be installed later in the article and it will work without errors forcing you to start over from scratch.
Now wait for the install to complete and reboot.
The next step is pretty basic just answer the questions and reboot again.
OK here is the reason I had you choose Gnome as a desktop environment rather than strictly command.
If you are like me you were born and bred on Windows, but even this step can and will help the expert Linux Guru.
1st. You can physically see the files and their structure as well as how they tie into your system and web server.
2nd. If you find an error while using the terminal you can go back to the file in the file manager and see where the necessary repairs need to be made. Then using the terminal make the needed edits.
3rd. You are going to get errors after the whole setup is complete Reading the log file entries will give you a start on fixing those errors. As a normal user you won't have permission to access these files and logs.
So you can see where the GUI is an important tool.
While in the Terminal unfortunately just like Dos in the day or the MS Command line of today you can go on forever and never be notified of a small error that will screw up the works. And while logged in as normal user you will find out in a heartbeat you do not have permission to read or write to the effected files. Either way you need Super User (root) Access.
Now here is a good place where I really upset the apple cart when it comes to the expert guru’s… ROOT ACCESS TO THE GUI. That's right super NERD I am telling all so they don't have to make the same mistakes!!!!!
For me as my best example using the terminal and using su or sudo I have screwed up more than I care to talk about let alone get into a pissing contest over because some clown with a pocket protector told me I should not do this I can screw up the whole operating system and will need to reinstall it… Nice bit of warning but I have had to reinstall more times than I care to remember because of a command line error or a terminal error using sudo. I am also glad to announce since I figured out how to allow root as a GUI user I have not once had to reformat nor have I had to reinstall.
Now let's get on with it
To unlock root
This works in Gnome and it is the only reason I chose it.
Go into the terminal – su and type in the root password you gave in the beginning of the install.
In the /etc/pam.d/gdm comment out "auth required pam_succeed_if.so user != root quiet"
vi /etc/pam.d/gdmIt should look like this.
#auth required pam_succeed_if.so user != root quiet
Then do the same with /etc/pam.d/gdm-password
vi /etc/pam.d/gdm-passwordIt should look like this.
#auth required pam_succeed_if.so user != root quiet*** For those who are not familiar with the vi editor, once the file opens click (i)insert make the appropriate edit(s)… To save click Esc, Shift : (colon) then wq!
Next you are free and clear all the way to step 5. Just follow Falkos Guide and you will be right with the world!
5 Adjust /etc/hosts
This is important to add after this next step, it will make sure your static IP stays static…
vi /etc/sysconfig/network-scripts/ifcfg-eth0
If it is not already here add ore replace: keeping in mind your IP's
BOOTPROTO=static BROADCAST=192.168.0.255 IPADDR=192.168.0.101 NETMASK=255.255.255.0 NETWORK=192.168.0.0
7 Disable SELinux
8 Install Some Software
From here on you will follow the guide as it is
But further into this article you will see why we chose not to include certain packages to be added to the repository as originally stated.
There will be a few short articles that will be added to this in future episodes on other How To Fix’s
In the mean time this should get you going in the right direction.
Don't forget to make all the necessary changes with your registrar after you have setup ISPConfig3
1 Final Edit
After you have completed the ISPConfig 3 setup and you go to do an email test, you may find first email attempt will send from your new server but won't receive.
Here is a fix for this problem. (This you can do from the GUI as root)
Go into your file manager /etc/postfix/main.cf
change:
mailbox_size_limit= 0 message_size_limit= 0to
mailbox_size_limit= 204800 message_size_limit= 204800or higher as needed
*** NOTE ***
I have now tested this on 3 separate drives and works without errors on each drive.
On to the Next! as Jay would say...
Next step installing to the live server.
*** One Last Note ***
During the ISPConfig 3 setup (System, Clients, Sites Ect...)
At some point before you setup the DNS Server first go to /etc/named.cf and comment out listen-on port 53 { 127.0.0.1; };
//listen-on port 53 { 127.0.0.1; };
and replace with:listen-on { any; };
Next comment out allow-query { localhost; };//allow-query { localhost; };
and again replace with:allow-query { any; };
Now you can setup your DNS Server without error.And yes I am running this system on the live server...
It has been working flawlessly since July of this year
