I may not have been very clear, my mistake. Basically it was user error in the seahub_settings.py file
I installed the current version and deployed it with the seafile install script from github: https://github.com/haiwen/seafile-server-installer
Which worked great until I tried to use the webUI/android app over wifi on the same subnet as the server.
Turns out the script sets the bound IP address by default to 127.0.1.1 (incorrect loopback).
This threw me for a loop until I went into the config files and changed the bound address to the correct IP/hostname.
Since the windows client worked prefectly I did not think to inspect the config files initially until after I finally noticed that the webUI was pointing to the incorrect loopback. Once I figured that out it works fine over the LAN/NAT
Basically it was user error on my part, but my issue would still remain in our production setup where I need it to listen on 2 seperate interfaces, out LAN/NAT interface, and a seperate private VPN endpoint on a subnet that is not serviced by DNS and I’m restricted from editing any hosts files, especially on mobile clients where I don’t have jailbroken/rooted users.
As a home solution I’m very much leaning to migrating away from my personal OC install once I verify that seafile works well in all my use cases.
Unfortunately it may not work well for me in our business setting.
Can I run 2 concurrent instances of seafile, each bound to different ports?
If I can do that with just some duplicate configuration files, I might be able to provide a work around that will be acceptable to our users.
Currently I’m testing out syncrify, but so far I much prefer seafile to any other solution I’ve seen.