Announcement

Collapse
No announcement yet.

Webpage not available

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Webpage not available

    I've had some new devices rolling into BYOD recently that experience a
    "Webpage not available"
    ERR_NAME_NOT_RESOLVED

    I believe it's due to DNS privacy settings set as "Automatic" on the devices I'm seeing.

    The webpage at http://untangle.example.local/capture host=connectivitycheck.gstatic.com& could not be loaded.

    Is there a recommended exception to resolve this issue, or am I looking at a configuration issue on my end?

    SSL inspector, or web filter?

    Thank you.

    EDIT- In the meantime I've manually added the username to the device in devices, but looking for a way to make it so users can reach captive portal more easily.

  • #2
    Most likely they are running DNS over HTTPS. You may have to check the sessions blocked and allow those sessions through captive portal.
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email [email protected]

    Comment


    • #3
      Thanks, I was thinking if I set them to pass, then it wouldn't trigger a response for the portal to present itself.
      The block rule triggered was "capture unauthenticated" - I'm not seeing any issue present in the report.

      I ticked this setting - "Always use HTTPS for the capture page redirect"

      Maybe that will hook me up?

      Comment

      Working...
      X
      😀
      🥰
      🤢
      😎
      😡
      👍
      👎