-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
talha nizamani edited this page Mar 4, 2026
·
1 revision
This page collects the most common operational problems and where to look first.
Check:
- incomplete dependencies
- invalid settings
- invalid host or port
- incompatible mode and tunnel combination
- directory path problems
Check:
- the bound host and port
- whether the saved config differs from the command you expected
- whether another process is already using the port
Check:
- whether you are actually using LAN mode
- whether the host binding is network-reachable
- whether clients are using the correct address
Check:
- whether the site is being opened over plain HTTP
- whether certificate and hostname expectations match your deployment
- whether clients are opening the site by an address different from the one you planned
This usually means the active download load is consuming too much request-handling capacity. Review:
- worker thread count
- max concurrent downloads
- real client load during testing
Check:
- file path validity
- permissions on the shared folder
- client connection reliability
- whether the machine is overloaded under concurrent transfers
Check:
- the exact link path
- file existence in the shared folder
- path confinement behavior
- whether the file was moved or renamed after the page loaded
Reduce request logging verbosity.
Check whether monitor mode is enabled.
Check:
- whether the mode is actually
public - whether tunnel behavior is enabled as required
- whether your expectations are LAN-only or truly public
Use this recovery approach:
- revert to local mode
- use a simple shared folder
- disable non-essential extras
- confirm the app works locally
- step forward one change at a time