Results 1 to 10 of 10
  1. #1
    Newbie
    Join Date
    Mar 2013
    Posts
    8

    Default Captive Portal Broken after Update

    It looks like we had an update last night and are on version 13.1.0.20171010T122129.8b95b52-1jessie . Now captive portal doesn't show the login page and is allowing all traffic through. In report viewer i see the user activity that should require a redirect to the login page and it shows as "captured" with the associated rule but they are not logged in. I even deleted all current authenticated sessions from the captive portal page and its still allowing out all traffic. I opened a ticket with support but want to throw this out there in case other users were seeing this issue.

  2. #2
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    6,075

    Default

    Post the captive rule as it's working on the box I tried.
    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 support@untangle.com

  3. #3
    Newbie
    Join Date
    Mar 2013
    Posts
    8

    Default

    Capture.JPG

    Its just a simple capture everything on this network. No settings changed. The events are showing up in the report center under captive portal as "captured" but there is never any authentication screen.

  4. #4
    Newbie
    Join Date
    Mar 2013
    Posts
    8

    Default

    Authentication settings:
    Capture.JPG

  5. #5
    Newbie
    Join Date
    Mar 2013
    Posts
    8

    Default

    Definitely something up with the captive portal redirect-when I manually enter the captive portal address in a device I get the login page and I can login with my AD account. So it’s not AD connector. I bet something in the update broke the captive portal so that it doesn’t redirect properly. It’s trying to go to the default http/https ports (80/443) and not the ones setup in my network services tab. I can even see my firewall blocking it these devices trying to get to the default http port (which is what is supposed to do).

  6. #6
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    16,489

    Default

    Post a screenshot of what you see on the client.
    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 support@untangle.com

  7. #7
    Newbie
    Join Date
    Mar 2013
    Posts
    8

    Default

    The clients don't show anything- they allow browsing and they show as "captured" in the report viewer for captured events in captive portal reports. Also they are not showing up in the "Active Sessions" area of the captive portal app. Most browsing is allowed but for instance gmail on ym phone won't work. However if i manually type in the captive portal url then I can enter my credentials and my client shows up correctly and everythign works. Its the redirect to the portal that seems broken and i bet its because i use different ports for http/https

  8. #8
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    16,489

    Default

    If you have a support subscription I would open a support case.

    I doubt it has anything to do with http/https ports. If you are browsing the web its not getting the 301 redirect - it doesn't matter where the 301 redirect would send them. Also I see no way a "captured" session would still reach the server, that essientially means that the session is endpointed, no data is sent to the server, much less is the response relayed to the client.

    I would make sure that you are looking at the correct session in reports. I would not look at them "generally"
    Visit a specific site, find that session, look at the report for that specific session. You can use wget to avoid any caching confusion.
    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 support@untangle.com

  9. #9
    Master Untangler
    Join Date
    Dec 2010
    Location
    Providence, RI
    Posts
    145

    Default

    I actually have an open ticket about a similar but not exact issue, and they may be related.

    I use AD Connector and Captive portal together, and I'm finding that the hosts table doesn't release captive portal logins, even though you don't see them in captive portal.

    @mccannit - If you go to the hosts table, and select the affected computer, do you see a username entry either for Directory Connector or Captive portal, and if you do, are they the same username?

  10. #10
    Newbie
    Join Date
    Mar 2013
    Posts
    8

    Default

    Turns out it was exactly what I suspected. To quote Untangle Support-
    "We have found a bug relating specifically to Captive Portal when the Service ports are changed"

    They immediately issued a fix for my system and everything it working again.

    yotefn- since my system is working now I don't think i can help you out anymore. I would recommend you contact support.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2