English
Cookbook
Use user isolation with existing sites
For a site created without Website Isolation, you can move it to a dedicated Linux user from Settings > Update Owner. Enter the new username (it is created automatically if it does not exist) and click Update; the site directory is moved to that user's home directory. See Site settings.
Uncommitted changes during deployment
This error can occur when files tracked by Git in the site directory have been changed by the application and would be overwritten by the new deployment.
To fix this, SSH into your site directory and run the following command to discard the changes:
git reset --hard && git clean -df
You should also review your application and fix any part of it that writes to a Git-tracked directory on your server. Otherwise, you may keep running into this error in later deployments.
Permission denied when writing files
When you upload source code as root (over SFTP or Terminal), the files may end up with the wrong owner, so the application reports Permission denied, cannot write its cache, or cannot accept uploads.
- Open the website's Overview page.
- In the Utilities group, click the Fix File Ownership tile, then click
Updateto give all files back to the website's Linux user. - If the error persists, click the File and Directory Permissions tile, enter the permissions for directories (Folder, usually
755) and files (File, usually644), then clickUpdate.
For WordPress websites, also check Website Lockdown: while it is enabled, core, plugin, and theme files are locked read-only.
Reapply the web server configuration
If the website's web server configuration was edited directly on the server or does not behave as expected, you can rewrite it from the settings stored in FlashPanel:
- Open the website's Overview page.
- In the Utilities group, click the Sync Config tile followed by your server's web server name (for example Sync Config Nginx).
- Click
Submitand follow the progress on the Events page.
WARNING
Manual edits made on the server will be overwritten. Put long-term customizations on the website's Nginx configuration page instead.
Website shows a 502 Bad Gateway error
See the step-by-step checks in 502 Bad Gateway Error.