@murgero Thanks for your suggestion! I have put the new healthcheck url in https://git.cloudron.io/cloudron/wordpress-app/commit/45dc91cd7868bd2e66ea726f0968c4752279812e . Will push out the update slowly and see if it causes any issues

@mariadjohnson0 On Cloudron, the code of all the apps are "read-only". We do this because rolling updates is an important feature of Cloudron. For example, if you change the code of an app, Cloudron cannot know how to update the app. We followed the same approach for WordPress. The code was read-only. WordPress itself could be extended by installing plugins. When a new WP release comes out, we push an update. We call this "Managed WordPress". This app does not have SFTP access. However, many users have requested that WordPress code be modifiable. For example, they use WP as the starting point for building web sites. For this case, we created a new app called "Unmanaged WordPress". In this app, the WP code is modifiable. This comes with the restriction that cloudron will not update the WP code by itself. You, the sysadmin, has to track and update WP (using the WP dashboard, for example). This app also has SFTP access. (You can view the Unmanaged WP, by going to Settings -> Enable Community apps).

@ruihildt It's a wordpress update

We have published a blog post with more detailed migration instructions at https://cloudron.io/blog/2018-11-05-wordpress-migration.html

@ahkg the reason for whitelisting 172.18.0.1 give access to all requests, is that this is the ip of the Cloudron internal gateway into the subnet where all apps are running. Unfortunately for your case the cloudron healtcheck also comes via this gateway. I think your htaccess file needs to check for the X-Forwarded-For header to check against the correct inbound address.

I will mark this as solved, since it is tracked on the issuetracker already.

This should be possible to adjust in the smtp settings of the wordpress instance. You can find those at https://<domain>/wp-admin/options-general.php?page=wp_mail_smtp.php