Tootfinder

investigating #wusel further, or rather the host's relation to the network, it is even more curious! 'host' on the url hostname correct gives a correct IP. 'host' or 'nslookup' on that IP gives another vhost for that IP, so, seriously HOW did wusel discover the core unix hostname of that remote LAN IP? How? Yet when I run a 'mount' command, there it is.

Trying to use #wusel to fuse mount my #NextCloud files, but when I give the URL to login, I get the redirect to browser and connect, but it then substitutes the target hostname for the vhost name for push/ws, and so, obviously, finds nothing.
There does not appear to be any command option to correct this, but a bigger mystery is how does ANY call to a URL end up knowing the remote hostname and why, in the Age of Hosted Systems, PREFER that over the vhost URL requested?