Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: Configuring Apache after VM move |
|
Author |
|
rob901
Joined: 19 Nov 2015 Posts: 1 Location: USA, Boston
|
Posted: Thu 19 Nov '15 17:38 Post subject: Configuring Apache after VM move |
|
|
Hello All,
I am 100% new to Apache and fairly new to system administration in general so I apologize if this is a rookie question. My company recently purchased another company and we are in the process of moving their stuff to our data center. They shipped me a copy of their website(VM on a hard drive, so 21st century). The VM is running Debian 6.0.10 and Apache 2.2.16.
So far I have changed the internal IP address of the VM. When I visit the IP in a browser I do seem to get to the server but get a message that 'the web site has not been uploaded yet, or is not configured to respond at this address.' Seems like I need to tell Apache to respond to the new internal address. I am guessing there is also more that I need to do but being completely green at all of this I am unaware of what is required. Any help is greatly appreciated.
Thanks,
Rob
Boston, MA |
|
Back to top |
|
jimski
Joined: 18 Jan 2014 Posts: 196 Location: USSA
|
Posted: Fri 20 Nov '15 10:43 Post subject: |
|
|
First open httpd.conf and check these directives and make sure they correspond with your new VM setup, domain and port.
ServerRoot
ServerName
Listen
Then log in to the vm and start Apache and open a browser on the vm and point it to the localhost or to 127.0.0.1 , if you use different port than 80, for example 8080, then point the browser to this port localhost:8080 . If the vm doesn't have GUI then you can use command line browser.
If you can access the website then Apache works fine and the problem is with the firewall. And if you can't access it then the problem is with Apache. |
|
Back to top |
|
|
|
|
|
|