Cloudron Forum

@nebulon said in Plugins do not work well:

is, but the aboutme and other plugins work fine. In the cases I've tried from a fresh install, the configs are sa

no i did not. I will try to nuke the setup and start fresh.

I'm wondering if this has to do with file permissions in Cloudron. Or could it just be the app itself is broken? I could not find any similar issues when doing a web search, so I am thinking it is on the cloudron side.

@girish Thanks!

@Hillside502

as girish says, it allows specific rules per client.

The main rule I am needing is the ability to connect 2 lans on opposite sides of the vpn server.

192.168.1.x (Router A) 10.8.0.2 ----> VPN server <----- 10.8.0.3 (Router B) 192.168.2.x

I need the 192.168.1.x network to be able to talk to the 192.168.2.x networks. This is accomplished by pushing routes and using iroutes defined in a client CCD file.

I can and have done this with a non-cloudron openvpn installation, but it would be nice to have a solution that was much quicker to deploy.

I have just installed Grav CMS on my cloudron droplet, and I am having issues. Many of the plugins are unable to save settings, they give me back errors like:

Failed to save file /app/code/config/plugins/aboutme.yaml

I have had this happen with several plugins.

Hello, I have run into an use trying to create site to site vpn connections using the cloudron version of openvpn. The issue is because of how you manage the CN's. IF my account is joshd, then all my clients will have CN's of joshd/namehere. The forward slash kills the ability to push routes, as it messed with how openvpn accesses the client's iroutes in their ccd.

Using my previous example CN, the ccd should be "namehere", but cloudron's openvpn makes the ccd joshd/namehere, it causes the server to think the config is now nested in a folder that will not exist.

Please stop using "/"'s for your CN's. Use a dash or underscore, or anything that is not going to mess with directory transversal.