Server Address Change

When the server address changes, update the client address, admin console address, domain, HTTPS certificate, proxy, file service links, and client update settings consistently.

Common Symptoms

Clients cannot connect after the address changes.
Old image or file links fail.
Some users still scan or enter the old address.

What to Check First

Whether the new address, protocol, domain, and port are correct.
Whether DNS, firewall, security group, proxy, and certificate settings are updated.
Whether QR codes and client upgrade URLs are updated.
Whether the old address needs a transition period.

Recommended Actions

Change the server address in one planned maintenance window.
Update the admin console, client address, QR code, HTTPS certificate, and proxy configuration together.
Test PC, mobile, internal network, and external network access.
Notify users of the new address and keep the old address only if required.

When to Contact an Administrator or Operations Team

The issue affects multiple users or the whole company.
The fix requires restarting production services, replacing certificates, changing databases, changing file services, or updating License files.
Provide the failure time, impact scope, screenshots, account information, client version, server address, and related logs when reporting the issue.