1 Answer
- Newest
- Most votes
- Most comments
0
The issue was resolved by recreating the certificates a few times. Most likely a bug in the backend services.
Relevant content
asked 2 years ago
asked 3 years ago
The issue was resolved by recreating the certificates a few times. Most likely a bug in the backend services.
asked 2 years ago
asked 3 years ago
Buggy stuff!! Frustrated here too.
Just want to update that I ran into this issue a full two years later. Deployed an app runner service with custom domain and public endpoint and things worked fine. Updated the service to a private endpoint and the cert name was invalid. Switched it back to public domain and the invalid cert remains.