Firewall Port Access
Firewall, cloud security group, DNS, proxy, and HTTPS settings must match the deployment address used by clients.
Common Symptoms
- The server works locally but external access fails.
- The client cannot connect after entering the server address.
- Some functions fail after switching to HTTPS or a domain name.
What to Check First
- Required ports are open in both the server firewall and cloud security group.
- Reverse proxy or Nginx forwards requests to the correct service.
- DNS resolves to the current server.
- The client address, admin console address, domain, and certificate are consistent.
Recommended Actions
- Test access from the server, internal network, and external network.
- Check firewall and security group rules according to the deployment manual.
- Check whether proxy or HTTPS changes affected file and message services.
- Keep a record of every changed port and rule.
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.