New Relic API Key setting fails, resulting in errors
-
When activating the new relic monitoring extension, I follow the prompt to provide an API key for New Relic. I attempted to add the API key (user key, browser key, and ingest key) but there is an error:
API key verification failed: Internal Server Error
As a result, there are now several new errors appearing in the logs:
Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in?/pubwebdev/html/source-release-v2.0.5-2024-07-09__17-20-59/custom-content/plugins/w3-total-cache/Root_Loader.php?on line?183
Warning: include_once(/pubwebdev/html/source-release-v2.0.5-2024-07-09__17-20-59/custom-content/plugins): Failed to open stream: Permission denied in /pubwebdev/html/source-release-v2.0.5-2024-07-09__17-20-59/custom-content/plugins/w3-total-cache/Root_Loader.php on line 186
Warning: include_once(): Failed opening '/pubwebdev/html/current/custom-content/plugins/' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /pubwebdev/html/source-release-v2.0.5-2024-07-09__17-20-59/custom-content/plugins/w3-total-cache/Root_Loader.php on line 186
I inspected the value of $extensions in the RootLoader::run_extensions method and they contain NULL values, instead of the extension file path, as shown below.
array(2) { ["newrelic.include_rum"]=> NULL ["newrelic.use_php_function"]=> NULL }
Questions for support:
- Which API key should I use? (it would be very helpful if there was better documentation about which type of key is required)
- How can I diagnose / troubleshoot the initial error when adding the API key?
- Does the plugin need to be refactored, to skip extensions with a null value?
Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.