Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
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.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
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.
Source: https://github.com/fastly/fastly-magento2/issues/163
Source: https://github.com/fastly/fastly-magento2/issues/163
Shows how to fix 503 Service Unavailable on Fastly Magento2 admin endpoints (Edge Dictionary ListAll). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Use when a call returns 503 temporarily_unavailable or a body whose retry kind is none.
Fixes this failure: fix the WSUS server side, not the client: restart the WSUSPool application pool in IIS, raise its private memory limit, and check the SUSDB for timeouts.