Errors, looking for help

[BBScience]

I am trying to install CGIProxy and PHProxy onto my account, however I am recieving a bunch of errors or it just doesnt work. Can anyone shed some light on my situation? All permissions are set correctly, and the files work on my other server. CGIProxy has the correct perl route (based on the FAQ thread).

http://www.freepgs.com/vineman/phproxy
http://www.freepgs.com/vineman/cgi-bin/nph-proxy.cgi

[Ben]

Just a quote from the Terms of Service should solve all your problems...

FreePgs.com membership will be revoked if any of the following activities occur:
l.) Accounts containing Proxy or Anonymizer scripts

Edit: Apparently, you were approved by admin in another post, so I'll help anyway.

For PHProxy, the errors are just Strict errors. Change your PHP error settings to all but E_Strict and you'll be fine. Strict errors are nothing more than recomending working with features that may not be supported in future versions of PHP.

I don't know what would be causing the 500 Error on the other one, sorry.

[sixthcrusifix]

I am trying to install CGIProxy and PHProxy onto my account, however I am recieving a bunch of errors or it just doesnt work. Can anyone shed some light on my situation? All permissions are set correctly, and the files work on my other server. CGIProxy has the correct perl route (based on the FAQ thread).

http://www.freepgs.com/vineman/phproxy
http://www.freepgs.com/vineman/cgi-bin/nph-proxy.cgi

I dunno what your problem is but you need to remove that first link ASAP, I clicked that and immediately firefox started opening in a million windows and I had to open the task manager and quit it.

[admin]

In order for NPH* scripts to work, you must change Perl to "Direct/CGI" in the Options panel and wait 5 minutes.

Not all scripts are compatible with mod_perl.

You also do not need to chmod the files to 777

Thank you,
FreePgs.com Admin

[BBScience]

Alright thanks for the PHProxy help, but now I've found a new problem Whenever you try to go to a link, it spits out "
Fatal error: Non-static method PHProxy::decode_url() cannot be called statically in /fpgs/fpgshttpd/vineman/phproxy/PHProxy.class.php on line 276". Anyone?

Also now http://freepgs.com/vineman/cgi-bin/nph-proxy.cgi is a blank page (after switching to Direct/CGI)

[admin]

Please try the CGI script again.

There were additional spaces on the first few lines (of the code)

Code Select Expand

use strict ;
use Socket ;

Changed to

Code Select Expand

use strict;
use Socket;

As for the PHP script, others are using the 0.3 version on this machine.  Be sure you have uploaded the unmodified files to the system in ASCII (if uploading from a Windows-based machine).  If the script does not function with PHP5, we can move these two scripts over to the Plesk system [where they are allowed anyway]

Also, please change your Error Reporting setting back to the default (All But Notice & Strict) and try to access the PHP script again in 5 minutes.  I have chmod'd your PHP files back to the default 644.  They do not require 777 to operate.

As for what is allowed (regarding the Terms of Service entry) - That was added due to one particular PHP-based proxy script which hogs cpu cycles when being used.  The nph-proxy.cgi does not appear to cause this problem as it is much more efficient than the "defilter.php" script.  Since the "3:l" term contradicted with the text on item "5", "3:l" has been removed.

Thank you,
FreePgs.com Admin

[BBScience]

I love you admin 

[goldox]

Alright thanks for the PHProxy help, but now I've found a new problem Whenever you try to go to a link, it spits out "
Fatal error: Non-static method PHProxy::decode_url() cannot be called statically in /fpgs/fpgshttpd/vineman/phproxy/PHProxy.class.php on line 276". Anyone?

Also now http://freepgs.com/vineman/cgi-bin/nph-proxy.cgi is a blank page (after switching to Direct/CGI)

I am using PHProxy 0.4, the same error was found. How can I do?

[stevensol]

I thought freepgs accounts did not offer CGI/perl??

[brainiac744]

They did long ago. (for example back in march when this topic was started...)

I think people who had it turned on back then might still have it on? Can't say for sure...