Submitted by s0h0punk on Mon, 10/26/2009 - 16:09
ok, here goes... I have a debian 4 machine running virtualmin & vmware server. I have a virtual server set up to 'proxy' to a local virtual server running ubuntu desktop & webmin (see screen2.jpg) however, when you surf to the domain of the virtual host, you get the error as seen in screen1.jpg.
As you can see in the error message, it comes from the 'host' server.
When I use the host's firewall to forward port 81 directly to port 80 of the virtual host, it works flawlessly.
if you need more details, let me know!
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Mon, 10/26/2009 - 19:25 Comment #1
Is that error coming from the proxy system , or the remote system?
You should be able to tell by checking logs on both systems ..
Submitted by s0h0punk on Tue, 10/27/2009 - 01:26 Comment #2
the error comes from the system that's supposed to proxy the connection to the local server. you can also tell, looking at the error that it's a debian system. The proxy server runs Debian while my local servers are running ubuntu.
Submitted by s0h0punk on Tue, 10/27/2009 - 01:30 Comment #3
sorry for triple post - I got an internal server 500 error while posting so I refreshed... a couple of times :-)
Submitted by s0h0punk on Tue, 10/27/2009 - 01:30 Comment #4
sorry for triple post - I got an internal server 500 error while posting so I refreshed... a couple of times :-)
Submitted by JamieCameron on Tue, 10/27/2009 - 11:05 Comment #5
If you put an index.html file in the public_html directory of the proxy domain, does it show up when you access the website?
Submitted by s0h0punk on Tue, 10/27/2009 - 14:59 Comment #6
nope
index.html is in place - nothing changes...
I'm seeing some errors concerning proxy_html
I've tried googling it, didn't get me any usable info... I'm quite new at all this stuff...
here's the log from the 'proxy' server
[Mon Oct 26 21:50:56 2009] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Mon Oct 26 22:11:28 2009] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Mon Oct 26 23:02:58 2009] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Mon Oct 26 23:07:33 2009] [warn] proxy: No protocol handler was valid for the URL /vhcs2/. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Tue Oct 27 03:38:33 2009] [warn] proxy: No protocol handler was valid for the URL /status.html. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
Submitted by JamieCameron on Tue, 10/27/2009 - 23:23 Comment #7
What gets logged to the logs/access_log file under the domain's home directory on the proxy system?
Submitted by s0h0punk on Sat, 10/31/2009 - 05:25 Comment #8
this is apache access log for that domain...
94.224.117.114 - - [31/Oct/2009:11:20:15 +0100] "GET / HTTP/1.1" 403 384 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.27 Safari/532.0"94.224.117.114 - - [31/Oct/2009:11:20:15 +0100] "GET /favicon.ico HTTP/1.1" 403 395 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.27 Safari/532.0"
and a lot of dfind errors and errors for phpmyadmin etc (which is not installed) But I guess that has nothing to do with the proxyfying not working
94.23.220.167 - - [30/Oct/2009:16:55:28 +0100] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 408 "-" "-"92.68.249.36 - - [30/Oct/2009:18:50:00 +0100] "GET //phppgadmin//scripts/setup.php HTTP/1.1" 403 411 "-" "Plesk"
92.68.249.36 - - [30/Oct/2009:19:32:59 +0100] "GET ///scripts/setup.php HTTP/1.1" 403 399 "-" "Plesk"
92.68.249.36 - - [30/Oct/2009:20:15:59 +0100] "GET //admin//scripts/setup.php HTTP/1.1" 403 406 "-" "Plesk"
92.68.249.36 - - [30/Oct/2009:20:58:55 +0100] "GET //admin/pma//scripts/setup.php HTTP/1.1" 403 410 "-" "Plesk"
92.68.249.36 - - [30/Oct/2009:21:41:42 +0100] "GET //admin/phpmyadmin//scripts/setup.php HTTP/1.1" 403 417 "-" "Plesk"
92.68.249.36 - - [30/Oct/2009:22:24:22 +0100] "GET //db//scripts/setup.php HTTP/1.1" 403 403 "-" "Plesk"
92.68.249.36 - - [30/Oct/2009:23:07:21 +0100] "GET //dbadmin//scripts/setup.php HTTP/1.1" 403 408 "-" "Plesk"
92.68.249.36 - - [30/Oct/2009:23:50:12 +0100] "GET //myadmin//scripts/setup.php HTTP/1.1" 403 408 "-" "Plesk"
92.68.249.36 - - [31/Oct/2009:00:32:57 +0100] "GET //mysql//scripts/setup.php HTTP/1.1" 403 406 "-" "Plesk"
92.68.249.36 - - [31/Oct/2009:01:15:44 +0100] "GET //mysqladmin//scripts/setup.php HTTP/1.1" 403 411 "-" "Plesk"
92.68.249.36 - - [31/Oct/2009:01:58:43 +0100] "GET //phpadmin//scripts/setup.php HTTP/1.1" 403 409 "-" "Plesk"
92.68.249.36 - - [31/Oct/2009:02:41:47 +0100] "GET //phpMyAdmin//scripts/setup.php HTTP/1.1" 403 411 "-" "Plesk"
92.68.249.36 - - [31/Oct/2009:03:24:49 +0100] "GET //phpmyadmin//scripts/setup.php HTTP/1.1" 403 411 "-" "Plesk"
212.241.210.76 - - [31/Oct/2009:03:32:20 +0100] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 408 "-" "-"
92.68.249.36 - - [31/Oct/2009:04:07:37 +0100] "GET //pma//scripts/setup.php HTTP/1.1" 403 404 "-" "Plesk"
92.68.249.36 - - [31/Oct/2009:04:50:31 +0100] "GET //web/phpMyAdmin//scripts/setup.php HTTP/1.1" 403 415 "-" "Plesk"
92.68.249.36 - - [31/Oct/2009:05:33:15 +0100] "GET //web//scripts/setup.php HTTP/1.1" 403 404 "-" "Plesk"
Submitted by JamieCameron on Sat, 10/31/2009 - 15:03 Comment #9
So it looks like proxying is not happening at all ..
What does the domain's Apache config file at /etc/apache2/sites-enabled/domainname.com.conf contain?
Submitted by s0h0punk on Sat, 10/31/2009 - 19:59 Comment #10
this is the conf file
<VirtualHost 91.121.221.32:80>ServerName zeroproxy.co.cc
ServerAlias www.zeroproxy.co.cc
ServerAlias webmail.zeroproxy.co.cc
ServerAlias admin.zeroproxy.co.cc
DocumentRoot /home/zeroproxy/public_html
ErrorLog /var/log/virtualmin/zeroproxy.co.cc_error_log
CustomLog /var/log/virtualmin/zeroproxy.co.cc_access_log combined
ScriptAlias /cgi-bin/ /home/zeroproxy/cgi-bin/
DirectoryIndex index.html index.htm index.php index.php4 index.php5
<Directory /home/zeroproxy/public_html>
Options -Indexes +IncludesNOEXEC +FollowSymLinks
allow from all
AllowOverride All
</Directory>
<Directory /home/zeroproxy/cgi-bin>
allow from all
</Directory>
ProxyPass / http://192.168.227.129/
ProxyPassReverse / http://192.168.227.129/
<Proxy *>
allow from all
</Proxy>
RewriteEngine on
RewriteCond %{HTTP_HOST} =webmail.zeroproxy.co.cc
RewriteRule ^(.*) https://zeroproxy.co.cc:20000/ [R]
RewriteCond %{HTTP_HOST} =admin.zeroproxy.co.cc
RewriteRule ^(.*) https://zeroproxy.co.cc:10000/ [R]
</VirtualHost>
Submitted by JamieCameron on Sun, 11/01/2009 - 17:49 Comment #11
Ok, I think the real issue comes from the error line :
[Mon Oct 26 21:50:56 2009] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.Go to Webmin -> Servers -> Apache Webserver -> Global Configuration -> Configure Apache Modules , make sure both proxy and proxy_http are checked.
Submitted by s0h0punk on Mon, 11/02/2009 - 00:30 Comment #12
wow thanks a lot that actually fixed my problem!
I've known that was the issue from the very beginning, but couldn't find where to include/enable it!
thanks a million!