Credit Refund Request + SSL Protocol Error on kimi.link Subdomain (kidp4yryohx6q.ok.kimi.link)

Kimi K2
,
1

I encountered a server-side SSL certificate error on Kimi’s link preview service that prevented content from loading, yet my account was still charged credits for failed attempts.

Technical Details:

  • Error: ERR_SSL_PROTOCOL_ERROR

  • Affected URL: https://kidp4yryohx6q.ok.kimi.link

  • Root Cause: Invalid SSL certificate/response on Kimi’s ok.kimi.link subdomain

  • Impact: Page loads but preview fails; unable to access content

  • Date/Time: March 28, 2026, ~02:25 UTC

  • Credits Deducted: [3] (for failed troubleshooting attempts)

Steps to Reproduce:

  1. Access any Kimi link using the ok.kimi.link subdomain

  2. Browser attempts HTTPS connection

  3. Server sends invalid SSL response

  4. Connection fails with ERR_SSL_PROTOCOL_ERROR

  5. Credits deducted despite no successful generation

Expected Behavior:

  • SSL certificate should be valid and trusted

  • Failed connections due to infrastructure errors should not consume credits

Request:

  1. Credit Restoration: Refund [3] credits deducted during failed attempts caused by this server-side issue

  2. Technical Fix: Investigate SSL configuration on *.ok.kimi.link subdomains

Evidence:

  • Browser error screenshot: [Attach screenshot of ERR_SSL_PROTOCOL_ERROR]

  • Network console logs showing failed TLS handshake

Environment:

  • Browser: [Chrome]

  • OS: [Windows]

  • Location: [EST]

  • No VPN/proxy in use

2

Thank you for the detailed report regarding the SSL error on kidp4yryohx6q.ok.kimi.link.

I checked our infrastructure from my end and the service appears to be operating normally:

SSL Certificate Status: Valid and trusted

image
image1072×1280 49.1 KB

Link Preview Functionality: Loading correctly

image
image1920×1080 90.1 KB

Given that our certificate is valid and the service is functional on our side, the ERR_SSL_PROTOCOL_ERROR you’re encountering suggests a discrepancy between what our server is presenting and what your browser is receiving.

To help us investigate this mismatch, please provide:

  1. A screenshot of your browser’s certificate viewer showing the specific certificate details your browser is receiving (click the padlock/error icon → Certificate → General/Details tab)
  2. The full certificate chain if visible