Moving to a new domain
Documentation · Own Ebook self-hosted
- Open your license here and request the production domain move. The service enforces the displayed cooldown.
- Back up the database and all persistent files, including
private/licensing. - Update CLIENT_URL, SERVER_URL and PUBLIC_SITE_URL in the backend environment; update NEXT_PUBLIC_SITE_URL using the deployment’s supported configuration procedure. On shared hosting, ask the provider to apply runtime configuration to the bundled frontend; do not ask the buyer to build Next.js. VPS technicians should follow that deployment’s build/configuration procedure.
- Configure DNS, the reverse proxy and HTTPS for the new domain. Preserve the same installation identity and restart the services.
- Open Admin → License & Updates and verify the license to obtain a lease for the new domain.
If the old server and its private identity are lost, contact support for installation recovery. Creating another identity consumes a new installation slot.
All topics
- العربية: تثبيت الاستضافة المشتركة بالصور
- Start here: 6 simple steps
- Will my hosting work?
- System requirements
- How to install
- Database setup
- License activation
- Production and development installations
- Moving to a new domain
- Reissue
- Updating Own Ebook
- Backup and rollback
- Common installer errors
- Common license errors
- Support