Incessant tinkerer since the 70’s. Staunch privacy advocate. SelfHoster. Musician of mediocre talent. https://soundcloud.com/hood-poet-608190196

  • 25 Posts
  • 739 Comments
Joined 9 months ago
cake
Cake day: March 24th, 2025

help-circle



  • irmadlad@lemmy.worldtoSelfhosted@lemmy.worldNAS decision paralysis
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    11 hours ago

    Huh… I thought Synology had a cap of 143 characters. Are you writing a book? LOL

    So if I want that backup to work, it appears I have to rename hundreds of files on that PC

    You could zip or tar the offending files. Inconvenient but would work. You could use VeraCrypt or Cryptomator containers which would give you 255 character cap. Using a VeraCrypt or Cryptomator container will let you store files with longer names inside the encrypted volume, but it won’t change the 143‑character limit for the container filename itself on the Synology NAS.


  • irmadlad@lemmy.worldtoSelfhosted@lemmy.worldNAS decision paralysis
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    12 hours ago

    I was specifically wondering if I could in fact just chuck them in as-is and it would be able to access the drives? Because like, they’re separate drives, right? How would that work in a non-RAID setup when accessing from another computer? Would they show up as separate drives? Is it at all possible?

    I have a shelf of NetGear ReadyNas-4 bay enclosures. They are old as the hills ReadyNas 214 with OS 6.10.3. The first 2 of them are set up as JBOD (Just a Bunch Of Drives) 8 bays x 10 tb drives . They have no RAID setups on them. They all show up as separate drives. Now, you may need to set up permissions to access the drives, but they all act independently of each other. However, in that setup, if a drive fails, well you’re SOL. Some caveats would be that the drives to be inserted into the JBOD NAS setup need to be formatted in a compatible file system such as EXT4 or NTFS

    The other 2 ReadyNas-4 bay enclosures are set up as RAID 5. So using RAID 5, you have ~30 tb usable space and 1 10tb drive for redundancy per each ReadyNas unit.




  • Google Cloud Armor, AWS Shield, Fastly, Akamai, Incapsula, Freenom World, DDoS-GUARD, Netlify, all offer some level of DDoS and plans vary widely. Cloudflare’s Tunnels/Zero Trust free tier is quite generous. I realize some selfhosters have an aversion to Cloudflare, but Cloudflare is very good at what they do. There are VPS hosts that do offer DDoS protection like DigitalOcean, Vultr, Linode, A2 Hosting, Hostinger, OVH, however, it’s usually just basic DDoS protection. Maybe check with your host to see what they offer.

    Most edge DDoS protection of any merit is going to be the big guys. You could lock down your VPS to only you and your handful of friends, but unfortunately, in the event of a DDoS attack, your server will be bearing the brunt of the attack. Is your VPS server of a nature that would elicit repeated DDoS attacks? I’ll have to say, anecdotally, that I’ve never experienced one, but that is no guarantee that you wouldn’t either.








  • Ok, so I am not the NC AIO expert. However, checking some similar issues online I’ve come across this:

    • v11.11: Compatible Successfully installed using Docker on Synology DSM. Necessary adjustments may be needed for port conflicts due to Synology services.

    • Latest: Potential issues Users have reported issues with the latest image (20251128_084214) causing connection problems with the Docker socket on Synology. It may be advisable to roll back to a stable version if issues arise.

    Also, on https://github.com/nextcloud/all-in-one/issues/7223 dated 11-29-25:

    • If you run an outdated or too new docker version, you might run into problems with the by AIO internally used docker api version. To fix this, you can specify the api version manually. You can do so by adding --env DOCKER_API_VERSION=1.44 to the docker run command of the mastercontainer (but before the last line ghcr.io/nextcloud-releases/all-in-one:latest! If it was started already, you will need to stop the mastercontainer, remove it (no data will be lost) and recreate it using the docker run command that you initially used). This variable excepts a string based on the pattern [0-9].[0-9]+, so e.g. 1.44. ⚠️ However please note that only the default api version (unset this variable) is supported and tested by the maintainers of Nextcloud AIO. So use this on your own risk and things might break without warning. https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-adjust-the-internally-used-docker-api-version

    And a confirmation:

    • Yeah I figured it out as it seems Synology’s DSM uses an older docker. The docker version says its API is on version 1.43. So I’ve fixed it by setting: DOCKER_API_VERSION: 1.43

    I’m not entirely sure this will fix you, but it seems to match the ‘containers stuck in startup’. Good luck!

    ETA TO CLARIFY: You are using the latest image of NCAIO, with Docker api 1.43, which seems to cause havoc on Synology.





  • Are they worth salvaging?

    I think they are worth salvaging, if but for a little while until at such time you wish to upgrade to something else.

    but I don’t know much about Linux

    Here’s a good opportunity to buff up your skill set. With two units, you can get into simple networking one device to another. Things like that. I see Proxmox has been mentioned and that might be an avenue to explore. Generally, I don’t toss a piece of equipment unless it has zero possibilities for use. I can always find something to do with old equipment even if it’s just testing out something new I’ve learned recently, without screwing up my main stack.


  • Oh please. Stop licking corporate AI boot and drinking the kool-aid.

    Why must you think that because I use AI that I have somehow ‘drank the kool-aid’ and am ‘licking corporate boots’? Why is that always the go to with you guys? It’s like blood in the water. Look, I am willing to accept that you vociferously dislike/hate/abhor AI. You have a definite opinion about AI. Got it loud and clear. Much like I have a definite opinion about the ‘arr stack’ which I would say that 75% of selfhosters run. You don’t hear me out here beating my tin pan every time someone mentions the arr stack tho. Why? Because I figure you are an autonomous adult capable of making your own choices, and I leave it at that. No long diatribes about copyright or theft. None of that. I let you be you, and make your own decisions…without all the browbeating.

    As I have stated before, I too am fully aware, and fully autonomous. OP used AI, didn’t write down anything, lots of mistakes were made. It’s not like none of us haven’t pulled some stupid boners in our self hosting journey either. You live and learn. It does zero good tho, to brow beat OP because they made some mistakes or used AI. In fact, I would say it would drive people to use AI because of the negative reactions in this very thread.

    You saying that these two things are as trustable as each other suggests you have quite a misanthropic edge to your personality and/or are going through a stage of cult-of-personality (or cult-of-brand).

    Your unsubstantiated and unqualified psychoanalysis is way off. Maybe you’re using the wrong AI.