@d19dotca I can confirm his fix works as well!

@lonk said in Apache, OLS and Nginx-Custom Benchmarks: redis is already apart of Cloudron Yes & no, Yes is part of the cloudron addon, but it can be integrated in different way. You can use it for dynamic cache (as cloudron use in there apps), behind the php, db lvl. You can use it as a Full Page Cache (similar to what Cache Enebler do but in RAM and not in local disc). php lvl You can use it for partial page caching, in this case is at webserver/proxy lvl. Redis is just a "database" in RAM, you can use it to store what you want, Redis is not a cache, but you can use it as it was one.

Perhaps try the All in One Migration plugin, at least couple of us have successfully used that to migrate WordPress to Cloudron. See e.g. this thread on How to move Wordpress.

@jdaviescoates You can just create app password as your own account, no need to create a new user. The idea of app password is that the password only works for that one app. It won't work on the dashboard or any other app. The usual use case is for mobile apps or 3rd party client apps, which you don't want to trust with your primary cloudron password. It also has an advantage that you can revoke/delete the password anytime.

Adding my two cents in here for anyone who comes along. You can also access the DB using desktop software like Sequel Ace and it's incredibly efficient to me.

@rahim I think best solution is to do this process via command line. Is clean, safe and you can upload any DB size. Of course, each installation have specific way to follow, depends on specific case. Eg. if origin domain is the same or different to destination domain. Also, If both, source and destination, are live. In this case, you've to approach the DNS A field to validate domain on Cloudron. This below is my procedure, assuming that source and destination have the same domain name and that domain is live. From the source server you need to export: mysql.dump wp-content folder Then you've to create a new instance on Cloudron called "swap". Eg. swap.mydomain.com. You upload mysql dump to /tmp/ via terminal, and then you import sql DB using command line (you can find info here). Then you have to upload "wp-content" folder. You can do via FTP or also via Cloudron File Manager. You can upload zip archive and then unzip inside main wp folder. When you have swap.mydomain.com working, you can use the function app "Backups", using "Clone" on the main domain. Just before cloning, you have to change A fields in DNS panel, so Cloudron can validate new domain. (You can skip this step if your domain is configured with DNS provider (Eg. Cloudflare or others listed). Let me know if is all clear and if I can help you.

There's more deep rooted issues - https://github.com/heiglandreas/authLdap/issues/194 . The package itself is wrong and unfortunately wp admin suggests it as an update. Breaking a lot of things.

@girish Nope, tried to debug it. Tried to even repair it. In the end a reboot fixed the problem, but that was pretty weird.

@jodumont I think just having any recommended snippets in the docs would suffice for most, no? Then just copy/paste any you want to use using the File Manager (after making a backup in case it breaks something).

@dreamcatch22 You might have to restart the app after making php.ini changes. Apart from that, you can install something like https://wordpress.org/plugins/php-info-wp/ which should give you phpinfo output to verify is the extensions are enabled.

Hm surfer will send cache-control: public, max-age=0 so I am not sure why it would cache as such, the etag also should have changed if the source content was updated.

@moocloud_matt Thanks for the heads up. The project is still early enough where I can make the switch.

The amazing self solving topic

Right, for the moment it accepts everything till 403

I agree with both of @girish's assessments of the file for the time being. But that doesn't mean that when Cloudron does support multi-site in the future, we can't assess multisite constants. So thanks for bringing it up! It lead me to that really interesting and eye-opening wp-config.php on Github.

@ketchalegend I see. With the above htaccess, I got curl -X POST -H "Authorization: Bearer 1234567890" https://wp.domain.com/wp-json/jwt-auth/token {"success":false,"statusCode":403,"code":"jwt_auth_invalid_token","message":"Wrong number of segments","data":[]} So looks like the route is working.

Follow up from the customer: "The issue here turned out to be that in Wordpress, WP Rocket caching plugin was used. This plugin automatically starts to preload the cache of each page once something in the site has been updated. The preload itself causes some stress on the CPU and maybe some other processes. Turning off the plugin, the products were sent for less than 2 mins." They are working with the WP Rocket team to find a workaround.

@Lonk said in WordPress Developer vs LAMP PHP 7.4: could test it in the same conditions yes, I got that after, I just simply did'nt actived it inside WordPress but at the end it is doing what the WordPress_Dev container doing manually.

@d19dotca Wordpress is my favorite and Cloudron is my new development passion so I’m happy to troubleshoot WP stuff to find edge cases that Cloudron may need to account for. I am very for making WP the best it can be on Cloudron. ️ I’m happy I’ve been able to help troubleshoot with you!

@imc67 said in Wordpress (unmanaged) CRON interrupts product loading: If you set it to 5 then WP site check is complaining that there are missed events. Because either WP or plugins can create 1 minute tasks. Yes, cron scheduled Wordpress can be scheduled down to the minute. But they're expected to be missed. The default WP-Cron interval is "whenever the next person visits the site, run all the scheduled events that are in the past and haven't been run" (the one that Cloudron rightfully uses the WP-CLI and disables the native WP-Cron). That's pretty horrible, but that's what Wordpress installs expect the environment to be at default. So, the WP Site Check says that's notable, that wp-crons don't get run at the minute they're specified? If the WP Health Status Page actually says that, then Wordpress devs clearly think 1 minute (or a hugely popular site) is the best interval.