A clear path forward
My published app is returning 403 Forbidden errors—how do I fix it?
A 403 Forbidden response means the request was refused. Check cookies, sign-in requirements and app access restrictions.
VerifiedRH-0048v2
- Large request headers: too many cookies may make the extra information sent with a request too large. Clear cookies for the app's domain and try again.
- Missing authentication: check that the request includes the required login token or session.
- Access restrictions: check whether the app is configured to block that traffic. See Private deployments and External access tokens.
For a more detailed diagnosis, paste the relevant deployment logs into a new Agent chat. Remove secret values first.
Did this get you unstuck?
Still stuck?
See what to include and open a support ticket.
Still stuck?
See what to include and open a support ticket.If this page did not solve it, contact Support and describe what you were trying to do and what happened, in your own words. You do not need to gather anything in advance.
Include in your ticket, if you know it
- What you were trying to do
- What happened, in your own words
- What you have already tried, if anything
Copying is optional. No ticket is submitted and no files are attached automatically; send your request in the support form.
Do not include passwords, API keys, or payment-card details.