Hello, When I try to build a function, I receive the following error
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7ffa8f7549a0>: Failed to establish a new connection: [Errno -3] Try again')': /simple/tgtg/
Function building worked fine on previous versions. I thought that since openruntimes-executor is used instead of appwrite-executor on this version I might have forgotten to change the env variable, but all seems good on that side. It's a bit odd though, as https://appwrite.io/install/env still mentions appwrite-executor
I think I read somewhere that 1.4.1 uses executor instead of appwrite-executor
Let me try to find this to confirm
Can you see if this thread resolves your issue? https://discord.com/channels/564160730845151244/1147311089135132703
Will try and let you know
Unfortunately not, even after double checking the hostname. It's a bit odd though, as the error implies the container cannot access outside internet to grab the dependency. Firewall settings did not change since upgrade to 1.4.1, so unlikely to be the cause
is this a private dependency? is this something we (someone else) can reproducde?
not at all, the only dependency is tgtg, it's public on pip
and this is a new 1.4 function? or old 1.3 function?
well it's a fresh 1.4 appwrite instance with the function being created in 1.4, but the code itself is the still the same
the way you write functions is pretty different in 1.4 👀
Recommended threads
- 408 Timeout / Curl Error 7 in Executor w...
Hey everyone, I am losing my mind over a routing loop/timeout issue on a fresh self-hosted setup. I have a single Linux VPS (IP: 45.141.37.105) and one domain (...
- functions returning error 401 in local
I updated to 1.9.0, and the functions that used to work fine in 1.8.1 are now giving me a 401 error. I can't seem to find a solution. If anyone is running versi...
- router_deployment_not_found
I updated my function a few times and now i am getting the error: router_deployment_not_found I even reverted back to my original code but i am still getting th...