[SOLVED] Function URL not accessible

[uncut swift]

none of my function's URL are accessible, how can i make it publically accessible?
I have followed this blog post by Steven: https://medium.com/@stnguyen90/how-to-run-appwrite-behind-nginx-19348ed34243
to setup reverse proxy on my Appwrite VPS .

[native shoal]

@uncut swift aside from conventionally deploying the function template, what other steps have you taken?

Ideally, your function URL should work out-of-the-box, so I'd love to know some more info about your setup

[uncut swift]

Function URL not accessible

[uncut swift]

Hi I just updated the question

[native shoal]

Do you need nginx as a part of your setup? Is there any mandatory requirement for the same?

I ask just so we can verify if this may be interfering anywhere, since this tutorial was created much before our current generation of Appwrite Functions

Also, are you not able to consume your function URL or unable to find it?

[uncut swift]

I'm not able to consume function URL

I'm using NPM for reverse proxy, does appwrite supports reverse proxy by default?

[native shoal]

To have function URLs on a selfhosted Appwrite instance, there are some configuration steps

https://appwrite.io/docs/advanced/self-hosting/functions#github-variables (check _APP_DOMAIN_FUNCTIONS)

https://appwrite.io/docs/products/functions/deployment#domains

As such, because we have function domains, you do not really need a reverse proxy to communicate with functions anymore

[uncut swift]

okay so let me remove the nginx

my .env

[native shoal]

Can you try setting _APP_DOMAIN_FUNCTIONS to a different subdomain

[uncut swift]

okay

http://659ea3665511cd0abde2.func.panarastudios.com

still not working after changing it to different subdomain

I have added new A record in my DNS settings pointing to VPS IP for this new sub domain, updated .env then ran docker compose up -d then created new function from console

[uncut swift]

and this is the URL of the newly created function

[native shoal]

Can you check your function executions to see if you're getting any errors?

[uncut swift]

it's not getting executed

[native shoal]

Are you able to execute it from the SDKs?

Or from the console directly?

[uncut swift]

if i execute it from console directly it's working!

[native shoal]

Did you remove the nginx reverse proxy and try?

[uncut swift]

only function URL not working

[uncut swift]

haven't removed yet, but i can it on my other VPS which don't have nginx, it only has Appwrite

[native shoal]

Let's try that once

You will however need to create other subdomains

It seems like nginx is working on http://func.panarastudios.com/

This might be causing a conflict

Let's try without nginx for sure

[uncut swift]

this is the proxy host i created in NPM

[native shoal]

Steven's blog was written to create a proxy to the Appwrite instance domain, because in the past we did not support function URLs

This wasn't meant to be used with the function URLs directly

[uncut swift]

okay

removing nginx

I have removed the nginx.

let's me test now.

[uncut swift]

it's fixed

looks like it was nginx creating conflict with appwrite

[SOLVED] Function URL not accessible

[crystal flare]

A reverse proxy may still be helpful if you're running multiple apps/services on your server and want them all to be exposed on the same port.

[crystal flare]

it should have been fine to have NPM in front of Appwrite. I've done it before

[crystal flare]

maybe the problem was using HTTP instead of HTTPS

[native shoal]

Can we maybe test and see where this conflict occurs or any pitfalls to stay away from?

Could be a config issue

[crystal flare]

just confirmed it worked

[native shoal]

Can you share your NPM configuration once?

[native shoal]

Just to compare with this?

[crystal flare]

It's shown in the article:

and of course, you'd add the *.whatever.com for your functions

[native shoal]

This seems to be the only troublemaker then, I guess

[uncut swift]

I was using HTTPS

[crystal flare]

This is http

[uncut swift]

I tried https while calling it in browser

Or are you talking about something else?

[uncut swift]

That was copied from Appwrite console. I also tried running https in browser but it was also not working

[crystal flare]

🤷‍♂️ It's also unclear what exactly was going on for you. All you said was it doesn't work

[uncut swift]

Yes because function URLs were not working

http or https

Non of them

I had dns pointed to correct IP as well as I have added wild card sub domain in NPM

[turbid surge]

I have fix this with separate proxy host.

and using Wildcard SSL for the function domain

[uncut swift]

Okay I see I was using same

[regal vale]

I'm having the same issue with Caddy, URL not excecuting functions, but all domains and api working. the only thing I got left to test is to disable the http->https auto redirect, although I don't see how could this help since appwrite's container only listen on one port (80)

also, untill I'm able to provide a reproduction, I would like to ask how and what containers do route the request to the function's container. for example how is the main appwrite on port 80 going to route the connection to a node/bun port 3000

also worth mentioning I'm on a single node docker swarm, so I'm deploying it as a stack and did the required changes