Thanks for that hint - I didn't think to check log files since it didn't start. error.log said the app's log file couldn't be created so I updated that location to match my previous values. Victim of cut-and-paste-itis. But I'm back to 'can't establish a connection to the server at...' when trying to reach the SSL'd site from Firefox. With apache2's stop and start I continue to see: apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName (sic) This is Ubuntu 6, and it automatically put a hosts entry of 127.0.1.1 to the machine's name which explains the odd IP, but what I have for the VirtualHost *:443's ServerName is also sitting in the hosts file on the line for 127.0.0.1, just like the PHP site's name which works fine. I also tried commenting out the VirtualHost *:80's entry in case there was forwarding confusion, but that tag actually works forwarding the http to https. The only intelligent question I can ask is: could Apache2 be confused because I have an https proxied to an http://localhost:3000/ ? I wouldn't think so, but maybe ProxyPass/Reverse forwards the encrypted request instead of decrypting it and passing it along..? Thanks again, -Chris Joshua Slive said: > On 8/24/06, Chris Dagnon <chris.dagnon@xxxxxxxxxxxxxxxx> wrote: >> Hello all, >> >> I've been using a site configured to Proxy requests to another port for >> one ServerName and another on the same Apache2 directly serving PHP >> pages. >> That's been working fine. But now I want to add SSL to the proxied >> pages >> and it isn't going so smoothly. I had hints from a coworker and tried >> integrating that with my existing vhost files, but even at the best of >> times Apache2 fails startup. > > What does the error log say? > > Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|