Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • SFTP to backup

    Solved Support
    8
    1 Votes
    8 Posts
    849 Views
    scookeS

    @Neluser It's always appreciated when solutions are posted because eventually someone has a similar or same question. Thank you!

  • Connecting Synology NAS to Cloudron LDAP fails

    Unsolved Support
    2
    0 Votes
    2 Posts
    507 Views
    nebulonN

    Without being able to debug this further, for a start, the filter seems wrong. The Cloudron provided user records would have the following objectClass attribute:

    objectclass: [ 'user', 'inetorgperson', 'person' ]

    so use one of those three entries there. Also Cloudron has no attribute uidNumber maybe using entryuuid works there though.

  • 0 Votes
    7 Posts
    1k Views
    ajtatumA

    @girish & @mehdi - thanks for your advice! It gave me the idea to Tailscale. I installed it on the Cloudron server and was able to successfully mount a shared folder from my Synology using cifs. However, even though the data persists between reboots, I don't see the data on the Synology, even when I'm logged in as the root user. I'm not quite the linux expert, but I noticed that when I changed Nextcloud's appdata folder to point to the mount, it created it as a "root" user. On the Synology, I created a Cloudron user that has the necessary permissions and I mounted the shared folder with the Cloudron user, password, and domain. So, I'm thinking this has something to do with user IDs not matching up or something like that.

    I'm nervous about moving forward since I can't actually see the data on my Synology. Would you or anyone else have any advice?

    By the way, this is how I mounted it:
    sudo mount -t cifs -o credentials=/etc/nas-credentials,vers=3.0 //nas/Cloudron /mnt/nas

    In fstab, the command is:
    //nas/Cloudron cifs -o credentials=/etc/nas-credentials,vers=3.0,_netdev,auto 0 0

    Thanks for all your help!

  • 0 Votes
    17 Posts
    6k Views
    J

    @jayonrails SSH and SAMBA access haven’t been enabled yet, therefore it didn’t worked. After enabling it, everything works perfectly.