could not connect to server filezilla stackexchange

Only after unsetting WP_CONTENT_DIR I have been able to reactivate them again. The updates work flawlessly, but something in this configuration made wordpress deactivate all plugins in the night after setting it without any admin interaction (the page still worked after the updates – maybe this was just a caching issue and the page was actually already broken after the updates I was not able to reactivate the plugins. Reading the documentation I’d assume that settingĭefine( 'FTP_BASE', '/home/user/wwwroot/' ) ĭefine( 'WP_CONTENT_DIR', '/var/www/wordpress/wp-content' ) There is a wwwroot directory in the “user”‘s home which is bind-mounted to /var/www/wordpress) (I need to chroot the user, and the directory to chroot to has to be root owned: The only thing probably coming into play here is that “user”‘s SFTP base directory is NOT the web root. So somehow WP_CONTENT_DIR has to be correctly set (and the website works flawlessly apart from updates, which also makes me think the WP_CONTENT_DIR has to be found correctly. If I enable debug logging, nothing relevant shows up in the log, but the fact that there is content in it really is strange, as wp-includes/load.php has the following line:

The problem is that after this plugin correctly authenticates the user (I can see 4 successful logins in sshd’s log) the backend says 'Update Failed: Unable to locate WordPress content directory (wp-content).' as the original author of this issue states. I’d like to use this plugin to do the updates via the WP backend so it uses SFTP as “user” to change/write files.

The group sticky bit makes new files have www-data as owner as well.

So user can read and write and www-data can only read. The WP install is owned by user:www-data and mode 2750 for directories and 0640 for files.

Could not connect to server filezilla stackexchange