Guest User!

You are not Sophos Staff.

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

Sophos connect cliente

Hello everyone

I have the problem in the sophos connect client when making an SSL configuration with OTP authentication, the client establishes the communication but does not authenticate, and is simply in the state of waiting to establish the connection, if I make an ipsec (remote access) connection with the same user, this procedure works.

Someone can help in the sense of being able to simply use the sophos connect client to establish the two types of VPN (IPSec remote access and SSL VPN remote access)

Below is the contents of the .pro file I use to make the SSL connection

[

  {

"display_name": "VPN-SSL",

"gateway": "vpn.mydomain.pt",

"user_portal_port": 4434,

"otp": true, "2fa": 1,

"auto_connect_host": "",

"can_save_credentials": true,

"check_remote_availability": false,

"run_logon_script": false

  }

]

Thank you



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

    Hi ,

    Thank you for reaching out to the Community! 

    Have you turned on OTP for SSL VPN from Authentication > One-time password > Settings > Enable OTP for facilities? 

    If yes, I would advise you to 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

    Thanks,

Reply
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to the Community! 

    Have you turned on OTP for SSL VPN from Authentication > One-time password > Settings > Enable OTP for facilities? 

    If yes, I would advise you to 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

    Thanks,

Children
  • Hi Harsh Patel

    I thank you in advance for your brief help on the subject. after having done as you mentioned the service in dibug mode, when you see the status of the service it is stopped, I tried to restart and it didn't work, it failed to start, I will have to restart the apliance to see if the service starts normally, because it didn't pass head that the service could be below, because it authenticates some users and not others. Thanks and I'll be back to you with news