I try to get the current logged in user on the server side, ended up with this strange error: Unable to connect. Is the computer able to access the url?

[Albert-Gao]

It occurs on a locally deployed function (deployed to my local Docker instance). The function can be invoked from the client SDK without issues, but this code has an error.

• The console can be accessed via http://localhost:8310/console/.
• In the function, The APPWRITE_FUNCTION_API_ENDPOINT has a value of http://localhost/v1, is it correct? I can not find anywhere of this value to be set. Also, tried to hard code to http://localhost:8310/v1, still not work
• Fontend ENV: VITE_APPWRITE_PUBLIC_ENDPOINT = "http://localhost:8310/v1"
• API Endpoint in the project Settings - Overview - API credentials: http://localhost:8310/v1

On the server, the client instance is being initialized like this:

  const client = new Client()
    .setEndpoint(Bun.env["APPWRITE_FUNCTION_API_ENDPOINT"])
    .setProject(Bun.env["APPWRITE_FUNCTION_PROJECT_ID"])
    .setKey(req.headers["x-appwrite-key"]);

  // Get JWT token from headers
  const jwt = req.headers["x-appwrite-user-jwt"];

  if (jwt) {
    client.setJWT(jwt);
  }

  try {
    const account = new Account(client);
    const user = await account.get();  
  } catch(e) {
    error(e.message)
  }

[SametDulger]

Hi Albert,

The error "Unable to connect. Is the computer able to access the url?" usually means your function cannot reach the Appwrite API endpoint.

A few things to check and try:

APPWRITE_FUNCTION_API_ENDPOINT value
You mentioned it’s http://localhost/v1, which looks incorrect since it lacks the port. Usually, if your Appwrite console is at http://localhost:8310/console/, the API endpoint should be http://localhost:8310/v1.

Make sure the environment variable APPWRITE_FUNCTION_API_ENDPOINT is set correctly inside your function’s runtime environment. If it’s missing or wrong, your client will try to connect to a non-existent endpoint.

Networking inside Docker
If your function is running inside a Docker container, localhost inside the container refers to the container itself, not your host machine.

So, if your Appwrite API is running on the host machine at localhost:8310, your function container likely can’t reach it via localhost.

Solutions:

Use Docker networking to connect containers by service name or IP instead of localhost.

If your function and Appwrite run in different containers, they need to be on the same Docker network and communicate via container names.

Alternatively, use the host IP or special Docker host addresses (host.docker.internal on some platforms) to reach the host from the container.

Hardcoding endpoint
When you tried http://localhost:8310/v1, if that’s inside the container, it probably still fails for the same reason above.

Verify from inside the function container
Try running a simple curl or HTTP request inside the function container to the API endpoint to verify connectivity.

Summary
Your function likely can’t reach http://localhost:8310/v1 because localhost inside Docker means “this container”, not your host machine. You need to use the correct network address.

Try setting:

.setEndpoint('http://host.docker.internal:8310/v1')

if your environment supports host.docker.internal. Otherwise, configure Docker networking accordingly.