-
Notifications
You must be signed in to change notification settings - Fork 85
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
External condition not working. conditions.uri.IsValidUriResponse(): response not 200, disabling recording. #145
Comments
hello @enduluc, I assume you are still using the old Kerberos Agent? |
hi @cedricve Version 3.1.8 I even tried entering to the containers´ console, test the command curl -i to the endpoint and the response is 200. but the agent says NOPE. |
hi @cedricve any updates? do you need more information about this, logs, or anything else? Please let me know. kind regards, |
Hi @cedricve I have an update. I tested two agents with different url endpoints (condition url). Those endpoints are in my nodered instance. The results: http://192.168.192.30:1880/endpoint ----> this always works in keberos agent and the status code in browser is 200 http://192.168.192.30:1880/endpoint/ ----> when I put the "/" to the end, in kerberos agent stop working and says that response is not 200. The condition URL in kerberos agent cannot validated the url response when you have another deep level in the url. |
Thanks for the information @enduluc, we will provide a fix! ;) |
For some reason, the external condition using a condition url stop working,.... I have several agents configured, when meets the Region of Interest, and the condition url gets the 200 Status code, I should start recording. I almost have 5 months with this configuration, but now stop working. even if I reinstall everything from scratch.
INFO[2024-07-27T14:20:06-04:00] conditions.uri.IsValidUriResponse(): response not 200, disabling recording.
The text was updated successfully, but these errors were encountered: