az webapp config ssl bind results in error when binding valid wildcard certificate.
See original GitHub issueDescription
Attempting to bind a wildcard ssl certificate (valid for hostnames *.example.com
and example.com
) to a deployment slot with the hostname, slot-master.example.com
, results in the following error:
Certificate for thumbprint '<thumbprint>' not found.
The command I used was az webapp config ssl bind --certificate-thumbprint <thumbprint> -n <appname> -g <resourceGroup> --ssl-type SNI -s master
.
I have verified that the thumbprint exists, and was able to bind the certificate to the hostname via the Azure portal. Also verified that the certificate is listed via the command line using az webapp config ssl list --resource-group <rg>
Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: pip, and using az component update
to keep up to date.
CLI Version: What version of the CLI and modules are installed? (Use az --version
)
Answer here:
azure-cli (2.0.6)
acr (2.0.4)
acs (2.0.6)
appservice (0.1.6)
batch (2.0.4)
cdn (0.0.2)
cloud (2.0.2)
cognitiveservices (0.1.2)
command-modules-nspkg (2.0.0)
component (2.0.4)
configure (2.0.6)
core (2.0.6)
cosmosdb (0.1.6)
dla (0.0.6)
dls (0.0.6)
documentdb (0.1.5)
feedback (2.0.2)
find (0.2.2)
interactive (0.3.2)
iot (0.1.5)
keyvault (2.0.4)
lab (0.0.4)
monitor (0.0.4)
network (2.0.6)
nspkg (3.0.0)
profile (2.0.4)
rdbms (0.0.1)
redis (0.2.3)
resource (2.0.6)
role (2.0.4)
sf (1.0.1)
sql (2.0.3)
storage (2.0.6)
vm (2.0.6)
Python (Windows) 3.6.1 (v3.6.1:69c0db5, Mar 21 2017, 18:41:36) [MSC v.1900 64 bit (AMD64)]
Python location 'C:\Python36\python.exe'
OS Version: What OS and version are you using?
Answer here: Windows 10 Pro Version 1607, Build 14393.1198
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: Powershell
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (5 by maintainers)
Top GitHub Comments
@mstancombe Have issue open here: https://github.com/Azure/azure-cli/issues/9972
@yugangw-msft I have the same issue where a wildcard cert issued by letsencrypt can be bound via cli when the app service is in the same resource group as the plan, but not when it’s in a different resource group. Given that this is a supported configuration through the azure portal ui, can this issue be re-opened?