Test the actual bound IP and port. When bound to `0.0.0.0`, local access can use `127.0.0.1`; when bound to a specific LAN IP, use that IP locally too. 5995 is only the default port.
Manual
Mingcedar Share Troubleshooting
Check service listening, browser sessions, permissions, and shared-folder scope in order.
Separate three checks first
Check service state, account permissions, then whether 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 Mingcedar Share machine, use the actual bound address and port. Use `127.0.0.1` when bound to `0.0.0.0`, or the specific IP when bound to one address. If local access still fails, check service state and port conflicts.
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.
Sessions expire 12 hours after login by default or when sharing restarts. Sign in again; if login still fails to persist, allow cookies for this site.
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. Mingcedar Share rejects out-of-bound reads.
Confirm upload permission, valid target directory, total request size including all files and form overhead (512 MiB by default), and free space on the shared-folder disk.
Files stream to the client. Check network interruptions, proxy timeouts, and browser limits; use a stable wired LAN for large packages.
Service fails to start, port is occupied, or autostart fails
Windows / macOS launch at login opens the app without starting sharing. Check systemd and config.json on Linux. On macOS, check local-network and folder permissions.
Default port is 5995. Desktop mode suggests a free port; Linux service mode should use `config set --port` and restart the service.
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 `/etc/hqshare/config.json`; the env file only points to the executable and configuration.
`127.0.0.1` permits local access only; `0.0.0.0` listens on all IPv4 interfaces, with access still subject to network and firewall rules. For production, use a fixed internal IP and restrict sources with the firewall.