[SOLVED] Issue setting up url

I'm trying to setup an email verification system in my auth flow. It hasn't worked out too well. I have my domain 'parlay.live' in the web domains in the AppWrite console. When calling the createVerification function: ⁨``` await withTimeout( account.createVerification('https://app.parlay.live/verify'), AUTH_TIMEOUT_MS, 'Verification email request timed out' );

I then get the following error:
[AUTH] Verification email failed to send: Invalid ⁨`url`⁩ param: Invalid URI. Register your new client (app.parlay.live) as a new Web platform on your project console dashboard

I have a CNAME DNS record pointing to app.parlay.live, and the parlay.live domain in the appwrite console. I'm not sure what else to do.

I should also add I have a SMTP server configured as well.

In the overview section Add the domain as a platform

I can't even tell if it works lol, the TLS cert doesn't verify.

[03:46:15] Certificate generation started. [03:46:16] Certificate generation failed: DNS verification failed with resolver 8.8.8.8. Domain app.parlay.live has incorrect CNAME value 'appwrite.network,imagine.diy'. (region: New York)

Uhh what are you trying to do here?

<@287294735054274560> <@1019617205220016128> the error here has the incorrect value for CNAME value

Are you trying to set a custom domain on an Appwrite Site?

I’m not at my computer, I’m on my phone. I changed something in the DNS settings and the certificate finally was issued. The problem with the original question is still ongoing though. I had to wait for the dns to verify.

Long story short I’m trying to send a email verification for users to verify the email. The error said the uri was invalid- then up top someone said I needed to add it as a platform.

You shouldn't get the invalid url error anymore if you deployed an Appwrite site in the same project with custom domain app.parlay.live

It worked now, this ticket is solved. Thank you.

[SOLVED] Issue setting up url

Oh wow, thanks for bringing this up 🔥 Applied urgent fix to prevent this from happening to more developers, and manually fixed it for everyone affected.

For transparency, this was caused by an evening release yesterday due to change in env variable. To prevent this fom hapenning in future, staging tests will be more strict when appling changes to env variable values.