darShanOriginal post
Rank 4: Virtual Machine
Note: I've already seen this : https://discord.com/channels/564160730845151244/1155442466426736651/1155442466426736651
I am getting the above error on a fresh install of 1.4.4 & also 1.4.3 when using a function to access any API.
As per the linked post, the ports are accessible -
Bash
ufw statusStatus: active
To Action From-- ------ ----22/tcp ALLOW Anywhere 80/tcp ALLOW Anywhere 443 ALLOW Anywhere 8433:8443/tcp ALLOW Anywhere 22/tcp (v6) ALLOW Anywhere (v6) 80/tcp (v6) ALLOW Anywhere (v6) 443 (v6) ALLOW Anywhere (v6) 8433:8443/tcp (v6) ALLOW Anywhere (v6) Appwrite is installed on ports 9000 & 9001, I'm aware of using standard ports but this seems to be working on 1.3.8. I've tried adding those ports for allowing connection, doesn't work.
The exception:
Bash
Error: connect ECONNREFUSED 127.0.1.1:443 at Client.call (/usr/local/server/src/function/node_modules/node-appwrite/lib/client.js:180:23) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async Users.get (/usr/local/server/src/function/node_modules/node-appwrite/lib/services/users.js:598:16) at async Module.default (file:///usr/local/server/src/function/index.js:11:22) at async execute (/usr/local/server/src/server.js:141:22) at async /usr/local/server/src/server.js:158:13For the 127.0.1.1:443,
my previous installation on a different server which used 1.3.8 also had this, worked fine.
Function -
JavaScript
const client = new sdk.Client().setProject(projectId).setEndpoint(endpoint).setKey(key);const user = await (new sdk.Users(client)).get(userId);Summary
The user is experiencing an error "connect ECONNREFUSED 127.0.1.1:443" when trying to access the API in a fresh install of Appwrite version 1.4.4 and 1.4.3. They have confirmed that the required ports are accessible and have tried allowing the connection on additional ports without success. The user also mentions that a previous installation on a different server with version 1.3.8 had the same error but worked fine. The function that is causing the error is shown in the thread.
Solution: The user mentions that reinstalling CloudPanel and changing the sub