Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 2 subscribers
  • Views 1879 views
  • Users 0 members are here
Options
Suggested
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

ChaimKrause
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
    I have an idea. I have packet filtering allowing any:https to get to my DMZ. What other packet filtering do I need to allow? Maybe something from the DMZ out that I ain't already doing? I am at work now and can get to the HTTP server just fine, but not the HTTPS. The behavior seems like the packets are getting in, but not back out.
Reply
  • 0
    I have an idea. I have packet filtering allowing any:https to get to my DMZ. What other packet filtering do I need to allow? Maybe something from the DMZ out that I ain't already doing? I am at work now and can get to the HTTP server just fine, but not the HTTPS. The behavior seems like the packets are getting in, but not back out.
Children
  • 0 in reply to ChaimKrause
    Tautologically, that's all there is for HTTPS; the log would show what's getting blocked (put a Deny Any Log rule at the bottom of the rules to be sure...)

    Maybe you should disable HTTPS administration of the firewall??