Contrib.social

Unexpected response status code: 401

Open on Drupal.org →
Created on 8 August 2023, about 1 year ago
Updated 9 August 2023, about 1 year ago

Problem/Motivation

In every cron run I get this message:
Unexpected response status code: 401. Body was: @"message":"The incoming token has expired" { "type": "WATCHER_REQUEST_LOGIN_RETRY", "code": 401 }

The crons are initiated by the control panel by a command like:
/usr/bin/wget -O /dev/null https://www.example.com/cron/the-cron-key >/dev/null 2>&1

Is this intended behavior?

💬 Support request
Status

Closed: won't fix

Version

1.0

Component

User interface

Created by

🇳🇱Netherlands promes

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @promes
  • Comment about 1 year ago →
    🇩🇪Germany jurgenhaas Gottmadingen

    This is a message that is generated by the CrowdSec SDK and indicates that your Drupal site was using an outdated token to request data from the CrowdSec backend. Their SDK is built in a way that it then re-authenticates itself automatically and tries again. Only if that retry would also fail, the system would throw an exception.

    The message you're seeing in the logs is just for information. Personally, I don't like that message either, but there's nothing we can do about that. It could only be removed in the CrowdSec SDK, so a request for that change should be filed upstream in their repository.

  • Status changed to Closed: won't fix about 1 year ago
  • Comment about 1 year ago →
    🇳🇱Netherlands promes

    Thanks.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024