Hi Frank. I'm not too hip on load balancing but I might be able to sort you out a little on the LogFormat directive. This directive tells apache what information you want included in a particular log. Apache and/or its virtual host each have two logs. By default they are access_log and...
The machine that is setup to be your webserver needs to have a static ip address on the LAN side as well as the WAN side. Your router connects the two. The WAN or internet side of the router has a public ip address assigned to it. This is the one that dns servers use to point a web address to...
I don't think this is a file permission issue. It is acting like the DocumentRoot is not defined properly in the config file. The DocumentRoot directive should have the path to a directory that contains an index such as index.html or index.php. Then that directory should be defined with a...
One of the easiest ways is to put a .htaccess file in any subdir where you do not want access. It allows you to specify which type of access/authentication that subdirectory and all its subs can have. You can put just about any directive in the file that you can put in apache's main config...
If you are familiar with "yum", you can try "yum downgrade". It should roll back all the rpm packages to the last version. However, I don't think it works for the kernel. That shouldn't be a problem though because linux saves the older versions of the kernel. Just change to the one you want...
You need to tell apache where the web files are. This is called the DocumentRoot. You can edit or copy /etc/httpd/conf/httpd.conf to the new server and that should hook you up. Remember, any time you modify httpd.conf, you need to restart apache so it reads this file.
I know nothing about Windows stuff. In my opinion they should get out of the server business. That being said, apache uses the Listen directive to bind it to a particular address or port. By defaul it is all addresses on port 80 (Listen *:80). If you are using name based addressing, you...
If you can access everything from localhost then the problem is not with apache. You need to forward all http (port 80) traffic to the lan ip of the server.
It may be that you don't have the cgi part of the perl package. Another thing I was tinking is that your app may not be in a Script or ScriptAlias defined directory. Apache will parse any thing in these directories as script otherwise they are parsed as html. What do your error logs say?
Have you tried changing the hostname of the machine the server is on? If you are using that machine as a web server, mail server or both, you can still use that name for your machine since dns will be pointing to it already. However, if you are hosting other domains, you may want to go with...
There is rpmfind.net if you want to search for a particular package. If you have yum installed, you can type "yum install (package name)". You can update packages too. Let's say you want to update RPM itself. You would type "yum update rpm".
Since the ip addresses are commented out, they are not an issue. I can see by the use of caps that you are a Windows kind of guy. Linux doen not treat "This" the same as "this". Case does matter to linux. If you use caps, anybody typing your url will have to also.
Your vhosts are pretty fouled up. When an http request come in on port 80, apache looks for the requested domain. It uses the ServerName directive to resolve this. If you look at how you have things, you will see right away why apache would get so confused. Organizing things will help quite...
Is itssoezy.net a fully qualified domain name? I'm wondering why you are using it as a subdomain of inwoon.net. It seems search engines these days want to point back to the index of the top level domain. I am not sure why they think one of the index pages is a frame.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.