tokers commented on issue #8663: URL: https://github.com/apache/apisix/issues/8663#issuecomment-1381217519
> @tokers yes, we are using v3.x (latest helm version actually) .. but we have an issue logged using the api upload as well .. #8665 which we could not get to work, it would accept the cert, and return 200, but dashboard failed to get the expiry date out of the cert, the dashboard DID extract the SNI correctly. > > Problem is that the cert displayed in the dashboard but was not able to be deleted > > Again, apisix logged the **Same error as per above** on **both upload methods**. (api and dashboard UI) > > I also tried downgrading the cert from 4096 to 2048, just in case, no difference @MarkCupitt I mean, the certificate path prefix for APISIX fetching from the ETCD doesn't match the one Dashboard uses to write the certificate. i.e.g, APISIX fetches from the key space `/apisix/ssls/` while dashboard writes to `/apisix/ssl/`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
