Make sure endpoint is connected / prevent disconnections

[fidodido48]

Describe the bug
Endpoint gets silently disconnected.

To Reproduce
Mount the drive normally via provided js code and it gets silently disconnected after some time/failure/etc.

Expected behavior
Shouldn't disconnect abruptly, especially when transferring data/files. Should report disconnection issue and take action.

Screenshots
Not provided.

OS (please complete the following information):

• OS: Arch Linux
• Filesystem and Disk type used [HDD, ext4]

Additional context
Happened a couple of times already.

Hi,
Im testing your filen-network-drive via rclone (webdav/rclone) and having silent disconnection issues. Silent means rclone reports that 'transport is not connected', but not your filen-network-drive. More so it actually doesn't know the failure occurs as:

systemctl --user filen-network-drive reports:

Active: active (running) since ...
Feb  4 23:27:40 archlap systemd[7007]: Started Node.js Filen Network Drive Service.                                                                       Feb  4 23:28:10 archlap npm[3032642]: > start                                
Feb  4 23:28:10 archlap npm[3032642]: > node filen-network-drive.js
Feb  4 23:29:03 archlap npm[3033043]: Network drive started

but df -h |grep -i filen shows nothing.

It happened couple of times already and im ending up with files in my local disk instead of remote (not even knowing that it got disconnected). I could only find out about something wrong happening by luckily spotting errors in the syslog.
Rclone log:

Feb  5 00:14:02 archlap rclone[3033856]: ERROR : <FILE_INFO_REDACTED>: partial file rename failed: can't move object - incompatible remotes
Feb  5 00:14:03 archlap rclone[3033856]: ERROR : <FILE_INFO_REDACTED>: Failed to copy: failed to read destination hash: hash: failed to read: ransport endpoint is not 
connected