Open `http://127.0.0.1:5995/` on the server first, then open `http://server-ip:5995/` from a client.
Manual
HQShare Troubleshooting
Check login, port, download, upload, and permissions layer by layer. Confirm the service is listening before checking browser session and shared-folder boundaries.
Separate three checks first
Do not mix web login, service ports, and file permissions. First confirm the service is running, then confirm the account has permission, then confirm the file is inside the shared root.
If login works but buttons are missing, the role usually lacks permission. Downloads require `files.download`; uploads require `files.upload`.
Files must be inside the shared root. Do not use a system drive, desktop, or real customer root folder as the shared root.
Browser cannot open, login fails, or login loops back
Separate service startup, port reachability, invalid credentials, and browser session issues.
On the HQShare machine, open `http://127.0.0.1:5995/`. If local access fails, check service state and port conflicts first.
If local access works but client access fails, check bind address, firewall, network segmentation, and the IP address used by the client.
Confirm the user is enabled, the password is correct, and the role still exists. Change the initial manager password before production use.
Check whether the browser session is blocked or whether a proxy rewrites the access address in a way that makes login state unstable.
Download fails, upload fails, or large files are unstable
Check permissions and paths first, then file size, disk capacity, and browser download behavior.
The current user lacks download permission. Use a role that is allowed to download files.
The file is missing, the name does not match, or the file is outside the shared folder boundary. HQShare rejects out-of-bound reads.
Confirm upload permission, valid target directory, maximum upload size, and free space on the shared-folder disk.
HQShare streams files, but network interruption, proxy timeout, or browser limits can still affect large packages. Prefer stable wired LAN for major packages.
Service fails to start, port is occupied, or autostart fails
Windows desktop mode shows startup prompts and current-user startup state. Linux deployment should be checked through systemd and the environment file.
Default port is 5995. Desktop mode suggests a free port; Linux service mode should update the env file and restart.
Confirm the desktop app is running, the tray icon is visible, current-user startup matches the site requirement, and the shared folder is still accessible.
Run `systemctl status hqshare` and `journalctl -u hqshare -n 100`, then confirm the shared folder, port, and bind address in the env file.
`127.0.0.1` allows only local access; `0.0.0.0` listens on all interfaces. In production, bind a fixed internal IP and pair it with firewall rules.