This is not a real domain, so there is no collision in the real.

The hostname and endpoint I will connect to is. The hostname can be anything really, and doesn’t need to be a world-reachable domain name. You cannot connect securely to just the IP 1 you either have to add a hosts entry to your local machine or connect via a DNS-registered domain name that matches the CN or one of the SANs (to be set shortly). Decide on the hostname to connect over HTTPSĮither the Common Name (CN) or one of the Subject Alternative Names (subjectAltName or SAN) of the certificates we’ll generate and the hostname header in the Docker daemon REST API requests must match. A remote Linux server running Docker CE.PhpStorm successful connection to remote Docker daemon This is intended for PhpStorm on Windows and AWS users, but it is equally applicable to developers in other IDEs, on OSX, and on other remote OSes.

We’ll create certificates, configure the Docker daemon, verify the setup, and configure PhpStorm to even use Docker Compose remotely.Īt the end of this article we should have PhpStorm connecting to the Docker daemon in an AWS Linux 2 EC2 container over HTTPS. This will allow us to develop Docker applications remotely inside the PhpStorm IDE. Goal: Let’s setup a remote Docker daemon and connect to it securely over HTTPS (TLS) with PhpStorm.