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.

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
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
0 ChaimKrause over 19 years ago

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.
Cancel
Vote Up 0 Vote Down

Cancel
0 SecApp over 19 years ago 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??
Cancel
Vote Up 0 Vote Down

Cancel
0 DrMabuse over 19 years ago

You should take a look at knowledge-base-article 111678 on www.astaro.com/kb about DNAT. Also make shure you move away the webadmin-port (443) in System > WebAdmin Settings, so it does not conflict with your DNAT rule.
Cancel
Vote Up 0 Vote Down

Cancel
0 ChaimKrause over 19 years ago in reply to DrMabuse

I have seen that article and my setup conforms to that setup. I moved the webadmin off of 443, but that has not solved my problem. HTTP continues to be fine, and HTTPS continues to not work.
Cancel
Vote Up 0 Vote Down

Cancel
0 Simon Shaw over 19 years ago in reply to ChaimKrause

Are you using transparent HTTP proxy on the ASL?

Try adding the DMZ server to the HTTP proxies "Skip source/destination networks:" list.

Make sure you have a packet filter rule:

LAN HTTPS DMZ_Server Allow
and vice versa.

Is the DMZ on public or private IPs?
Cancel
Vote Up 0 Vote Down

Cancel
0 Prometejas over 19 years ago in reply to Simon Shaw

I have the same problem - transparent proxy - http works fine, but https not - where is the problem?
Cancel
Vote Up 0 Vote Down

Cancel