Skip to main content

Why Force HTTPS Redirect not active?


1 comment

  • cPRex Jurassic Moderator

    Hey there!  There are two possible reasons this could be happening.  The first, is that the addon domain itself is controlled by the associated subdomain.  You'll see this warning when you hover over the "?" in the "Force HTTPS" column:

    The second issue could be that AutoSSL is not yet working for the domain, which would show this error when hovering over the triangle logo in the "Force HTTPS" column:

    Do you see either one of those happening on the system?


Please sign in to leave a comment.