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

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

help-circle






  • 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.


  • I’ve had some luck with portable drives by removing the drive from enclosure and attaching it directly to sata-bus instead of USB

    I did try removing it from the enclosure in hopes to hook it to a USB3.0 to IDE/SATA which also includes legacy stuff. However this drive (HD Passport) has the micro-b soldered onto the drive board. I’ve tried several different micro-b to whatever connections, but no joy. The drive won’t initialize and reports a fatal hardware error when I try. When initially plugged in, you can physically feel the platter spin momentarily, and the power light comes on. But the platter will stop spinning and the power light will start blinking on and off. This drive has been beat up, dropped, etc, in a camera gear bag. I’m actually surprised it hasn’t failed before now.


  • My notes are jokey, full of profanity, sarcasm, and self deprecating humor

    I meant tedious, as in, it takes some effort to pause, write the shit down, and then proceed on. I can only speak for myself, but when I’m in the zone doing something, excitement can overshadow note taking. So, I have to make myself document line by line. But, yeah I have entries like ‘Before proceeding, make sure you do _____ , dumbass!’ LOL



  • Gamefaqs tutorial for a SNES game

    Well, I can’t speak to Gamefaqs or SNES as I am incapable of gaming. However, even what I would consider reputable tutorials such as ones you find on HowToForge, sometimes don’t quite turn out as expected. There is always some config or app that the tutorial needed, but was left out by the person writing the tutorial. Or the writer of the tut, had something pre-configed or preinstalled, so it wasn’t mentioned, even when following the tutorial line by line. It’s inevitable. For this reason, I maintain a small test VPS where I can run amuck and if I fuck something up, no problem, wipe/reinstall. So, if you’re going to say don’t trust AI, then you have to also be skeptical of all tuts. I mean, that’s where the AI scrapers got the info in the first place. I’m not saying AI is 100% tho I anticipate one day it will be, or at least very damn close. There are things AI gets right. It seems very capable of writing compose files well. Just my 2p




  • OP, I am sorry that I cannot offer any immediate solution to your issue. However, if I may, pass along a bit of advice I learned long ago, and it has nothing to do with AI. TAKE PROLIFIC NOTES!!! It is tedious, it is work, but it will save your ass in the long run. Write everything down. Don’t be lulled into the mindset that you will be able to remember each and every thing you’ve done to the server, especially when you’re breaking new ground in your selfhosting journey. 9 times out of 10, you won’t. Then when you are successful with your endeavors, go back, clean up your notes, and store them for future reference.