Working with local instances generated by DDEV on Docker

The error message GuzzleHttp\Exception\RequestException: cURL error 60: SSL: no alternative certificate subject name matches target host name 'drd.ddev.site' means, that the "server" (i.e. DDEV containers) hosting drd.ddev.site does not provide a valid SSL certificate for that domain.

The error message GuzzleHttp\Exception\ConnectException: cURL error 7: Failed to connect to 127.0.0.1 port 64983: Connection refused means that you can't use the IP address instead of the domain name to connect to that other site.

To resolve this, you have to get your local environment into a stage, where they properly server the domain name with valid SSL certificates. As I'm not working with DDEV, I can't help with that.

I've stumble across that issue by accident. I've quickly tried to replicate the issue and also forwarded the issue to @rfay, while setting up the two sites outlined in the steps to reproduce section, and randy pointed to https://ddev.readthedocs.io/en/latest/users/usage/faq/#can-different-pro... . I've quickly added a docker-compose.communicate.yaml to the drd project. that way the guzzle error doesn't turn up anymore. but due to the fact i never had the need to set up drd before i was unable to save the core (probably missing a few essential steps). but at least the guzzle error doesnt show up with the docker compose file in place anymore. hope that helps (in case it is still an issue anymore at all)

Thanks a lot @rkoller for your input. That sounds as if this is working as designed and what's required is the recommended ddev configuration. For that matter, I'm closing this, the issue can still be found for others when they run into similar issues.