Hi all!
Brand new to the Cloudron sphere.
I wanted to install a script that I often use on other servers to whitelist countries (https://github.com/friendly-bits/geoip-shell) except that since I installed it, my cloudron no longer has access to the store.
1 - In which country is the store located?
2 - Is there a way in Cloudron to whitelist or blacklist countries?
I only saw the IP solution.
Thank you all!
Hello everyone, I just installed the new VPN version.
Is it possible to have a custom route in Wireguard similar to OpenVPN?
Let me explain: In OpenVPN, I used the following configuration:
# This makes clients redirect all the traffic via the VPN.
#push "redirect-gateway def1 bypass-dhcp"
#push "redirect-gateway def1 ipv6 bypass-dhcp"
pull-filter ignore redirect-gateway
This setup allows clients to communicate with each other while still using their own internet access.
I couldn't find a similar option for Wireguard.
I couldn't find any information about this in the documentation.
Second question,
I already have OpenVPN installed on my Cloudron, with clients currently using it.
Can I use the entire configuration stored in /app/data/ to migrate my clients seamlessly?
Thank you in advance, and I wish you all happy holidays!
+1 for zabbix
Hi, I tried:
chmod a+rw /mnt/volumes/04067a3544294e0fa162392e066337cf/media
It didn't work.
I tried:
export MOUNT_DIR=/mnt/volumes/04067a3544294e0fa162392e066337cf/media
chmod 777 $MOUNT_DIR
hgrp media $MOUNT_DIR
chmod g+s $MOUNT_DIR
setfacl -d -m g::rwx $MOUNT_DIR
setfacl -d -m o::rx $MOUNT_DIR
touch $MOUNT_DIR/test-file
ls -l $MOUNT_DIR/test-file
Output:
-rw-rw-r-- 1 root media 0 Aug 7 15:53 /mnt/volumes/04067a3544294e0fa162392e066337cf/media/test-file
root@liello:/mnt/volumes/04067a3544294e0fa162392e066337cf/media# ls
partage test-file
root@liello:/mnt/volumes/04067a3544294e0fa162392e066337cf/media#
It doesn't work. Is there something I did wrong? Thanks.
@BrutalBirdie Hi! Great job! Thanks.
Hello everyone,
I have a small issue.
I’m on an OVH VPS with an additional disk mounted under /dev/sdc1 by cloudron.
I have some applications installed, and everything is working fine.
At the root of my additional disk, I created a folder named "media" that I want to share with some applications. I ran a chmod 777 -R media.
I added a new volume in Cloudron:
Mount type: filesystem
Local directory: /mnt/volumes/04067a3544294e0fa162392e066337cf/media
The status indicator is green, but when I click to explore the folder, it appears empty.
Is there a trick to get this shared folder to work properly?
Hello everyone,
I’m having an issue with Cloudron when trying to use the OVH DNS API integration.
For some time now, I haven’t been able to add my OVH API credentials into Cloudron. Because of this, I have to update all DNS records manually.
I always follow the official documentation:
https://docs.cloudron.io/domains/#ovh-dns
For a new domain, to avoid any mistakes, I copied the exact permissions listed in the guide.
Here is an anonymized example of the API rules I configured (domain name masked):
POST /domain/zone/xxxxxx.fr/record
PUT /domain/zone/xxxxxx.fr/record/*
DELETE /domain/zone/xxxxxx.fr/record/*
GET /domain/zone/xxxxxx.fr/record/*
POST /domain/zone/xxxxxx.fr/refresh
However, when I enter the API credentials into Cloudron, I always get this error:
Access denied: OVH DNS error 403 — This call has not been granted
Does anyone know what might be causing this?
Thanks in advance for your help!
Hi and thank you!
In stress, I read half...
It works well through the cloudron web terminal.
Thank you for your quick responses!
Upon analysis, the issue stemmed from the Tegel 1.3.0 library used by the OpenVPN application: it was adding a space at the end of the OIDC scope:
scope=openid profile email[espace]
I created a patched Docker image for the OpenVPN 2.13.0 application by modifying the scope generation to use .trim(), thereby removing that space.
After redeploying the application with this image, the scope is generated correctly:
scope=openid profile email
OIDC authentication and access to the OpenVPN interface are working again, without modifying existing VPN configurations.