Antoine de Chassey
Antoine de Chassey
Hey Matthias, Thanks for your response. Unfortunately, when setting this env, the app container does not start..
It seems that when config.json changes, the app container does not go back up.
Same error for me trying the latest version... This is getting me crazy.
Hi guys, Any plans to implement this feature in the near future? Would be very nice to have a kind of switch equivalent to `AllowTcpForwarding yes` of OpenSSH :)
Hey @LarsTi Any update on this? I am struggling to make SSL work... I tried with certdumper wich generates cert and key from my acme.json and passes it to mailu...
Seems like the night was good. I managed to make SSL work by letting the front container (Nginx) exposing all the mail ports. docker-compose.yml ```yaml ports: - 'SERVER_IP:110:110' - 'SERVER_IP:143:143'...
Hello Giovanni, This is quite strange as the error has already been seen some time ago. I will keep track of this issue but a new way of managing the...
Hello Giovanni, Coming back to this issue, I just figured the tokens where automatically deleted when a user changes his password. This is a default security functionality implemented by Loopback...
Hi Giovanni, Nothing must have been deleted. The only possible error I see might be a change in the callbacks on the Sigfox Backend.. Best, Antoine
> Adding curl for a healthcheck in the Docker Compose configuration is unnecessary in this case. > > The service is already managed by Docker, which handles the container lifecycle...