Creating a deployment target whose first deploy fails no longer shows a server error
TL;DR: When you created a deployment target and its first deploy failed, the portal answered with a server error instead of its message. It now tells you the target was created and that the deploy failed.
When you created a deployment target in the portal and its first deploy failed, you received a server error instead of a message saying what had happened. The portal now tells you that the target was created and that its deploy failed.
The target was created all along, even when you saw the error. If this happened to you, there’s no need to create it again: it’s already in your list, and you can deploy to it from there.
The same fix covers any message about a deployment target that contains characters outside basic Latin, such as a host name written in another script. Those messages now appear as they should instead of an error.
What you need to do
Nothing.