-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot register docker agent with communiy edition #375
Comments
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. |
Thank you @amitsavyasachi for your reply. |
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
it will directly accessing |
Has there been any further progress on this issue? I am still trying to understand whether it is a bug, limitation or documentation issue. |
Hi, is it still impossible to use headless option with self-hosted version? I'm going to start a new project and testsigma would be my first choice, but both headless than self-hosting are requirements for me. Thank you very much |
+Amit Savyasachi ***@***.***>
Regards,
Rukmangada(KR)
Founder & CEO | Testsigma
https://testsigma.com
…On Sat, Aug 3, 2024 at 4:12 PM cencio91 ***@***.***> wrote:
Hi, is it still impossible to use headless option with self-hosted
version? I'm going to start a new project and testsigma would be my first
choice, but both headless than self-hosting are requirements for me.
I cannot find any side by side comparison between feature of self-hosted
and cloud version.
Thank you very much
—
Reply to this email directly, view it on GitHub
<#375 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVOCK6QRYJF5NJV673BJDPDZPSX3BAVCNFSM6AAAAAA422Y3E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRWGY3TCMZSGM>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Hi Rukmangada, I'm sorry but I haven't understood your comment |
@cencio91 Yes, you can check the comparioson from here There are no plans as of now to add this to the community version as we are looking for more contributors who can actually contribute to this on scale. However, these options are available in the cloud version. |
Ok @amitsavyasachi , thank you very much for for your clarification and the provided documentation |
Is there an existing issue for this?
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
The text was updated successfully, but these errors were encountered: