Thanks Kiriki! Tbh, I really don't want to risk breaking anything else by moving pound.
But I did follow your advice to remove HeadRequires, which initially got the site back up - internally. That is, 192.168.0.161:80 was being directed by Pound to 192.168.0.160:8080. Then I added HeadRequires back, restarted Pound, and oddly, the site was again visible - internally. But after restarting Pound after a reboot, internally I get the 'Service unavailable' message. So I removed the HeadRequires, but this time the site was not internally visible - with no 'Service unavailable message' too. Even when the site was temporarily visible via 192.168.0.161, externally visitors were seeing the message: 'The server at xxxxxxx is taking too long to respond...'. Apache is configured to listen to the backend address: 192.168.0.160:8080 - not 161:80, so no interference there. Thanks for your help! I'll keep plodding on! ----------------------------------------------------------------------------------------------------------------------- Send big files for free. Simple steps. No registration. Visit now http://www.nawelny.com -- To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED] Please contact [EMAIL PROTECTED] for questions.
