| |
|
Welcome to AstaHost - Dear Guest | |
Replying to Access A Website Created Locally On A Virtual Machine From The Host Machine
Topic Summary
Ahsaniqbal111
Posted 23 April 2012 - 02:32 AM
manuleka
Posted 22 April 2012 - 03:59 AM
Ahsaniqbal111
Posted 18 March 2012 - 10:29 PM
I am desperately waiting to know your research on the problem as mine have led me to no conclusion.will have to re-create this setup when i have time just to find out what's really the issue
manuleka
Posted 18 March 2012 - 09:07 PM
yordan
Posted 15 March 2012 - 08:22 PM
virtual machines are installed exactly the same way as physical machines.
That's why for instance you can perform a PtoV migration, in order to move all your system from your actual machine to a virtual machine.
This means that, in my opinion, if you do simultaneously the installation on both systems (one virtual Linux machine and a physical PC), you boot from the same CD during operating system install and you catch your rpms from the same fileserver, you will reach exactly the same system state, and your LAMP application will fail the same way on both physical and virtual machine.
The only difference between a physical system and a virtual machine is inside the drivers, which are not part in our webhost configuration problem.
manuleka
Posted 15 March 2012 - 06:55 AM
Unfortunately, I was also unable to resolve he same issue on my setup. So eventually, I ended up instally wamp on my primary OS (windows 7) and then I shifted all of my work to it. Now all my development is going on in the primary OS.
Your case seems different. I was working with virtual machines but you appear to be working with actual machines so you got to resolve this issue. I will be very interested in knowing how you resolve it, as it might help me big time for my future needs.
yes actual machines but with Linux HTTP Server running Wordpress... i don't know why and right now i don't have the time to try and do some research on the issue...
Ahsaniqbal111
Posted 28 February 2012 - 10:15 AM
Your case seems different. I was working with virtual machines but you appear to be working with actual machines so you got to resolve this issue. I will be very interested in knowing how you resolve it, as it might help me big time for my future needs.
manuleka
Posted 28 February 2012 - 02:28 AM
first computer runs apache... second computer connected directly (cabled) to it... visit the standard the servers default page and everything seems fine, when i hit the php link (or folder) the page goes simple html with no style.. but my setup was with a Linux Server so have you tried running wordpress from Windows VM or Machine running WAMP Server?
Ahsaniqbal111
Posted 30 January 2012 - 03:48 AM
My problem is a bit different. Though without styles, but I can access the website from the host machine. This should mean that the apache server and the mysql server all are working fine. I could have gone deep into this issue but it is not the primary one. The primary issue is that I cannot login to the administrator section of the website. And I don't have any idea why I am unable to. If this was something related to apache or mysql, the site shouldn't be available for viewing. I can view it (without styles) but I cannot log in to the admin section. And this is making me crazy..To make the guest listen to ANY IP on port 80 or http port, just add this on your config
Listen 80
Instead of adding Listen xxx.xxx.xxx.xxx:80 which while only listen on the same exact IP that you provided.
In order to make wordpress work, you need apache server, Php interpreter and lastly is a mySQL server.
Forget one of them and the whole wordpress system wont work.
Take note that in apache and all linux/unix base system, filenames are case sensitive making "folder" not equal to "Folder" hence producing "file not found" errors which in turn can hang the whole system.
Before attempting other things on that server, I added the Listen 80 line to the httpd.conf file. But after I made the edit, the server failed to start. It gave me some error (I don't remember exactly what that error was) but I remember that when I did some research for the matter, I found that that particular error was generated because of duplicated entries. Simply, it meant that Listen 80 was already added to some configuration file (other than httpd.conf), so I guess I don't need to play around with this issue.
yordan
Posted 27 January 2012 - 02:17 PM
Very nice. I used to add one LISTEN line for each NIC I had, your way is really smart. Thanks.



