Remote access Connection component error

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Remote access Connection component error

L3 Networker

Unable to initialize remote access connector. It seems the connector is running but it shows as connector component error in Remote access portal.

 

When i try to check the connector in the container using Podman PS, I am not able to see the connector running in the container.

 

Getting the below error when trying to initialize Remote access connector.

 

"The connector is registered. Please wait until connector is operational. This may take several minutes.

To interrupt, press 'Ctrl-C'; the initialization will continue in the background

 Reverse proxy configuration applied.

  Number of applications: 0

 Remote Access certificate applied

 Reverse proxy running

Encountered errors while initializing the connector. Use 'show-status' command to see status of the connector

connector-cli> show-status

25-11-2024--18-05-13

Connector: OfflineaccConn (Id: ***********)

Site: OnPrem (Id:*****************)

Company: **********

Connector version 1.0.22404

Uptime: 0d-0h-05m-06s

 

Secure tunnel connection to Remote Access Service: disconnected

Command plane connection to Remote Access Service: connected

Reverse proxy:

  Running: yes

  Reverse proxy configuration: applied

  Remote Access Certificate: applied, valid for 89d-22h-59m-39s

Number of applications: 0

LDAP server not initialized

Native SSH Access started: yes"

 

Anyone encountered this issue?

3 REPLIES 3

L7 Applicator

Hi @Froz Abdul Wahab Ameer Ahamed​ 

 

Have you tried restarting or reinitialize rthe container ?

 

Also please check the Podman logs

 

podman logs <container-id>

 

In addition please ensure the Firewall is not blocking port 443

 

Hope it helps !

L3 Networker

Yes already tired restarting the server.

 

I also checked the podman and I couldn't find any container in it. podman ps returns nothing.

 

This is really the confusing bit. I am not sure where it got installed if there is no podman container..

 

FW is not blocking 443. That is checked and verified.

Hi @Froz Abdul Wahab Ameer Ahamed​ 

 

As the community has not yet answered this question for some time, could you kindly share if you were able to resolve the issue and how? Your solution could help other community members who may face a similar issue.

 

If the issue is still relevant, I would advise raising a ticket with our Support team for further assistance.

 

Thanks, Liad

  • 293 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!