Hi, @FlorianWerndl. I believe the issue here is because there was already an existing branch for the alias when it was used. This is the deploy being shown for that URL:
I believe this is the last time a deploy for that branch was done using a build at Netlify.
Because there is an existing branch deploy with this name, using the same name for the --alias option isn’t working (at least that is what seems to be happening).
Would you be willing to test a netlify-cli deploy with the --alias option set to “testing” (or “potato”)?
If so, please let us know when that is done as I’ll want to see if the alias subdomain is successfully directing to that deploy or not.
EDIT: The “potato” --alias was because I was also working on this topic and there the other person troubleshooting is using “potato” for a testing string. I’m mentioning this because it is otherwise very random and I didn’t want you to wonder why I had said that. It would have made more sense if I included that the other (“other” meaning the “correct”) topic. 