Skip to content

Advanced Reporting endpoint – empty reply

Subject

Advanced Reporting endpoints return TLS close_notify / no HTTP response → Magento MBI service CURL connection error #52

Priority

P3 (Standard) — Production admin feature unusable, storefront unaffected. (Adjust if this blocks operations.)

Product / Area

Adobe Commerce / Advanced Reporting (Magento Analytics module) (Adobe Entwickler Webseite)

Description

Since 20 Aug 2025 our Magento Admin Reports → Business Intelligence → Advanced Reporting fails with an exception. Magento attempts to fetch an OTP from https://advancedreporting.rjmetrics.com/otp and immediately receives TLS close_notify with no HTTP response. The same behavior occurs when requesting /report.

This appears to be an upstream endpoint issue (or deliberate drop of unauthenticated requests) rather than a local network problem:

  • Reproduced from multiple independent hosts and networks (including non-corp servers).
  • TLS/SNI is clean; certificate is valid for *.rjmetrics.com.
  • curl -v shows successful TLS handshake, then TLS alert, close notify, and no HTTP headers/body → curl: (52) Empty reply from server.

Steps to reproduce

  1. In Magento Admin: Reports → Business Intelligence → Advanced Reporting (or Dashboard → Go to Advanced Reporting).
  2. Alternatively, Magento tries POST https://advancedreporting.rjmetrics.com/otp via the Analytics module.
  3. Error is thrown in the backend (stack trace below).

Expected result

  • /otp returns a normal response (when called by Magento with token) and Admin opens /report?otp=… (hosted Advanced Reporting UI). (Adobe Entwickler Webseite)

Actual result

  • Magento throws: MBI service CURL connection error #52: Empty reply from server and cannot open Advanced Reporting.

Evidence (commands & output)

curl -v --http1.1 https://advancedreporting.rjmetrics.com/report -o /dev/null
* Connected to advancedreporting.rjmetrics.com (44.207.154.102) port 443
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
> GET /report HTTP/1.1
<no HTTP response>
* TLS alert, close notify (256)
curl: (52) Empty reply from server

openssl s_client -connect advancedreporting.rjmetrics.com:443 -servername advancedreporting.rjmetrics.com -brief
CONNECTION ESTABLISHED
Protocol version: TLSv1.3
Ciphersuite: TLS_AES_128_GCM_SHA256
Peer certificate: CN = *.rjmetrics.com
Verification: OK

Magento error (stack trace excerpt)

Exception: MBI service CURL connection error #52: Empty reply from server
in vendor/magento/module-analytics/Model/Connector/Http/Client/Curl.php:77
Called from OTPRequest->call() → ReportUrlProvider->getUrl() → Controller Adminhtml Reports Show
[full trace attached in the case]

What we already tried

  • Admin: Advanced Reporting Disable → Save → Enable → Save, then System → Extensions → Integrations → “Magento Analytics user” → Reauthorize (resource: Analytics → API only).
  • Verified prerequisites (public HTTPS base URL, Secure URLs enabled, cron running, single base currency) per Adobe docs/troubleshooter. Still fails at the external endpoint with empty reply. (Experience League)

Environment

  • Magento: , Edition: <Adobe Commerce / Open Source>
  • Hosting: <Cloud / on-prem>
  • PHP:
  • Region/Timezone: Europe/Berlin
  • Affected since: ~<time window on Aug 20, 2025>
  • Outbound egress: advancedreporting.rjmetrics.com:443 allowed
  • No SSL inspection on tested paths (see openssl s_client above)

Request

  • Please check availability and behavior of https://advancedreporting.rjmetrics.com/otp and /report endpoints.
  • Confirm whether there is a service/CDN issue or a new requirement (e.g., rejecting unauthenticated GET/HEAD) causing the immediate TLS close without HTTP response.
  • Provide guidance/workaround and ETA for restoration.

Attachments (I can upload in the case)

  • Full curl -v logs from multiple networks/hosts
  • Full Magento exception log
  • Screenshot of Admin error

How to submit (step-by-step)

  1. Go to Experience League Support and sign in with your Adobe ID.
  2. Click Support → Submit a support case → choose Adobe Commerce.
  3. Paste the ticket text above, set priority, and attach logs/screens. (Experience League)

Tip: include a link to the Adobe Status → Adobe Commerce page in your case notes to show you already checked for incidents. (status.adobe.com)

Want me to tailor the ticket with your exact Magento version/edition and timestamps? If you share those, I’ll drop them into the template for you.