Error “There was a problem with retrieving your Domain Key” won’t go away

  • Resolved dassels43

    (@dassels43)


    1 year, 10 months ago

    The above error won’t go away. We moved servers and updated all IP settings, firewall allows, etc. Tested the rest route and we get a “{“_res”:”ok”}”. In the end, we manually pasted in the Domain Key and it appears to be working (we were able to send images to QUIC and it is picking up CCSS requests). We’re not sure though if something is still wrong or some kind of bug with the error message?

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

  • Are you using CloudFlare for your DNS?

    CF sometimes cause this type of issues

    • This reply was modified 1 year, 10 months ago by Virgil.
    Thread Starter dassels43

    (@dassels43)

    No cloudflare or any other CDN type stuff. Same DNS provider as before when it was working.

    Plugin Support qtwrk

    (@qtwrk)

    please provide the report number

    you can get it in toolbox -> report -> click “send to LiteSpeed”

    Thread Starter dassels43

    (@dassels43)

    Hi, report just sent. The number is: LZAQXMYO

    Plugin Support qtwrk

    (@qtwrk)

    from the report , your site got domain key already , could you please do me screenshot what is it shows or where you see that message?

    Thread Starter dassels43

    (@dassels43)

    Hi, yes of course. I should have attached it earlier. Here it is.

    • This reply was modified 1 year, 10 months ago by dassels43.
    • This reply was modified 1 year, 10 months ago by dassels43.
    Plugin Support usabe

    (@usabe)

    Looks like something got stuck in the database. Could you please open a ticket by emailing to [email protected] with further details? Remember to reference this topic and ask to assign your ticket to Abe.?

    Thread Starter dassels43

    (@dassels43)

    Issue is sorted. Turns out the documentation at QUIC’s website is a bit misleading. It says to visit this address to test the API call:

    https://example.com/?rest_route=/litespeed/v1/token
    And to check if either:

    {“code”:”rest_no_route”,”message”:”No route was found matching the URL and request method.”,”data”:{“status”:404}}

    or:

    {“_res”:”ok”}

    is returned. In our case this was true however, it still failed because one actually needs to verify that one can make API calls to:

    https://example.com/?rest_route=/litespeed/v1
    (just “v1”, no “token” after it)

    Permissions reconfigured to allow calls to v1 and now everything works

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Error “There was a problem with retrieving your Domain Key” won’t go away’ is closed to new replies.