Cannot Get Server Address During Login
When the client cannot get the server address, first confirm the address, network, firewall, domain, and 'DuliRoute' service.
Common Symptoms
- Saving the server address reports a connection failure.
- Login reports network exception or '4000'.
- Multiple users cannot connect after entering the address.
What to Check First
- The server address, protocol, and port are correct.
- The client network can reach the server.
- Firewall, security group, DNS, and proxy settings allow access.
- 'DuliRoute' is running if multiple users are affected.
Recommended Actions
- Test the address from a browser or another network.
- Confirm whether only one client or many clients are affected.
- Ask operations to check 'DuliRoute', firewall rules, and server logs.
- Reissue the correct server address or QR code if the address changed.
Operations Focus
- Login '4000' and server-connection failures should first point to 'DuliRoute'.
- If login succeeds but the client stays disconnected, also check 'DuliFront'.
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.