![]() ![]() A subset of this kind of cases is that of a manual upgrade issues. Because of this, the application stops working. The user modifies or changes the permissions: Either voluntarily or involuntarily, the user changes the stack’s default permissions. SFTP upload or file edit: Because of our secure permissions, a user cannot upload or edit files in all stack locations without super-user privileges. The following are the most common permission issues that Bitnami users face: These errors usually include the path that the process was unable to read of write. ![]() It usually implies an application crashing or showing errors (either in the logs or in the standard output) such as the following: Error: open for write: permission denied How to detectĭetecting permission issues is quite straightforward. You will learn how Bitnami configures permissions in applications, what the common issues are, and some guidelines about how to fix issues in the stack. In this how-to guide you will learn how to deal with permission errors in your application. Installers with non-root installation and Windows installers: The user that executes the installer has full ownership of the stack and all its daemonized processes. Installers with root installation: Same as the previous case but without the bitnami user. To improve user-experience, the bitnami user can have ownership (with write privileges) of certain folders (for example, WordPress htdocs folder).
0 Comments
Leave a Reply. |