Callback /wp-json/litespeed/v1/token failed
-
We are receiving the message that callback to wp-json/litespeed/v1/token has failed for one of our client domains. We activated debug mode with litespeed/v1/token and as far as I am aware it shows that it should work.
02/06/25 14:12:11 - OC - Init Redis connection
02/06/25 14:12:11 - OC - connecting to localhost:6379
02/06/25 14:12:11 - OC - Connected
02/06/25 14:12:11.921 [45.76.252.131:34076 1 l73] 💓 ------POST HTTP/1.1 (HTTPS) /
02/06/25 14:12:11.921 [45.76.252.131:34076 1 l73] Query String: rest_route=/litespeed/v1/token
02/06/25 14:12:13.724 [45.76.252.131:34076 1 l73] [Vary] 👒👒 Guest mode
02/06/25 14:12:13.734 [45.76.252.131:34076 1 l73] [Optm] init
02/06/25 14:12:14.251 [45.76.252.131:34076 1 l73] [Ctrl] X Cache_control init on
02/06/25 14:12:14.467 [45.76.252.131:34076 1 l73] [Vary] Rest API init disabled vary change
02/06/25 14:12:14.646 [45.76.252.131:34076 1 l73] ❄️ ✅ Passed Cloud IP verification
02/06/25 14:12:14.646 [45.76.252.131:34076 1 l73] [Ctrl] X Cache_control -> no Cache ( Cloud token validation )
02/06/25 14:12:14.646 [45.76.252.131:34076 1 l73] ❄️ ✅ __callback token validation passed
02/06/25 14:12:14.651 [45.76.252.131:34076 1 l73] ❄️ ✅ Passed Cloud IP verification
02/06/25 14:12:14.651 [45.76.252.131:34076 1 l73] ❄️ ✅ Passed Cloud IP verification
02/06/25 14:12:14.652 [45.76.252.131:34076 1 l73] 💰 [Tag] Add --- HTTP.200
02/06/25 14:12:14.653 [45.76.252.131:34076 1 l73] [Ctrl] not cacheable before ctrl finalize
02/06/25 14:12:14.654 [45.76.252.131:34076 1 l73] 💰 X-LiteSpeed-Cache-Control: no-cache
02/06/25 14:12:14.654 [45.76.252.131:34076 1 l73] 💰 Cache-Control: no-cache, no-store, must-revalidate, max-age=0
02/06/25 14:12:14.654 [45.76.252.131:34076 1 l73] [Core] run hook litespeed_buffer_finalize
02/06/25 14:12:14.654 [45.76.252.131:34076 1 l73] [Optm] bypass: Not frontend HTML type
02/06/25 14:12:14.654 [45.76.252.131:34076 1 l73] [Core] Silence Comment due to REST/AJAX
02/06/25 14:12:14.654 [45.76.252.131:34076 1 l73] Response headers --- array (
0 => 'X-Powered-By: PHP/8.3.16',
1 => 'X-DNS-Prefetch-Control: on',
2 => 'Content-Type: application/json; charset=UTF-8',
3 => 'X-Robots-Tag: noindex',
4 => 'Link: <https://kaysleking.com/wp-json/>; rel="https://api.w.org/"',
5 => 'X-Content-Type-Options: nosniff',
6 => 'Access-Control-Expose-Headers: X-WP-Total, X-WP-TotalPages, Link',
7 => 'Access-Control-Allow-Headers: Authorization, X-WP-Nonce, Content-Disposition, Content-MD5, Content-Type',
8 => 'Allow: POST, GET',
9 => 'X-LiteSpeed-Tag: c12_HTTP.200',
10 => 'X-LiteSpeed-Cache-Control: no-cache',
11 => 'Cache-Control: no-cache, no-store, must-revalidate, max-age=0',
)
02/06/25 14:12:14.654 [45.76.252.131:34076 1 l73] End responseWe have all quic.cloud IP’s in CSF inside allow, ignore and verified this.
In addition the same server has just yesterday handled another client domain key generation without problems. ID of that one DomainID:3964261 Both domains have the same PHP engine, module setup. There are no REST API blocking functions active. We wiped .htaccess and wpconfig.php clean during trial run. Modsec shows no security rules being triggered for the domain either.
We have not yet edited line 150 of /rest.cls.php or downgraded to 6.1 as test as we want to have verified if the response we see in debug should indeed indicate that there has been no connection issue.
Report ID: YJDJKNLK
We can grant full access by Dologin Security or direct account if it is deemed neccesary.
We have tier LiteSpeed Enterprise
Best regards,
IT Management HKBO
The topic ‘Callback /wp-json/litespeed/v1/token failed’ is closed to new replies.
