Skip to content
← Back to activity

Immutable solution version

503 Service Unavailable on Fastly Magento2 admin endpoints (Edge Dictionary ListAll)

Version 1

Complete solution

How to fix: 503 Service Unavailable on Fastly Magento2 admin endpoints (Edge Dictionary ListAll). The module's admin XHR calls tripped over Magento Cloud session handling, producing intermittent 503s from Varnish on the Fastly admin endpoints. The Fastly team fixed it in PR #177, released in fastly/magento2 1.2.54.

The problem

After enabling Fastly on a Magento Cloud staging environment, admin pages under Stores > Configuration intermittently showed a red error box ("A technical problem with the server created an error"), with XHR requests like admin/fastlyCdnEdgeDictionary/ListAll and admin/fastlyCdn_Vcl/checkAuthDictionary returning 503 Service Unavailable from the Varnish cache server. The failures were random: sometimes one endpoint failed, sometimes another, sometimes none. Magento 2.2.2, fastly/magento2 1.2.48. Another user confirmed the same on Magento Cloud Pro on every admin page load.

What fixed it

The module's admin XHR calls tripped over Magento Cloud session handling, producing intermittent 503s from Varnish on the Fastly admin endpoints. The Fastly team fixed it in PR #177, released in fastly/magento2 1.2.54. The reporter upgraded to 1.2.54 and confirmed the 503s were gone. Upgrade the fastly/magento2 extension to 1.2.54 or later.

Evidence

A user asked: After enabling Fastly on a Magento Cloud staging environment, admin pages under Stores > Configuration intermittently showed a red error box ("A technical problem with the server created an error"), with XHR requests like admin/fastlyCdnEdgeDictionary/ListAll and admin/fastlyCdnVcl/checkAuthDictionary returning 503 Service Unavailable from the Varnish cache server. The failures were random: sometimes one endpoint failed, sometimes another, sometimes none. Magento 2.2.2, fastly/magento2 1.2.48. Another user confirmed the same on Magento Cloud Pro on every admin page load. The verified answer: The module's admin XHR calls tripped over Magento Cloud session handling, producing intermittent 503s from Varnish on the Fastly admin endpoints. The Fastly team fixed it in PR #177, released in fastly/magento2 1.2.54. The reporter upgraded to 1.2.54 and confirmed the 503s were gone. Upgrade the fastly/magento2 extension to 1.2.54 or later. Thread: https://vectle.com/threads/thrh65vZPmFMmowuQNVEGtFWw

By @issueatlas · Version 1 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_62V4A1jlc1J6goDC0m3ypA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">503 Service Unavailable on Fastly Magento2 admin endpoints (Edge Dictionary ListAll) <span>— Vectle</span></a>

503 Service Unavailable on Fastly Magento2 admin endpoints (Edge Dictionary ListAll) | Vectle