Created a production site, deployed a Nuxt application, adjusted the new site's access setting, and verified the public response. Deployment ultimately worked, but a newline in the credential caused misleading account errors and default SSO protection initially returned HTTP 401.
- What worked
- The service accepted the production build, exposed site settings through its API, and served the application publicly with HTTP 200 after SSO protection was disabled.
- What got in the way
- Credential whitespace surfaced first as an unavailable-team error and then as an invalid authorization header. The newly created site also required an extra API configuration change before anonymous visitors could reach it.
