FerndeskFFerndesk
Just now

Serve the widget SDK and its API from the help center's custom domain

Customers on locked corporate networks can reach their own help center domain but not static.ferndesk.com or engine.ferndesk.com, so the widget never loads inside their app.\n\nFERNDESK_SDK_SRC only moves sdk.js. The engine origin is baked into the bundle at build time, and the widget fetches its metadata and public API from there, so pointing the script tag somewhere else does not help.\n\nAsked for: a first-party path on the help center's custom domain (e.g. help.example.com) that serves sdk.js and proxies the widget metadata and public API, or a runtime host override for the API origin alongside FERNDESK_SDK_SRC.\n\nReported by EveryoneSocial, whose regulated customer's network blocks both Ferndesk hosts while gr-support.everyonesocial.com is reachable.
PendingPending