This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HTTP fine, but HTTPS won't work

I have apache running in the DMZ. I can view standard web pages via HTTP from the internal network, but HTTPS doesn't connect. I can't get a connection. I have set up my HTTPS NAT and packet filter to parallel my HTTP NAT and packet filter rules. How should I go about troubleshooting this?

This thread was automatically locked due to age.

Parents

0 KKnecht over 19 years ago

Try to connect to your Apache directly from DMZ to ensure HTTPS is up and running.

Why do you need NAT rules ? Aren't your services connect to 80 / 443 ?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 KKnecht over 19 years ago

Try to connect to your Apache directly from DMZ to ensure HTTPS is up and running.

Why do you need NAT rules ? Aren't your services connect to 80 / 443 ?
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 ChaimKrause over 19 years ago in reply to KKnecht

Yes, https is up and running.

I'n not sure what you are asking about the NAT rules and services. I have NAT rules because the web server is in the DMZ and I want it to served up web pages.
Cancel
Vote Up 0 Vote Down

Cancel