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 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

Reply

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

Children

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