AddOn Updater API not working and need help

[Mayron]

EDIT: Solved the problem by switching to Postman instead of via terminal.

I'm trying to use the same curl commands I've used many times in the past but now they are failing. I tried regenerating the API token and that didn't solve the problem.

I have uploaded the WoW retail version of my addon using the site instead of the API, but I don't think I can use that same approach for the Wrath Classic and Classic Era versions (please correct me if I'm wrong as I wish I could do this).

This is the command I'm using in command prompt on windows:

curl -H "x-api-token: <my-api-token>" -F "id=12345" -F "version=6.7.0-wrath" -F "compatible=3.4.0" -F "[email protected]" https://api.wowinterface.com/addons/update

and I get this error:

curl: (35) schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.

Also, on a side note, I would love to delete the Burning Crusade Classic version so users can't download those old files. Blizzard removed the ability to play this version of WoW so it makes no sense to keep it and only confuses users.

AddOn URL: https://www.wowinterface.com/downloa...-MayronUI.html


I have the files ready to be uploaded but I can't. I could give the field temporarily to a mod to do it for me if it's a hard fix. Hope to hear back soon ty

[Mayron]

I think I got this solved using Postman instead of via command prompt/terminal.

I would still like to remove the Burning Crusade classic (BC) downloadable file version if possible. Thanks.

[Dolby]

The error suggest that curl has an issue with the ssl cert. Which is strange because it works for me and we've gotten hundreds of updates via our API recently.

What do you get if you run this command?

curl https://api.wowinterface.com -vI

It should look something like this...

$ curl https://api.wowinterface.com -vI
*   Trying 104.25.39.63...
* TCP_NODELAY set
* Connected to api.wowinterface.com (104.25.39.63) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=Cloudflare, Inc.; CN=sni.cloudflaressl.com
*  start date: Jun  2 00:00:00 2022 GMT
*  expire date: Jun  1 23:59:59 2023 GMT
*  subjectAltName: host "api.wowinterface.com" matched cert's "*.wowinterface.com"
*  issuer: C=US; O=Cloudflare, Inc.; CN=Cloudflare Inc ECC CA-3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7f961280d600)
> HEAD / HTTP/2
> Host: api.wowinterface.com
> User-Agent: curl/7.64.1
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 403
HTTP/2 403
< date: Mon, 31 Oct 2022 16:19:53 GMT
date: Mon, 31 Oct 2022 16:19:53 GMT
< content-type: text/html; charset=iso-8859-1
content-type: text/html; charset=iso-8859-1
< vary: Accept-Encoding
vary: Accept-Encoding
< cf-cache-status: DYNAMIC
cf-cache-status: DYNAMIC
< report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=h3%2BGzoeKCDgC5asRucvJJJ1BWb%2B9FmnZzCAtPmILUXtMQQGOrEYpw8CUtiJFpUfPnVqswKn0HIGwFxQovgfl%2B963gInbFyQN%2B7%2BJkWogfw1Y0wX%2Bh7E14A4s%2BNqfyCQRvmLo88gj"}],"group":"cf-nel","max_age":604800}
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=h3%2BGzoeKCDgC5asRucvJJJ1BWb%2B9FmnZzCAtPmILUXtMQQGOrEYpw8CUtiJFpUfPnVqswKn0HIGwFxQovgfl%2B963gInbFyQN%2B7%2BJkWogfw1Y0wX%2Bh7E14A4s%2BNqfyCQRvmLo88gj"}],"group":"cf-nel","max_age":604800}
< nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
< server: cloudflare
server: cloudflare
< cf-ray: 762db705fa47e26c-ORD
cf-ray: 762db705fa47e26c-ORD
< alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

<
* Connection #0 to host api.wowinterface.com left intact
* Closing connection 0

[Dolby]

Removed the BC releases

[Mayron]

Oh, that was quick! Thank you. I figured I may have been able to just delete the old files and the BC link would go but you were faster lol.


I've always done the same thing with command prompt. I run it as administrator, too.

I ran the command you mentioned and I see a similar error:



Raw Output:

C:\>curl https://api.wowinterface.com -vI
*   Trying 104.25.40.63:443...
* Connected to api.wowinterface.com (104.25.40.63) port 443 (#0)
* schannel: disabled automatic use of client certificate
* ALPN: offers http/1.1
* schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
* Closing connection 0
curl: (35) schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.