Search results

Are you using the Plesk firewall? If so, did you enable it before or after starting the containers? Because starting the firewall appeared to solve the problem for me as well... until I had to restart dockerd, which recreated the nat entries and made the ports world-open again...

Interesting... because this not an issue, but the intended behavior according to the Docker extension docs, see [1]: "Important: If port mapping is configured, Docker binds to the specified port on all network interfaces of the host system. Usually, this means that the application can be...

Have you checked what happens when you restart dockerd and the container, or even the whole system? Cause our support told me that the most likely reason for this "solution" to work is that the Plesk firewall seems to delete the nat entries of Docker. So, did you verify that this is indeed a...

Good to hear that it's at least somehow on the agenda. How do you plan to fix this? In fact, an embarrassingly simple change allowing the specification of a binding IP with the port would be perfectly sufficient. The only problem is that the current filter won't let me do this and instead reply...

Hello everybody, recently, we started using the Docker extension of Plesk. Personally, I think that this extension is - in theory - a brilliant idea. However, when it comes to the details of implementation, I think that some things have not really been thought through to the end. This is...

Hello everybody, great job, I can't wait to try this out, BUT... we have an owncloud instance on one domain, which might cause problems with SPDY/HTTP2 because of a restriction in the Qt desktop Clients, see https://github.com/owncloud/client/issues/3146 Is it possible to run this particular...