Troubleshooting FAQ

When I run FSproxy Agent Windows tells me it's not properly configured.

You haven't installed Visual C++ 2008 Redistributable.

Server is not responding when started automatically at logon.

This feature currently doesn't work and it's a known bug. In the configuration dialog please check either Start at logon or Automatically start server not both.

Server is not responding (general).

This may be caused by various things:

• Check if it's running. You can't access \\fsproxy or http://fsproxy when server is stopped! Duh!
• Check if accessing \\192.168.255.1 works. If yes, it may be that your hosts file is incorrect or setup couldn't modify it. You need to manually add 192.168.255.1 fsproxy line to your %WINDIR%\system32\drivers\etc\hosts file.
• Check if TAP interface used by FSproxy is enabled and has static IP address of 192.168.255.2 and network mask: 255.255.255.0.
• If everything above failed to resolve the problem try restarting the server.
• If the above failed try restarting Windows or reinstalling FSproxy.
• If everything failed mail me about the problem.

My Linux/*NIX/other OS reports that <partition mounted by FSproxy> has not been cleanly unmounted.

FSproxy is unable to cleanly unmount partitions mounted read-write when it's closed due to system shutdown or user logging off. Keep in mind that write support is still experimental. Either close FSproxy manually, disable write support from context menu before logging off or disable write support at all. Note that all journaled filesystems should be fine. Most of them have ~5 seconds commit interval.

My <filesystem type> partition hasn't been detected by FSproxy but it's on "supported filesystems" list.

In that case it's a bug. Mail me the detection log (available at http://fsproxy) and full output of:
# file -s <partition> (for example: file -s /dev/sda1).
If you don't know what that means or you don't have file(1) on your system, don't mail me. Sorry, you won't be of any help.

In configuration dialog I can't see any hard drives listed.

You don't have administrative rights on the system. FSproxy needs this to function properly.

UAC is nagging me everytime FSproxy starts at logon!

Disable UAC. ;-) OK I know it's a knee-jerk response but I currently don't have time to write workaround for this. FSproxy needs UAC elevation for direct drive access and I can't do anything about it right now.

I've lost some of my precious data due to FSproxy failure! I'm gonna sue you!

No you don't. Read the disclaimer.