As I said last time, problem descriptions at the level of detail of "having a little trouble" do not call forth detailed suggestions. But once again, I'll guess.
When you set up apache-ssl, you created some sort of certificate it uses to authenticate itself. It may be the built-in "self-authentication" certificate Apache can generate on its own, or it may be one from an external CA such as VeriSign. That certificate has embedded in it information about the server's identity. In moving the server behind the firewall, you either changed something about that setting (like the machine's hostname or FQDN) or you made some element of it unverifiable (say by the DNS problem that was behind your earlier problem with NFS not starting). If my guess is wrong ... try a followup that describes the actual trouble you are having. At 11:39 PM 1/27/02 -0500, Lonnie Cumberland wrote: >Hello All, > >it seems that my firewall is now almost working the way that we want, >but we are having a little trouble getting the Apache SSL secure web >server to work even though we have set up a port forward for port 443 >which is supposed to be for the secure connection I think. > >Does anyone have any ideas? > >The secured SSL Apache web server was working just fine before we >placed it behind the firewall, just to let you know. -- ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA [EMAIL PROTECTED] ---------------------------------------------------------------- _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
