. . . it just stops taking new connections, switching the server off and then on fixes it, i couldn't find why this happens and had to resort to run a script that checks 24x7 if hfs is not accepting downloads and kills it and runs it again.
Do you use the Watchcat2 script?
https://rejetto.com/forum/index.php?action=dlattach;topic=12055.0;attach=9809The stuck/off server is made worse by running limits (hfs menu > limits) that make HFS get more busy and stuck more often.
The Worst is Speed limit. Instead of HFS speed limit, you could spend 3 dollars on a 100 megabit USB2 adapter, assign it a fixed address and assign HFS to the megabit>USB adapter's ip address. If you were to accidentally get a gigabit adapter, (and therefore get stuck), just go to properties of the network adapter and manually set 100-half. This also applies to single-thread versions of most web servers.
Upload and download at the same time will probably get stuck If the connection speed is high. Perhaps a clever programmer could figure out complete lockout/tagout logic to thoroughly prevent simultaneous uploads+downloads? The problem is not severe at 100megabit and lower speeds.
Edit: HFS2.4 RC7 has 'archive-only-selected' for overload protection; however, earlier versions can try to download the entire server with just one click on the archive button (stuck in 1 click). Possible fixes include search and disable the recursive function. . . Or switch to the RC7 template or takeback or throwback or stripes. Since the archive feature makes .tar files that the user doesn't want, removing the archive button is an option.
EDIT: See HFS 3
https://github.com/rejetto/hfs