403 error in Liferay SaaS project
Written By
Jamilly Macedo
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- Sometimes, Liferay SaaS clients report that they are unable to perform simple tasks like uploading files or saving changes.
- When checking in the Network tab of the browser console, we see that 403 error is reported.
Resolution
- These errors could indicate a block by Cloud Armor (WAF used in Liferay SaaS).
- Please create a ticket requesting the team to updated the rules in WAF.
- To help with resolution, add a HAR file collected at the time the error is reported.
Did this article resolve your issue ?