Fix IIS Wildcard SSL for Telegram
Budget: $10 – $30 USD
Our API endpoint is running on IIS 10 with a wildcard certificate, yet every Telegram call is rejected with “SSL routines::certificate verify failed.” I need someone who knows their way around IIS Manager, certificate chains, and Telegram’s strict SSL requirements to step in, inspect the current bind-up, correct any missing intermediates, and confirm the service can be reached over HTTPS without warnings.
The job is finished when a live Telegram webhook test returns 200 OK and the certificate chain passes an external SSL checker. We can arrange a quick remote session or you can guide me step-by-step—whatever gets the certificate green-lit fastest.
The job is finished when a live Telegram webhook test returns 200 OK and the certificate chain passes an external SSL checker. We can arrange a quick remote session or you can guide me step-by-step—whatever gets the certificate green-lit fastest.