(This was built using the Linode marketplace instance automatically) I'm not going to use my actual domains for this, but I have the Appwrite panel set up at backend.example.xyz, which is the value for both the _APP_ENV and _APP_DOMAIN_TARGET environment variables, but when I try setting a custom domain for a web app to something like api.anotherdomain.me, I get an internal server error popup
What do the docker logs for the appwrite container say?
appwrite | [Error] Timestamp: 2023-07-08T16:53:39+00:00
appwrite | [Error] Method: POST
appwrite | [Error] URL: /v1/projects/:projectId/domains
appwrite | [Error] Type: Appwrite\Extend\Exception
appwrite | [Error] Message: Unreachable CNAME target (localhost), please use a domain with a public suffix.
appwrite | [Error] File: /usr/src/code/app/controllers/api/projects.php
appwrite | [Error] Line: 1344
appwrite | [Error] Timestamp: 2023-07-08T16:55:44+00:00
appwrite | [Error] Method: POST
appwrite | [Error] URL: /v1/projects/:projectId/domains
appwrite | [Error] Type: Appwrite\Extend\Exception
appwrite | [Error] Message: Unreachable CNAME target (localhost), please use a domain with a public suffix.
appwrite | [Error] File: /usr/src/code/app/controllers/api/projects.php
appwrite | [Error] Line: 1344
oops that was it twice
Did you apply the changes to your .env file by recreating the containers?
wait does rebooting the linode not do that?
Not necessarily
ah i see lol
does docker compose up -d recreate the containers? sorry i'm not super familiar with docker
it worked lol thank you!! i should've thought of that before D:
[solved] Internal server error when setting custom domain
Recommended threads
- Project Inactivity Clarification
I'm on appwrite free plan with my account (om.thakkar@ivcventure.com). Even though throughout the week we use the project atleast once to upload dynamic content...
- Free trial credit?
I understand that another person I know got a free 50 dollar credit promo as a banner in his project but I fail to see one in mine. Is such promo not for everyo...
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...