• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question How to force Plesk Docker to use 0.0.0.0 instead of 127.0.0.1?

L. Hagen

Basic Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Obsidian v18
Hi,

it seems so that when using Plesk docker interface that the container listen on 127.0.0.1. This prevents connections from other servers. So how can I setup the Pleask docker that it always listens on 0.0.0.0?

Thx and best regards,
Lars
 
Hi Kaspar, I saw this entry. But I have two "identical" servers (same versions, updates, configs etc.). It woks on one server but not on the other and on both servers the `/etc/docker/daemon.json` contains `{"ip":"127.0.0.1"}`. So I expect the issue in a different place.
If you run the docker ps --format '{{.ID}} {{.Names }} {{.Ports}}' command on both servers, do they also both list 127.0.0.1 on the port forwarding? For example:
34b5670a1bbad phpmyadmin 127.0.0.1:8080->80/tcp, :::8080->80/tcp
 
Back
Top