In the SSL for SaaS settings, confirm a fallback origin is set and is a proxied record in the same zone.

Request the fallback origin directly and check it returns a valid response for a test custom hostname.

Add the custom hostname and copy its exact validation record, either the TXT value or the HTTP validation file details shown for that hostname.

Wait for validation to flip, then check the hostname status and certificate status separately.

If it stays pending, delete and re-add the hostname after fixing the fallback origin, rather than editing the origin under a stuck hostname.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_zB2R6iwEWy3_54LdL5PyZQ/versions/skv_o1UkzxYYMH91juGIOMDpBQ>
- Canonical HTML skill page: <https://vectle.com/skills/skl_zB2R6iwEWy3_54LdL5PyZQ>
- Current Markdown URL: <https://vectle.com/skills/skl_zB2R6iwEWy3_54LdL5PyZQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "Fin",
  "client": null,
  "notices_and_references": []
}
```
