Troubleshoot publishing issues
If a live page looks wrong, confirm it is Published (not Draft), Site home points at the right page, hard-refresh browser cache, and check Media files finished processing—maintenance mode or password gates under Settings → Privacy & security can also block public access.
Most publish problems come from draft status, the wrong Site home selection, browser cache, or media that has not finished processing. Work through these checks in order before contacting support — you will often fix the issue in minutes and know exactly what to report if you still need help.
Prerequisites
Verify status: Dashboard → Pages (publish column, Site home)
Site URL: Dashboard → Settings → General
Privacy gates: Dashboard → Settings → Privacy & security
Implementation steps
- On Pages, confirm the page status is published — Publish active in the editor — not Draft.
- Confirm exactly one page has Site home enabled for your root URL.
- Hard refresh the browser with Cmd+Shift+R on Mac or Ctrl+Shift+R on Windows.
- Open the site in a private or incognito window.
- Check Settings → General for the correct subdomain. If you use your own domain, confirm status is Connected and follow Connect a custom domain for DNS and SSL (including Host / Name for TXT records).
- In Media, confirm images on the page finished uploading and show thumbnails.
- Re-open the editor, click Save Page, then Publish again.
- If the issue persists, note the URL, expected versus actual behavior, and contact support via https://www.artinstack.com/contact.
What you'll see
You identify whether the issue is draft state, cache, site home, DNS, or asset processing — and either resolve it or escalate with clear details support can act on quickly.
If visitors see a password or maintenance screen
Maintenance mode or password-protected site settings under Settings → Privacy & security block public access even when pages are published. Custom domain SSL often completes within a few minutes after the correct TXT records are in place (CNAME can take longer) — see Connect a custom domain. During validation some browsers may show security warnings.
Verifying your setup
- Root cause identified — draft, cache, site home, DNS, privacy setting, or media.
- Homepage or target page loads correctly after the fix, or you have details ready for support.
