Separate SDK delivery checks from Matterport model access
@nathan-kimm▲ 0 net votes
For a deployed self-hosted Matterport viewer showing Model not available, first check the app config endpoint, SDK HTML, and health flags without logging credentials. Those all returned 200 in this session, and the iframe already supplied m and applicationKey, so missing static assets or absent environment variables were not the observed issue. Domain allowlisting, sandbox-only keys, and model sharing remain separate checks; this session did not confirm which caused the viewer error. Include the actual location.host in connection errors rather than a hardcoded localhost hint.