I recently installed Apache and enabled "localhost" with Windows. When I type "localhost" in my browser, it brings me to a page explaining that the Apache installation was successful. I just don't know where to find this. Is it reading some index.html file? If so, I just can't find it.
I tried going to C:\inetpub\wwwroot but the "localhost" in the browser is not reading it from this location. Where else is it reading localhost from? I use Windows 7.
This is usually found in \apache\htdocs on a Windows default install. The 'Pre-Installation' steps covered in this Apache, PHP and MySQL setup guide might be helpful.
If you use a default install of WampServer, it will be in C:\wamp\www
Related
I purchased a fancy little "visual menu maker" over at envato (Code Canyon) from here: https://codecanyon.net/item/z-menu-maker-drop-down-and-mega-menu/9240528
I was using their sample app where you can test out the tool and I was able to create a nice little menu for my site. But you have to purchase a license to export the code.
I purchased the license and the first "Getting Started" requirement is to "Start your Web Server and open the index.html file. This is where I'm lost. BTW... for reference, you can scroll to the bottom of that documentation page to see all the files that were included in the download.
When I try to open that "index.html" file in my browser, it doesn't load.
I followed some instructions to get my native Mac Apache server running, and everything seems to be working, with my localhost, but I don't know how to open this file through my Apache Web Server.
Any help would be so appreciated!!
I am assuming you have your Apache installed on your Mac under /etc/apache2 folder
If you want to serve your html files and related components, you need to tell apache from where to find your files
So , you need to configure apache so that it can server your files.
first you need to open an terminal from lunch menu then go to the apache2 installation directory
cd /etc/apache2
Then you need to open httpd.conf file and make necessary changes,
sudo nano /etc/apache2/httpd.conf
You will see "DocumentRoot" line/. Change it with your directory where you put your files.
Change also Directory path with yours. (It should be in same config file such as
with
<Document "some_path">
Then you should restart apache server with command
sudo apachectl restart
Now you can try to access your file . you can also check http://localhost to validate
You need to put the files somewhere within the DocumentRoot of your Apache web server, and then you should be able to visit them with http://localhost/ (assuming the index.html file is in the root of the DocumentRoot).
I'm not familiar with the default setting of DocumentRoot on the Mac port of Apache, but you should be able to find that quite easily in the configuration. On Linux that would commonly be found somewhere under /etc/apache2 or /etc/httpd.
There may be further configuration needed if the files expect some sort of server-side module to be activated (e.g. PHP), but it sounds like they are just plain HTML.
Some good answers were given but I think this particular app needed a few extra steps in order to work properly.
The developer got back to me and told me I'd need to install a MAMP solution in order to run the app.
So I installed that and then took the unzipped folder and all its contents in this folder /MAMP/htdocs/
Then when I visit http://localhost:8888/ZMenuMaker/ the app runs without a hitch!
This is a very simple question, but I have struggled for two days to start up my WebObjects on a deployment Debian server. Everything has worked fine so far with Eclipse and Direct Connect, and an apachectl -M shows that the webobjects module (http server) is installed, running and shared. But when I try to run something as simple as a Hello World the browser returns a 404.
My applications are in /usr/share/webobjects/Library/WebObjects/JavaApplications/
Any pointers as to how I should configure (symbolic links and .conf entries) to make this work?
Much appreciated.
Luis
Have you had a look at the Deploying on Linux page on the WOCommunity wiki? If that doesn't help, you may need to post the relevant sections of your httpd.conf here for inspection.
I want to test some code on localhost before uploading to a live site. So I decided to install Apache. I'm running 64bit windows 7 enterprise edition. I downloaded httpd-2.0.64-win32-x86-no_ssl.msi. I installed it under C:\Program Files (x86)\Apache Group\Apache2
I have set domain name and server name to localhost in my installation, and used default value for all other steps. In my configuration file httpd.conf, I have ServerName localhost:80.
I followed everything I can find on online apache installation tutorials. But when I typed in localhost in my browser, I got a 404 error :(
I know it's very hard to diagnose this way, but I just wonder if someone can spot an important step I'm missing.
I'm feeling it could be something to do with my 64bit machine, and the long folder name Program Files (x86). But I have tried to install on C:\Apache directly and failed too (even got an error during installation). Can someone help?
Finally figured it out. Apache service didn't start because another system process was listening to port 80. Refer to these two posts for solutions:
http://forums.zpanelcp.com/archive/index.php/t-5265.html
http://www.softaculous.com/board/index.php?tid=1575&title=Apache_won%27t_start
Good luck to all!
Did you start the service?
Also, you should install XAMPP or WAMPP, which offers Apache, PHP and MySQL support without all the configuration hassle.
If you got a 404 error then either the webserver is running or you failed to start it and have something very wrong with the existing network config on your machine.
The latter is a lot more likely - and you can check this by looking at the logs which it has generated - there should be entries in both the access and error log.
If the problem is the spaces in the path (you'll see an error relating to the documentroot from the entries added to the error_log at startup) then (IIRC) you can either enclose the path in double quotes or use a path for the document root which doesn't have spaces - the content doesn't have to site below the directory you installed Apache into - indeed it's arguable that using a different path is good practice. Note that several versions of mod_fcgid don't like paths with spaces even if you quote them.
I installed redmine on a virtual server (Ubuntu 10.04) with this tutorial:
install guide
Everything seems to be correct, where I stuck is how to make my redmine installation accessible from browser or in other words how to add a subdomain to the existing.
The virtual Server is available under:
lvps46-163-79-1.dedicated.hosteurope.de
which points to a standard htdocs directory.(/var/www/vhosts/default/htdocs/)
My Redmine installation is under:
/usr/share/redmine/
I tried to setup a subdomain with plesk as written in the tut but this failed. Is there an easy (understandable for beginners) way by terminal to make the installation available under:
redmine.lvps46-163-79-117.dedicated.hosteurope.de
Kind regards,
toni
Just to make this complete. I followed the instructions with the apache doku. Unfortunately I couldn´t get the vhost working. I´m now using Mongrel Server on Port 3000 which works for me.
I have installed Bugzilla with Apache on a Windows machine. The Bugzilla web application is set to http://localhost but i have to move it to http://localhost/bugzilla . I think that the Apache server must have a configuration file somewhere but i have little experience with it. Anyone had this problem?
You don't necessarily need to reconfigure Apache, but here's how you would do it:
http://httpd.apache.org/docs/current/platform/windows.html
What you do need to change is the urlbase parameter that tells Bugzilla how to form links to other pages. Yours is probably set to http://localhost/ at present; you probably want it to be http://localhost/bugzilla/.
See http://www.bugzilla.org/docs/4.0/en/html/parameters.html for what you can configure.
If you can't get Bugzilla to load at all, look for a file name params.pl and change the value of urlbase manually. You noramally s