I have installed Ubuntu Server 10 on a virtual machine (VMWare) and I have set up a LAMP stack. Everything runs fine when I go to "mysitename" in Firefox on the linux virtual machine, but when I try to access it on my windows machine, it only gives me the HTML in my .php file, and does not execute the PHP. Can anyone provide some suggestions? I'm guessing it will be an apache setting, but I'm not sure.
What URL are you accessing from your Windows machine? Are you sure that the PHP file is actually interpreted when you're accessing it from the Linux Guest?
Related
Earlier it worked without any problems.
But when I installed php and made the configurations I tried to open phpMyAdmin on the browser and then I realized the Apache web server wasn't running.
I took these steps:
Tried to check for any configuration problems but there weren't any.
I changed the port.
I re-downloaded but it didn't work again (I configured and changed the port correctly after re-downloading).
below are some info about versions of xampp and phpthis is the info about versionsand this is my xampp version
I'm trying to run a simple Laravel project inside a Vagrant (VirtualBox) VM. The guest is Ubuntu 14.04 x64, and the host is Windows 7 x64. I've set up port forwarding (8000 on host to 8000 on guest), but when I run php artisan serve, though I get a message stating that the server is running on port 8000, when I visit localhost:8000 on my host machine, Chrome tells me 'this webpage is not available'. There are two complications:
First, if I use curl from inside the VM, I receive the correct page contents - so it appears the server is working fine.
Second, if I run a Python web server using python -m SimpleHTTPServer on the same VM, I can access it fine on my host OS. Visiting localhost:8000, I see the directory contents listed. So it appears the port forwarding is working fine.
I tried deleting the public/.htaccess file in the Laravel project, to no avail. I'm no PHP expert, and this problem is hard to Google! Any pointers would be appreciated.
After reading this question I tried
php artisan serve --host 0.0.0.0
And it works fine now.
I have a php webserver setup running in a remote website; lets call it remote.com
Have the wamp installed in local windows machine ( localhost ) and did the necessary xdebug configuration and netbeans installed. Now my doubts are:
My IP is not static IP but dynamic one. So specifying this in the remote server's php.ini will work?
To debug the php file which resides in the remote server, should I have the same exact copy of source file be available in localhost too? What will happen if there is small changes, lines mismatch etc.
What happens in the background technically?
Thanks in advance.
I am new to Windows IIS and I need to run a php/mysql application on it. For local php development on windows, I have found WAMP to be the easiest.
But can WAMP be used in this case instead of installing php and mysql separately ?
This needs to be done on an ec2 Windows 2003 instance. So far, I have already tried installing WAMP and setting up apache to listen on port 8080 instead of 80. From inside the remote desktop, both IIS and WAMP work properly in parallel on their respective ports.
However, when I try to connect from another computer using the ip address http://184.**.***.***, IIS works fine serving the default web page but cannot connect to apache on http://184.**.***.***:8080.
Is it possible to use WAMP at all for this purpose and if yes, would there be any disadvantages in using it instead of installing php/mysql seperately ?
Edit :
I dont know if this is a problem of blocked 8080 port. To verify this I stopped IIS and configured apache to listen to 80. Even then http://184.**.***.*** doent show the WAMP homepage. IS anything needed to be configured in IIS ?
RESOLVED :
Added the port 80 in Windows Firewall Exceptions and it started working.
Also, its necessary to select "Put Online" in the WAMP tray otherwise it gives a forbidden response as suggested by some answers.
Thanks
I haven't used EC2 in this way before, but broadly speaking, I'd encourage you to use the same server for development and production environments if at all possible - the installation effort can be a bit of a pain, but it's nothing compared to developing an app locally and then finding an IIS configuration issue causes it to break on production.
This approach also lets you keep your PHP configurations in source code control - php.ini and any modules you're using - and automatically deploy them alongside your application; again, forgetting to deploy the correct PHP.ini usually makes your application do crazy things...
So, your choices appear to be:
- switch off IIS and have WAMP listen to port 80. Not sure WAMP is designed for production level traffic, but in the past, I've run low-traffic public websites in this way.
- work out why port 8080 is blocked, and if it can be unblocked. This would still require you to run your website on an unusual port, which makes for ugly and hard-to-communicate URLs.
- install PHP on your IIS instance. One benefit of having installed WAMP is that MySQL should already be up and running, and the basic PHP installation should also be there; getting PHP to run on IIS is no longer a dark art ([http://php.iis.net][1])
For my money, I'd go for the latter option...IIS is a production quality server, and it's clearly what Amazon want you to use in this instance.
Of course, running IIS on your development environment may be a problem.
Have you put the server online? Think it is offline by default, meaning it's only accessible from your local machine. It's an option in the systray menu to put it online.
If I remember well, there is an option "go public" (or "put online") on the system traya icon of wamp.
This option modifies the httpd.conf to authorize public access.
You should give a try.
On a side note, you can make php work with IIS. This is another option to help you manage your server. (Mysql and Php have to be installed separatly but, this is very easy to do as far as I remember :) )
I've first installed the WAMP server on my system.
It used http://localhost to show my files in the www directory.
But then I installed visual studio 2008. It too uses the http://localhost/
But it doesn't show up. What should I do?
I assume you mean IIS? Cassini (the build in "debugging" webserver) uses high ports when you fire an app up. Either way you need to configure either WAMP or IIS to listen on a port other than port 80, then you can access one on http://localhost/ and one on http://localhost:MYPORT/.
VS uses it's own development server, and usually VS starts his own server in debug mode, and there isn't a common server executable. Since VS needs to start it's own server in debug mode to test .NET driven applications, it can't show your WAMP applications because it usually runs in other port. Also, you can't run PHP applications under VS.
Try looking at server connection that the browser brings you at the application URL.