Cannot register docker agent with communiy edition

[cencio91]

Is there an existing issue for this?

• I have searched the existing issues

Doc/tutorial link

https://testsigma.com/docs/agent/setup-on-windows-mac-linux/

Explain the problem

Hi,

I'm trying to setup a testsigma agent using Docker. I'm using Testigma Community (self hosted).

According to the linked guide, I should go to the agent page and click on "add new Agent", then select the option "activate later" to obtain an activation key.

The "activate later" option is not available on my interface (I'm using testigma server v3.0.1). Is this a community licence limitation?
I can see from the agent log that it try to connect to app.testigma.com. Does it only works with app.testsigma.com? In this case, is it not possible to have a headless test execution in community edition?

Than you very much

Your inputs to improve

• If it's a licence limitation, plese better specify it in the documentation
• if it's due to an old documentation, please update this page

[amitsavyasachi]

Hey @cencio91 Yes you are right, the headless option and later activation is available in the cloud version. From the error message i see, it looks like the agent need to run on the background so that web application polls and looks for communication with the agent. But here i see that the agent is not able to communicate to the web app that you have hosted. This could be due to various reason a common reason could be due to security restrictions.

We are currently revamping our documentation, especially for the community edition and this is a valid input, we will promptly work on the feedback and get back to you. However you can avail these feature on our free cloud version as well.

[cencio91]

Thank you @amitsavyasachi for your reply.
Is this a commercial choise limitation, or it will be available also in self-hosted version later? The pricing step between free and pro plan is too large for my use case.
I've got that error running the docker-compose.yml template in the repository, so the agent is installed inside the container

[ghiyastfarisi]

I am encountering this issue also, and looking into the agent source code, there are no way to change the server url host in agent setup to make it accessing our self-hosted testsigma_url
as printed in this log

testsigma-agent           | 2023-09-19 09:53:55  INFO  ApplicationEventHandler:runPostWebContextReadyActions:149 TestsigmaAgent  -------------- Post Web Context Ready Actions Finished --------------
testsigma-agent           | 2023-09-19 09:53:55  INFO  ApplicationEventHandler:postAppContextReadyActions:74 TestsigmaAgent  -------------- Post App Context Ready Actions Started --------------
testsigma-agent           | 2023-09-19 09:53:57  INFO  AgentService:checkAppConnection:38 TestsigmaAgent  https://app.testsigma.com reachable? true
testsigma-agent           | 2023-09-19 09:53:57  INFO  AgentConfig:setMobileEnabled:103 TestsigmaAgent  Checking if appium executable exists in /opt/app/appium/appium
testsigma-agent           | 2023-09-19 09:53:57  INFO  AgentConfig:setMobileEnabled:108 TestsigmaAgent  Mobile enabled flag - true
testsigma-agent           | 2023-09-19 09:53:57  INFO  HttpClient:get:122 TestsigmaAgent  Making a get request to https://app.testsigma.com/api/agents/certificate

it will directly accessing https://app.testsigma.com

[beanywilson]

Has there been any further progress on this issue? I am still trying to understand whether it is a bug, limitation or documentation issue.