Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 1 subscriber
  • Views 1721 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

allowing actual HTTPS traffic

JFCSDave
Hi everyone-
I am currently using a Demo unit of the ASG 320. So far we are quite happy but are experiencing some issues. One that is particularly strange is that each time I go a site that is HTTPS secured (twitter, the support site here, ect) that asks me to trust the certificate and while I accept it, the site does not completely render properly. I was able to make an exception for Astaro.com, but I obviously can't do that for each https site on the internet.

can someone provide me with some guidance ?

Thanks,


This thread was automatically locked due to age.
Parents
  • 0
    The second image indicates that, when you did the initial installation, you named the ASG something like mail.domain.com, and that, from inside your network, you're accessing it like https://192.168.1.1:4444/.  That is, you aren't accessing it by its actual name.  You can just ignore that and proceed, or you can add an entry to internal DNS that resolves mail.domain.com to 192.168.1.1.

    Does that resolve this issue?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    The second image indicates that, when you did the initial installation, you named the ASG something like mail.domain.com, and that, from inside your network, you're accessing it like https://192.168.1.1:4444/.  That is, you aren't accessing it by its actual name.  You can just ignore that and proceed, or you can add an entry to internal DNS that resolves mail.domain.com to 192.168.1.1.

    Does that resolve this issue?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    The second image indicates that, when you did the initial installation, you named the ASG something like mail.domain.com, and that, from inside your network, you're accessing it like https://192.168.1.1:4444/.  That is, you aren't accessing it by its actual name.  You can just ignore that and proceed, or you can add an entry to internal DNS that resolves mail.domain.com to 192.168.1.1.

    Does that resolve this issue?

    Cheers - Bob


    Yes-thank you so much for your help
    [[:)]][[:)]]
Cookie Information Banner