>>337
Thank you, that's frustrating. Perhaps the DA login script is broken due to a change on their end, or they are just Cloudflaring up for some reason. Hydrus can't get through CF yet.

Hydrus Companion is a generally good catch-all fix for these sorts of situations, as >>340 says. Opening the client api does not expose your entire db--every access requires an access key you manage on the services->review services->local->client api panel. Anyone requesting anything but the root '/' path of your client api (which gives a simple test page) will just get 401 or 403 unless they have a valid access key in the request.

Also, now I think of it, under services->manage services->client api, there's a checkbox about whether the client api accepts non-local connections (i.e. not 127.0.0.1). I think that is off by default, but please do to check it. If that's off, then the root '/' path will show to the lan, but anything else will 403, even with a good access key. You may also be able to get your firewall rules to reinforce this.