Can't Publish/Deploy
Publishing & Deployment · 12 articles
Can I publish multiple projects at the same time?
Yes, each project can be published independently. Publishing one project doesn't affect others. Each project gets its own Lovable subdomain or custom domain.
My deployment keeps failing.
Check for build errors in your project—the AI may have introduced code issues. Try reverting to a recent working version and publishing that. Review error messages in the deployment logs. If you can't resolve it, share the error details with support.
Publishing is stuck on 'uploading' or 'checking.'
Wait a few minutes—large projects can take time to upload. If it's stuck for more than 10 minutes, refresh the page and try again. Contact support if the issue persists.
The publish button is stuck or not responding.
Try refreshing the page and clicking 'Publish' again. Clear your browser cache or switch browsers. Check if your project has build errors by reviewing the latest chat messages. If the issue persists, contact support with your project URL.
Can I restrict who can access my published app?
By default, published apps are public. To restrict access, add authentication (login page) using Supabase email/password or Google OAuth. Business/Enterprise plans offer workspace-only publishing—restrict access to workspace members only. Alternatively, deploy to a custom domain and use network-level access controls outside Lovable.
Can I see analytics for my published projects?
Lovable's built-in analytics are limited. For detailed analytics, integrate Google Analytics, Mixpanel, or similar via a prompt: 'Add Google Analytics.' Lovable will add the tracking code. Project Settings shows basic info like project URL and visibility, but not traffic metrics.
Can I use the Security view for published projects?
Yes, you can use the Security center to review security findings for any project before or after publishing. Security issues exist in your code regardless of deployment status. Address critical findings before publishing to a production domain. The Security center helps you maintain code quality at any stage.
Why can't I publish my Lovable project?
Common reasons: (1) Syntax errors in your code—check the Cloud tab → Logs. (2) Missing required fields or unresolved dependencies. (3) Database connection issues if using Supabase. (4) Quota limits on free/Pro plans. Use the 'Try to fix' button (FREE, no credits) to scan logs and attempt a quick fix, which resolves ~60% of simple issues. For complex issues, contact [email protected].
My published site is down and users can't access it.
Check status.lovable.dev for any service incidents. Verify your domain's DNS records are still pointing to Lovable. Try accessing your Lovable preview URL—if that works, the issue is domain-related. Contact support immediately for production issues.
Will my site go down if my subscription expires?
Your published site may go offline after your subscription ends. Resubscribe to restore it. Your project code and data are preserved regardless of subscription status.
How long does it take for published changes to go live?
Changes typically go live within a few minutes of publishing. If you're using a custom domain, CDN or DNS caching may add a short delay. Clear your browser cache to see updates faster.
I published my changes but the live site still shows the old version.
Browser caching is the most common cause. Hard-refresh (Ctrl+Shift+R) or test in incognito mode. If you're using a custom domain, DNS caching may also cause delays—wait 15–30 minutes. Verify in the dashboard that the latest publish was successful.
