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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
P

pdrupp

@pdrupp
About
Posts
5
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Backup Errors
    P pdrupp

    I'm thinking about the possibility that the length of the encrypted filenames might be too much for Wasabi... I'll dig deeper...

    Support backups

  • Backup Errors
    P pdrupp

    Hey joseph, thx for your reply. No this error is when backing up using Cloudrons Backup Module to Wasabi S3. The Synology makes a complete VM Backup in the background, no errors there. I hadn't activated logging in S3, i will change that and run a new backup.

    Support backups

  • Backup Errors
    P pdrupp

    Hi, i have recently setup a 2nd Cloudron instance on Netcup that i only use as a mail server. Currently around 50 Mailboxes with a total of 180GB of data. I do hourly Backups to our on-prem Synology via Tailscale that work fine and fast. Usually between 1 and 5 minutes. Once per night i still want to make a direct backup from Cloudron to Wasabi S3. I already found out that rsync takes a lot of time, so i switched to tar for a few days, and that worked great, but still i would prefer rsync. There's pros and cons for both settings. So i switched back to rsync and the backups work, but during the upload i see a lot of 500 errors.

    Here's an example:

    Retrying (1) copy of 6sRz+6WKso8LhqISaUkfxZZhA02YwUGbjJPLNwP5YGg/viNdvgKqX2Z0h2Q8PWusD+r432QXN4DIGBmVbmWqqCQ/9EOUhxrSmnxrOk0C1mGNy73UPTrETurLwHZIMWcTaW4/WLjr6ukIaB+olQVkGmjQamtztBwQ0qCzvHqrSTsGUEJWr5EBiWSvHYqYxTOw-O7i/aBD30AGnxxwdei3sZYSXWzbyX2wX7ZCpUkgkj5czFDc/OL8uir0yWaEDftripDEB6aTiwnfGsOK+DCpt3UstR3LUPK4Lq3Vi6Y5W-I4dG6PXKSZaCtohB-DL-mGfDablPYtq-JDXCc3ke9wPI0otcFI. Error: InternalError: We encountered an internal error. Please retry the operation again later. 500
    

    What is this error, how can i fix it and how come the backup still finishes in a positive state?

    Support backups

  • Struggling to connect Okta
    P pdrupp

    Hello and thank you for your feedback.
    I put this idea on hold for the time being after learning that Okta has had several security breaches in the past. I am reconsidering which solution I want to use at all. Thanks anyway

    Support okta

  • Struggling to connect Okta
    P pdrupp

    Hello there, i am currently struggling with setting up Okta external directory.
    After some trial and error, i got Cloudron to accept my settings, then when i hit sync, i see under the progress bar the one user i currently have in okta and the task finishes without error. but the user is not created. I guess i have an issue with uid, username or something the like. kinda lost. could anybody help me out here? thx

    Support okta
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search