## Problem/Motivation On sites that boot through the `symfony/runtime` front controller —the default since Drupal 11.4 via `DrupalRuntime` — the `drd_action_info` action fails and the dashboard reports *"Remote instance does not support DRD"*. The agent side throws: ``` LogicException: Settings can not be serialized. This probably means you are serializing an object that has an indirect reference to the Settings object. Adjust your code so that is not necessary. in Drupal\Core\Site\Settings->__sleep() (Zeile 87 in /app/docroot/core/lib/Drupal/Core/Site/Settings.php). #0 [internal function]: Drupal\Core\Site\Settings->__sleep() #1 /app/docroot/modules/contrib/drd_agent/src/Crypt/Method/OpenSsl.php(116): serialize() #2 /app/docroot/modules/contrib/drd_agent/src/Agent/Action/Base.php(344): Drupal\drd_agent\Crypt\Method\OpenSsl->encrypt() #3 /app/docroot/modules/contrib/drd_agent/src/Controller/Agent.php(79): Drupal\drd_agent\Agent\Action\Base->run() #4 [internal function]: Drupal\drd_agent\Controller\Agent->get() #5 /app/docroot/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(123): call_user_func_array() #6 /app/docroot/core/lib/Drupal/Core/Render/Renderer.php(638): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() #7 [internal function]: Drupal\Core\Render\Renderer::Drupal\Core\Render\{closure}() #8 /app/docroot/core/lib/Drupal/Core/Render/Renderer.php(653): Fiber->resume() #9 /app/docroot/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(121): Drupal\Core\Render\Renderer->executeInRenderContext() #10 /app/docroot/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(97): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() #11 /app/vendor/symfony/http-kernel/HttpKernel.php(183): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() #12 /app/vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\Component\HttpKernel\HttpKernel->handleRaw() #13 /app/docroot/core/lib/Drupal/Core/StackMiddleware/Session.php(53): Symfony\Component\HttpKernel\HttpKernel->handle() #14 /app/docroot/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(30): Drupal\Core\StackMiddleware\Session->handle() #15 /app/docroot/core/lib/Drupal/Core/StackMiddleware/ContentLength.php(28): Drupal\Core\StackMiddleware\KernelPreHandle->handle() #16 /app/docroot/core/modules/page_cache/src/StackMiddleware/PageCache.php(118): Drupal\Core\StackMiddleware\ContentLength->handle() #17 /app/docroot/core/modules/page_cache/src/StackMiddleware/PageCache.php(92): Drupal\page_cache\StackMiddleware\PageCache->pass() #18 /app/docroot/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\page_cache\StackMiddleware\PageCache->handle() #19 /app/docroot/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() #20 /app/docroot/core/lib/Drupal/Core/StackMiddleware/AjaxPageState.php(71): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() #21 /app/docroot/core/lib/Drupal/Core/StackMiddleware/StackedHttpKernel.php(54): Drupal\Core\StackMiddleware\AjaxPageState->handle() #22 /app/docroot/core/lib/Drupal/Core/DrupalKernel.php(753): Drupal\Core\StackMiddleware\StackedHttpKernel->handle() #23 /app/vendor/symfony/runtime/Runner/Symfony/HttpKernelRunner.php(34): Drupal\Core\DrupalKernel->handle() #24 /app/vendor/autoload_runtime.php(32): Symfony\Component\Runtime\Runner\Symfony\HttpKernelRunner->run() #25 /app/docroot/autoload_runtime.php(22): require('...') #26 /app/docroot/index.php(13): require_once('...') #27 {main} ``` ## Root cause The `info` payload includes the raw `$GLOBALS`. The Composer-generated `vendor/autoload_runtime.php` runs in the global scope and assigns the application object to `$app`, which is therefore `$GLOBALS['app']`: ```php $app = require $_SERVER['SCRIPT_FILENAME']; // creates global $app ... $app = $app(...$args); // the resolved application (kernel) exit($runtime->getRunner($app)->run()); // → $kernel->handle() ``` While `$kernel->handle()` runs (i.e. during the agent request), `$GLOBALS['app']` is live and holds the service container. The container is intentionally not serializable (`Settings::__sleep()` throws), so `serialize()` in `OpenSsl::encrypt()` aborts. A recursive probe placed right before the failing `serialize()` confirms the entry point — every offending object hangs off the same path: ``` args/globals/app/*container/*services/… ``` This is not limited to `app`. Evaluating `array_keys($GLOBALS)` during a request shows that `autoload_runtime.php` leaves three runtime globals behind: ```php array_keys($GLOBALS); // => [ …, 'app', 'runtime', 'args', … ] ``` All three come from the same generated file: `$app` (the resolved application / service container), `$runtime` (the `SymfonyRuntime` instance) and `$args` (the resolved arguments, typically containing the `Request` object from `Request::createFromGlobals()`). `runtime` and `args` are also non-serializable. Any code that serializes the raw `$GLOBALS` on this bootstrap will therefore fail regardless of which of the three it hits first. ## Steps to reproduce 1. A Drupal 11.4.x site booting via `symfony/runtime` (default `docroot/autoload_runtime.php` → `DrupalRuntime`), DRD Agent (4.1.x-dev) installed and authorised (the problem also occurs during authorization). 2. From the dashboard, run the `info` action (or add/authorise the domain, which requires a successful `info`). 3. The agent logs the `LogicException` above; the dashboard shows *"Remote instance does not support DRD"*. Note: `domains_receive`, `collect used projects` etc. succeed, because their payloads contain no `$GLOBALS`. That is why already-connected domains keep working and the failure only surfaces when `info` is actually required (new authorisation, or the silent periodic run). Reproduced on two independent sites on the same platform, so it is not site-specific — it affects **every** agent running on the new bootstrap. ## Proposed resolution Do not let transient, non-serializable runtime state break encoding. Filter values that cannot be serialized out of the payload before `serialize()`. The attached patch adds a shared `removeUnserializable()` helper to `Crypt\BaseMethod` and calls it at the top of `encrypt()` in both crypt methods that serialize the payload (`OpenSsl` and `Tls`), so the fix is not duplicated and covers any future serialization-based method. A cleaner long-term fix would be to not collect the raw `$GLOBALS` in the info action at all, or to explicitly whitelist the scalar globals of interest (`$config`, `$settings`, `$databases`, …) instead of dumping everything — which would also drop the `app` / `runtime` / `args` runtime objects that have no value as monitoring data. ## Environments - Drupal 11.4.5 - DRD Agent 4.1.x-dev - PHP 8.3 - Drupal 11.4.5 - Drupal Remote Dashboard 4.1.x-dev - PHP 8.3 This issue was fixed with the help of A.I.