@micmc No, I'm not using a WP Reset Plugin. Yes, they're all Multisite Compatible to my knowledge. I'm going debug everything and see what I can come up with. I appreciate the feedback, will report back here with any issues.

@yoyo2p said in WPvivid Won't restore my WordPress site: developer version of wp vivid No, you want the Developer version of the Cloudron WordPress app, instead of the "Managed" (aka so locked down it doesn't actually work) version. In the app store, choose WordPress (Developer) instead of just WordPress [image: 1660299652529-screenshot-from-2022-08-12-11-17-31.png] This distinction seems to serve only to confuse people and leads to all sorts of headaches. IMHO the managed WordPress shouldn't exist and only the WordPress (Developer) app should be in the app store. Or, at the very least "WordPress (Developer)" ought to be renamed to just "WordPress", and the existing managed WordPress app, which is currently called just "WordPress" should be renamed to "WordPress (Managed)" and a message should be added to the install page warning them that they probably want the unmanaged one that actually works, not the locked down one that mostly just doesn't.

I think I had that issue a long time ago and it was something to do with the Auth-LDAP plugin not saving the passwords in the database, and so if that plugin gets disabled then we can't login 'offline'. The WP CLI will be the best way to work around it I think, as it seems you did already also with the password reset tool too!

There was a UI bug in the dashboard, which I have fixed here - https://git.cloudron.io/cloudron/dashboard/-/commit/7291d5a9ecf3ce1a450f08f59c075e453ca0297a

@JUVOJustin Have you tried just putting the public IP of the server in htaccess? When openvpn channels the request to wordpress, it will see the public IP of the server itself and not the private/tunnel IP.

@jdaviescoates yep that´s the plugin. To be honest i have no clue about ldap I actually don´t know how i should set up the plugin to work with the cloudron groups. Thats what my question is mainly about. If it is an issue with the plugin i could reach out to the developer.

@girish Thanks very much, worked! Thanks for the quick replies!

@martinkbs Ah very interesting! I'll have to look deeper into that option. Pretty cool looking. Thanks for the idea.

NVM I found a thread that answer this. Based on my current understanding, the cloudron dashboard shows cloudron package updates. For wordpress core in developer edition we have to control that update.

@robi I think this says it all: https://git.cloudron.io/cloudron/wordpress-managed-app/-/issues/32

@scooke Hello as far as I know you should have this running on WP multisite and thus moving it to Cloudron should be as easy as migrating any WP site. That being said, it may depends on how you have set your multisite either using sub domains or sub directories. I'm running a multisite using sub directories on Cloudron for a few years without any problems. There has been a few discussions here on the forum about the capacity of using it with sub domains, however I'm not sure if anything has ended up with a solution for this issue. Maybe, you can make a search for that on the forum, which I will check on myself as well as you remind us about it.

I just tried it, works great. Glad we got it sorted. Thanks for the help everyone.

Thanks for sharing the detailed solution here!

@marcusquinn I think this thread was about adding LDAP to WordPress Developer. We added that long time ago. But @d19dotca reported recently that LDAP plugin is not managing the roles properly - https://forum.cloudron.io/topic/6625/logging-in-resets-role-to-editor-instead-of-administrator-or-shop-manager . I have to investigate that.

@girish thanks for your help

@vova have you solved it?

@girish It's a shame, I'll have to change the plugin

@girish - It seemed like tonight it finally updated. Not sure why tonight over any other night though when it's been out for about 2 weeks and I check for auto-updates M-F each night, but it looks good now.

@girish So I replicated what you had done in the demo. So that seems to be working now -- after I disabled the plugins we have installed. I'm going to work through and go one-by-one on the plugins and see what is going on. This seems to be a really odd issue.