Perry Mitchell

> is it by VPN server IP address or for all VPN servers I think so yes - I have to connect to a dedicated endpoint as the forwarded ports...

> Did you try with FIREWALL=off? I hadn't, but I've just switched it off now. > Also could you try the latest image instead of a tagged release image? Thought...

So with Firewall off, same issue: I have to forcibly restart the VPN container: ``` 2022-11-24T10:32:05+02:00 INFO [healthcheck] healthy! 2022-11-24T10:32:22+02:00 INFO [openvpn] TCP connection established with [AF_INET]:1912 2022-11-24T10:32:22+02:00 INFO [openvpn]...

And it died again.. I enabled additional Firewall logs beforehand: ``` 2022-11-24T11:18:46+02:00 INFO [healthcheck] healthy! 2022-11-24T11:18:47+02:00 INFO [dns over tls] downloading hostnames and IP block lists 2022-11-24T11:18:52+02:00 INFO [dns over...

Still seeing tonnes of these errors, no matter what I try (OpenVPN 2.5 over 2.4, DOT on/off, blocking on/off, DNS @ google/cloudflare, healthcheck @ google/cloudflare): ``` 2022-12-06T21:14:41+02:00 INFO [healthcheck] unhealthy:...

So I've started using `ncat` to check this within the container.. eg. `ncat -l 54321`. While this works initially with OpenVPN, and I can access the port from outside, after...

Write streams are tricky, but the tests are currently working for writing: https://github.com/perry-mitchell/webdav-client/blob/master/test/node/operations/createWriteStream.spec.ts Are you able to work back from the tests if you haven't already moved on?

`getDirectoryContents` can return etags when using `options.details`: https://github.com/perry-mitchell/webdav-client?tab=readme-ov-file#item-stats https://github.com/perry-mitchell/webdav-client?tab=readme-ov-file#getdirectorycontents EDIT: Sorry, just saw putFileContents.. I'm not sure as I don't recall what the response contains. If it contains an etag...

The headers thing could be CORS.. and if that's the case there's nothing we can do in the client. But I can see adding a detailed response option here being...

Hello! Thanks for making an issue. Seems this is semi common on different Linux distros, but I'm not sure what the issue could be. I believe it's usually the OS...