rogervdf

it happened again - the things I did to force the correct certificate from being loaded, some of which may not have had any effect: * specify steveltn/https-portal:1 instead of...

Ever since strictly specifying the level of certificate per domain, this issue has not occurred

I can confirm that the `pasv_address` is the problem when behind a NAT or routing otherwise For my own purposes I hotfixed the problem with a Dockerfile as follows.. ```...

This bug now comes up ever more frequently, now even towards containers that don't have the same image. For example, frontend web service `x` is renewed and the URL externally...

Below are the 80/443 port users on the machine: it's docker ``` root@debian11-dockercompose:~# netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name...