[SOLVED] New domain to appwrite instance

[drifting scaffold]

can you post the domain you have problem with?

[charred rivet]

Thanks, Guille. I think the domain had not fully propagated. It is now working fine. But I wonder why I was getting logs when I hit the new domain.

[turbid cliff]

There's a possibility the domain could've propagated & connected to Appwrite but the browser might've somehow cached the Hello, World response before propagation completed. Just a hunch though.

[charred rivet]

Where is the Hello world from?

[charred rivet]

I have gotten it. This has connected to my starter function already.

[turbid cliff]

good possibility that nginx created a default index.html or something similar.

[turbid cliff]

I see.

[charred rivet]

Does this mean that I have to be creating a new subdomain for every function I create?

[turbid cliff]

aah no. just point a wildcard entry on the domain to appwrite via cname.

[charred rivet]

You are a star. Thanks. I have added functionID.functions.example.com to the custom domain on the function page.

Now how can nginx certbot generate certificates for *.functions.example.com

[turbid cliff]

if there's no proxy in front (like dns proxy via Cloudflare), appwrite should generate a valid ssl automatically for every function domain created.

[regal dome]

@charred rivet Do you have solved this?

[charred rivet]

Yes. I have. The only remaining problem is the ssl certificate. My appwrite instance sits behind an Nginx reverse proxy.

[turbid cliff]

aah i see. in that case, ig nginx sode certbot can issue ssls. iirc, the appwrite worker may not be able to issue ssl. its been a while in that case so memory is a bit hazzy on this.

[regal dome]

@charred rivet Next tine edit the title and add [SOLVED] instead of deleting the post 😅

[SOLVED] New domain to appwrite instance

[charred rivet]

How do I go about issuing certificates for my custom domains for my functions?

[regal dome]

I recommend creating a new post for that