Hi,
No, I don’t use docker, but I have a proxy to access the nextcloud host. and I can access the LT Server from both localhost, proxy and a client.
Here is a little schema if it’s easier to represent than my explanations :
domain.tld (NC) cloud.local
sub.domain.tld +-----------------------------------+
(CooL / LT) | Nextcloud:80 |
+--------+ | (through Apache) |
| | | CooL:9980 |
| Proxy +-----------+ (direct, installed with apt) |
| | | LanguageTool:8081 |
+--------+ | (direct, manually copied jar) |
curl sub.domain.tld/lt/v2/ OK +-----------------------------------+
curl cloud.local:8081 OK curl cloud.local:8081 OK
Browser throught Nextcloud KO curl sub.domain.tld/lt/v2/ OK
Browser throught Nextcloud Not tested
And the proxy config for LanguageTool :
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
client_max_body_size 10m;
client_body_buffer_size 128k;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 16k;
proxy_buffers 32 16k;
proxy_busy_buffers_size 64k;
location ~* ^/lt/(.*)
{
proxy_pass http://cloud.local:8081/$1$is_args$args;
}
When I try from NC/CooL, I don’t have entries on the NGinx proxy and LT Server saying that there is a query. Nextcloud or CooL log say nothing that seems relevant about LanguageTool (no mention of “LanguageTool”, “grammar”, “LT” or the URL configured in coolwsd).
But if the config seems right, maybe I should try filling a bug report on GitHub instead ?