eldadfux

_APP_ENV=production
_APP_LOCALE=en
_APP_OPTIONS_ABUSE=enabled
_APP_OPTIONS_FORCE_HTTPS=disabled
_APP_OPENSSL_KEY_V1=your-secret-key
_APP_DOMAIN=localhost
_APP_DOMAIN_TARGET=localhost
_APP_CONSOLE_WHITELIST_ROOT=enabled
_APP_CONSOLE_WHITELIST_EMAILS=
_APP_CONSOLE_WHITELIST_IPS=

eldadfux

Appwrite SSL Certificates

This is a small snippet to help you debug and make sure Appwrite is able to generate SSL certificates for your domains.

Things to check:

• You're using a public-facing domain pointing to your Appwrite instance.
• Your _APP_ENV variable is set for production mode (learn more at: https://appwrite.io/docs/environment-variables).
• You have a valid email address set on _APP_SYSTEM_SECURITY_EMAIL_ADDRESS (learn more at https://appwrite.io/docs/environment-variables).
• Currently, Appwrite is using the acme HTTP-challenge to issue an SSL certificate. This forces us to generate certificates for port 443. At this point, other ports will not work.

eldadfux

Appwrite's Email Verification

The Appwrite email verification process helps you verify your project user really owns the email address he has signed up with. The email verification process allows your user to update his user object emailVerification attribute to true.

The email verification process consists of 2 parts:

1. Sending the confirmation email
2. Confirming the verification process

By default, unverified users are not restricted in any special way. It's up to you and your app logic to decide how these users are treated. You can prompt them with a verification message or limit their access to your application.