System administrator, integrator
Moving EAS to new hardware
How to move a live site to a new server and restore mobile access and updates.
- 1
What changes when you move
The license is tied to a specific install on the server. After you restore the database on new hardware, access control and LAN work usually continue. The mobile app and remote access via the central hub may pause until support confirms the move to the new equipment.
Tip: Do not keep the old and new servers both connected to updates with the same install at once.
- 2
Prepare the new server
Install EAS on the new hardware (same release or newer — see Installing EAS on the server). Restore the site backup per your backup plan. Configure the link to the central update hub as on the old server. Stop the old server or block its internet access to asceas.ru.
Tip: OS choice (Ubuntu, Astra, or Windows) and install commands: /docs/install/.
- 3
Contact support
EAS support rebinds the license to the new hardware — this is not done from your admin UI. Write to Telegram EAS Support or use the Contacts page: organization name, that you moved to a new server, and a contact. After confirmation, mobile access and updates work again.
Tip: Saying “moved to new hardware” is enough. Support handles the hub-side steps.
- 4
Restart and verify
On the new server restart the EAS service (Linux: systemctl restart eas-server; Windows: the EAS service). In the admin UI open License — there should be no copy/clone warning. Check the mobile app and Hub update.
Tip: Do not reconnect the old server to the central hub with the same install.
- 5
If access does not return
If mobile or updates are still unavailable after support replies, write again and attach a screenshot of the License tab. Do not delete the database or change the key without agreement.