Domain Key Generation Issue

  • Resolved emisario

    (@emisario)


    3 years, 3 months ago

    Report number: ZBHUPCKY

    Report date: 02/24/2023 09:55:30

    Notice:

    There was a problem with retrieving your Domain Key. Please click the Waiting for Approval button to retry.

    There are two reasons why we might not be able to communicate with your domain::

    1) The POST callback to https://techkera.com/wp-json/litespeed/v1/token failed.

    2) Our Current Online Server IPs was not allowlisted.

    Please verify that your other plugins are not blocking REST API calls, allowlist our server IPs, or contact your server admin for assistance.:

    Things I have tried: Paused Cloudflare and cleared cache. Didn’t work.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support qtwrk

    (@qtwrk)

    3 years, 3 months ago

    could you please try disable CF proxy , wait for 20 minutes, then try again ?

    Thread Starter emisario

    (@emisario)

    3 years, 3 months ago

    Hi, I tried it. Cleaned the cache and all. I (disabled) the CF cache plugin and Paused CF proxy in CF portal as well. Doesn’t seem to be working.

    Thread Starter emisario

    (@emisario)

    3 years, 3 months ago

    Failed to communicate with QUIC.cloud server: The callback validation to your domain failed. Please make sure there is no firewall blocking our servers. Response code: 400

    I ggot this message once and the sample cycle repeats.

    Plugin Support qtwrk

    (@qtwrk)

    3 years, 3 months ago

    yes , something has blocked the communication

    please try , 1) disable CF proxy and keep it off for the time being ,

    2) go to plugin’s General -> server IP , keep it empty , save , and request domain key again , and kindly noted down the time in UTC so I can verify from our side of log

    Thread Starter emisario

    (@emisario)

    3 years, 3 months ago

    This should be enough to allow CF access, right? I might ask my Hosting provider to allow access if CF is not blocking.

    Applied for Domain Key Again at 04:24:53 UTC

    • This reply was modified 3 years, 3 months ago by emisario.
    Plugin Support qtwrk

    (@qtwrk)

    3 years, 3 months ago

    root@node-a:~# curl -i -XPOST -d "test" https://techkera.com/?rest_route=/litespeed/v1/token
HTTP/2 400
date: Sat, 25 Feb 2023 19:17:05 GMT
content-type: text/html
vary: Accept-Encoding
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=P2TN6r8zsi0cyru0PvpWvQwGASnQ80RAUtKFX88qsAkt%2BbU7eB4T5ujxYbDZ9pMzu3Wfx0B5oL2WAgpJDlahfHzZvGVGsEFAevN5%2B5mIg5GHVx%2BnhVB3BfnTH1qnzIY%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 79f2c7747e82a2f1-CDG

<h1>Bad Request (400)</h1>

    it looks like something in the middle that determine it to be a bad request

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Domain Key Generation Issue’ is closed to new replies.