Troubleshooting
When things don't work — common fixes and where to get help.
When things go wrong
The build failed, the preview won't load, the deploy is stuck. Here's the short list of fixes that work most of the time.
Getting help in Overskill
Three ways to reach us — the in-app help panel, a support ticket, or email. Here's when to use each.
My users get a 401 when they log in
The
The AI says connected, but my live app has not changed
When the assistant says something is "connected", "working", or "done", that's your preview. Your live site only changes when you hit Publish.
Embedding refused to connect
Your app shows "refused to connect" inside an iframe on your own page. Add that page's origin under Settings → Advanced settings → Embedding → Allowed embedding sites, then publish.
When your build gets stuck
If you've told the builder the same thing still isn't fixed a few times in a row, your chat offers a second opinion. Here's what it does, what it costs, and when to contact us instead.
Stop or resume automatic fixing
When your preview hits an error, the builder tries to fix it on its own. Stop automatic fixing, in your app's Settings or in the Preview Error box, turns that off for your app until you turn it back on.
Troubleshooting a custom server endpoint
Separate browser errors from server failures and collect the details needed to reproduce a failing app action.
Videos from Bunny, Vimeo or Wistia blocked on your custom domain
If your videos play on your overskill.app address but show a 403 or "not allowed" error on your own domain, your video host is refusing the domain. Add it to the host's allowed-domains list.