HumanSignal
webhook connection time out
I am trying to put the webhook to the labelstudio using AWS gateway API and lambda. It was work before, but the next I encountered the error in the following.
requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='vmwerwertewr.execute-api.us-east-2.amazonaws.com', port=443): Max retries exceeded with url: /dev/get_export (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f47af6758a0>, 'Connection to vmwerwertewr.execute-api.us-east-2.amazonaws.com timed out. (connect timeout=10.0)'))
I want to modify the connect time out as 30s, how to do that? It is shows it is the connection issue, but I test my GatewayAPI it works fine. I was wondering if it is the bug from labelstudio's side, but I need more information and further debugging. For the debugging work, I want to the modify the timeout limit, can anybody help to answer how to do that through kubenete and helm?
My label studio set up:
labelstudio version: 1.13.1
I deployed labelstudio on AWS EKS, I installed and updated labelstudio using helm, and the following global envrionment settings of my label studio:
helm upgrade labelstudio heartex/label-studio -namespace label-studio-dev –set global.extraEnvironmentVars.LABEL_STUDIO_DISABLE_SIGNUP_WITHOUT_LINK=“true” –set [global.extraEnvironmentVars.LABEL_STUDIO_USERNAME="[email protected] --set global.extraEnvironmentVars.LABEL_STUDIO_USERNAME=%[email protected]" –set global.extraEnvironmentVars.LABEL_STUDIO_PASSWORD=“mypassword” –set global.extraEnvironmentVars.SSRF_PROTECTION_ENABLED=“true” –set global.extraEnvironmentVars.LABEL_STUDIO_HOST=“http://xxxx.xxxx.com/”
I just make the webhook running using the lambda function link. related issue: https://github.com/HumanSignal/label-studio/issues/6385 but it would be nice to have a method to modify the timeout and do further debug because lambda function link have some risk of being corrupted when expose as webhook. I was monitoring my application activities, there are always some suspicious warning which reveals someone is trying to scan my .env files and hack my application.