# Mail watch domain migration

Website: https://authravia.com/
Origin server: 5.189.158.215

## Current state

- Only authravia.com serves the Mail watch application.
- mailwatchapi.com and www.mailwatchapi.com are retired in Apache, with HTTP 410 and no redirect on ports 80/443. A separate empty document root prevents another project from being served as a fallback.
- Existing operators stored under the previous domain may still log in on authravia.com. This does not enable the old hostname.
- Authravia HTTPS certificate and automatic renewal were verified.
- The old domain's DNS can be pointed to the user's other project. Once its new server is ready, replace the retired Apache site if reusing this same server.

## Google integration requires an external update

The user explicitly requested stopping all hosting on mailwatchapi.com. Consequently its old OAuth callback and Pub/Sub push endpoint now return HTTP 410 as well.

The stored gmail_pubsub.projects.redirect_uri has not been changed automatically; it still uses the previous domain. To complete the Google integration move:

1. Add https://authravia.com/gmail-pubsub/gaev5Lu0/redirect to the existing OAuth client's authorized redirect URIs in Google Cloud Console.
2. Update the matching gmail_pubsub.projects.redirect_uri to that same URL.
3. Update the Google Pub/Sub subscription push endpoint to https://authravia.com/gmail-pubsub/gaev5Lu0/push and verify delivery.
4. If hCaptcha restricts hostnames, allow authravia.com for the existing login site key.

Existing Gmail data and tokens were preserved. Live notifications and new authorizations will require the endpoint changes above.

Do not cache Laravel routes: this application selects routes by request hostname during bootstrap.
