Make sure that the Apache's mod_rewrite is enabled on your server.
Make sure that the AllowOverride Apache's directive is set to All in your server's apache2.conf file (or in the delegate file for apache configuration on your server).
Make sure that the /.htaccess and the /public/.htaccess files are uploaded on your server
If you have a 403 error on your Nginx environment, please check out these articles to learn more about the Nginx configuration:
If the error persists, please contact your hosting provider for more information and get a suitable help about that.
This error is related to LiteSpeed (LiteSpeed Web Server) or similar servers like OpenLiteSpeed.
If you receive an error 403 like in the screenshot above, this means that the script's files contents are not yet called before the error occurs, and you have to fix this error on your server (by contacting your hosting provider to get a suitable help).
NOTE: Usually this error is caused by wrong files permissions related to your hosting provider rules. Please check out these links for more information about that:
If the issue persists after fixing the files permissions, you must disable the mode_security on your server:
Otherwise, if restrictions cannot be properly configured, we strongly recommend to move to a classic web server.
This error is related to services like: Cloudflare, Imunify360, etc.
This kind of service is often more discreet and sometimes only blocks pages or static files (such as CSS, JS files, etc.). If you notice that the pages of your website are displayed without CSS styles and in a disordered way, it is very likely that the protection service of your server has not been configured to authorize requests coming from the files of your new website. You must therefore review this configuration on your server or contact your host for more suitable help.
Also if you receive errors 403 after seeing a security page like the screenshot above, this means that the Cloudflare (or similar system like Imunify360, etc.) service is installed on your server and blocks some of the script's requests. You have to fix the issue on your server (by whitelisting all the script's requests or by contacting your hosting provider to get a suitable help).
If the problem is not resolved, you must disable the mode_security on your server.
Otherwise, we strongly recommend to add all the script's files in the service's whitelist files, or we recommend to remove/disable the service on your server to avoid any request ban.