Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 38 subscribers
  • Views 1812 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

The captive portal shows up repeatedly

Rodrigo Silveira2

Hello, I am facing a weird behaviour with the Captive Portal, when it come up on the first time and I enter my login information, instead of redirecting me to the page I was requesting the browser presents me the Captive Portal page again and I have to enter my login information again to get logged in.

Seeing on Log Viewer and the first time I enter my credentials there is no log entry regarding the user or computer IP I am entering.

Anyone has experienced this behaviour?

SFOS 18.0.4 MR4



This thread was automatically locked due to age.
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to the Community. 

    Can you put the access_server process in debugging, replicate the issue, and provide access_server logs in debugging. 

    Follow this KB Article to SSH into the XG firewall: Sophos XG Firewall: How to SSH to the firewall using PuTTY utility

    Select Option 5 (Device Management) > Option 3 (Advance Shell)

    Run this command to put the access_server service in debug:

    • service access_server:debug -d -s nosync

    Please check out the following KBA to locate and capture the logs: Sophos XG Firewall: Where to find log files?

    Once you capture the access_server logs in debugging, run the same command to put access_server service in normal running mode. 

    Run this command to check service status :

    •  service -S | grep access_server

    SFVUNL_VM01_SFOS 17.5.11 MR-11# service -S | grep access_server
    access_server RUNNING,DEBUG

    Run the following command to put the csc service in debug: csc custom debug

    Note: Run the same command to remove the service from debugging. 

    Run the following command to collect csc logs: tail -f /log/csc.log 

    Please PM me the logs and username of the user you try to replicate the issue with.

    Thanks,

Unfiltered HTML