If you have PhpDig 1.6.5 working in full (including external binaries) on some other configuration, please post the configuration so that it can be added to the list.

If you have found a configuration where PhpDig 1.6.5 does not work in full, please post this also. For troubleshooting questions, please post in the Troubleshooting (http://www.phpdig.net/forumdisplay.php?forumid=22) forum.

Thanks.

This problem dealt with external binaries and the failure of the exec command in PHP 4.2.2.
Originally posted by lelandv
...
Just for information (in case anyone else comes across similar problems).. phpdig will NOT work on PHP version 4.2.2 -- this was the cause of the problems. Upgrading to 4.3.4 solved the problem. All working now!
...

This problem dealt with the inability to crawl pages residing on the same CGI server as PhpDig.
Originally posted by rafarspd
...
My ISP uses two servers, one for normal html (called the homepages server) and one dedicated to CGI, PHP, MySql etc.

PhpDig resides on the CGI server.
It can crawl any site on the homepages server but fails on any site on the CGI server.
This has been proven by installing PhpDig under my own user name account in addition to the www.rafars.org account.

Here is the reply from my ISP:-

cut -----
This is normal, the CGI platform is a loadbalanced cluster of servers, it is therefore not possible to connect back to "itself" on the loadbalanced address.

We are investigating other possibilities to enable this for the use of htdig etc although there is no ETA for this.
---- cut

So at least an answer from the ISP.

I say again:-
NOT A PHPDIG PROBLEM but an ISP CONFIGURATION PROBLEM.
...