Trying to access website over SSH, apache is sending unparsed PHP

dhelyar · 11-13-2010, 11:04 PM

Ok, the server is:

Ubuntu 9.10
Apache2
Php5

All is working if I view the server web pages using VNC, however if I try and access the web page over SSH using the following .ssh/config forwarding:

LocalForward 8000 localhost:80

and the web address http://localhost:8000

HTML files show up fine in browser, however PHP files are not parsed and are interpretted as downloadable files rather than view in browser.

Thanks for any advice

EDIT:

Ok I just tried using port 80 instead of 8000, and this parses the PHP fine, however this required me to run ssh client as root, as well as turn off my local web server.

Two things I'd just prefer not do, and also I imagine there must be a way of fixing this on the server apache config?

paulsm4 · 11-14-2010, 01:27 AM

Hi -

You're exactly correct:
1. Apache is basically working, and PHP is working

2. The only problem is that port 80 is configured to "understand" php, and port 8000 isn't.

3. All you have to do is to modify your Apache configuration on the server.

For example, in my Ubuntu 9.10 server, I have the following:

Code:

/etc/apache2/mods-enabled/php5.conf =>
<IfModule mod_php5.c>
  AddType application/x-httpd-php .php .phtml .php3
  AddType application/x-httpd-php-source .phps
  ...

/etc/apache2/mods-enabled/php5.load =>
LoadModule php5_module /usr/lib/apache2/modules/libphp5.s

... and, in my apache2.conf ...

/etc/apache2/apache2.conf =>
...
# Include module configuration:
Include /etc/apache2/mods-enabled/*.load
Include /etc/apache2/mods-enabled/*.conf

# Include all the user configurations:
Include /etc/apache2/httpd.conf

# Include ports listing
Include /etc/apache2/ports.conf
...

j-ray · 11-14-2010, 04:17 AM

You could create a virtual host that listens n port 8000 or whatever. In /etc/apache2/sites-available you find a default configuration you can copy and symlink to sites-enabled directory. Put a
Listen 8000
above and give the virtual host a name and restart the server...

http://httpd.apache.org/docs/2.2/vhosts/

paulsm4 · 11-14-2010, 04:15 PM

Hi, dhelyar -

You *may* use vhosts. But you don't *have* to.

The issue of whether or not .php files are interpreted or should be more or les *independent* of whether you're using a vhost or not.

The point I was trying to make in my response was to give you an example solution that would work in *all* situations, *regardless* of whether you used vhosts or not.