deleted by creator

Honestly I hate all these file sharing self hosting things. Looking at you nextcloud owncloud syncthing seafile etc. They all suck. All I want is NFS support in android, that’s my only pain point accessing my files from anywhere from my home network. I can already VPN/wireguard into my network from anywhere, but I can’t grab an ebook or mp3s off my NFS server from my phone or tablet, I have to have some other dumb infrastructure for it. Just (#@$^* put NFS in android already!!!

/endrant

Yeah setting it up the way you want is a pain, but I like it mainly for backing up photos from my phone automatically, as well as, syncing podcasts and music between devices since I moved away from Spotify and start using things like AntennaPod and Gramophone

I got 20TB in my server, might as well use it.

If you want to self host your contacts and calendars and have multiple users, I still don’t think there is anything better. I hope Open Cloud gets there eventually, but right now its only the beginning.

Agreed, nextcloud is a beast with lots of whistles, if you don’t need them you can have simpler solutions

This my approach here https://wiki.gardiol.org/doku.php?id=selfhost%3Afileserver

And I stated using AList which is a funny piece of software that has great potential. See here https://wiki.gardiol.org/doku.php?id=services%3Aalist

Use docker or podman compose https://hub.docker.com/_/nextcloud/

Nextcloud does not need a domain. Ip is fine.

I went from Seafile to Nextcloud with family file sharing as the primary usage. I’m using the AIO docker installation without issues.

This might not help, but I never experienced the issues you had.

(I moved away from Seafile due to - in my opinion - it dying a slow death with less and less support)

I also had bad luck with nextcloud, so recently I’ve set up SFTPgo and it works rather well and it’s only for files. You can either download and upload the files through the WebUI or you can mount them over the network to your OS.

https://github.com/drakkan/sftpgo

Nextcloud AIO has an option to skip domain check. the github README hasinstructions. And i love nextcloud because it integrates many features in one, file sharing, office collaboration, chat, rss reader, mailbox, photos, calendar, address-book, etc.

I have two instances running, one public and one completely local. And having a domain is just convenient but not necessary.

I just use SMB shares on my NAS. Why over think it?

So, use something else, like Seafile.

There’s a lot of stuff going on here, so let me break down your post for each issue:

1. You need to understand the difference between a docker run command, and detaching to run a container in the background. Just running it with ‘run’ keeps it in the foreground.

2. For the passphrase issue: https://github.com/nextcloud/all-in-one/discussions/1786

3. Lastly, if you’re not family with containers, and this is a single purpose machine, you’d be better off just running the bare project on the host. If there’s no need for containerization, just skip it.

I’ve never used the AIO image. I’ve heard it’s weird. This is my compose file for the community image:

volumes:
  db:

services:
  db:
    image: mariadb:10.6
    restart: always
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
    volumes:
      - db:/var/lib/mysql
    secrets:
      - mysql_root_password
      - mysql_nextcloud_password
    environment:
      - MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql_root_password
      - MYSQL_PASSWORD_FILE=/run/secrets/mysql_nextcloud_password
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud

  nextcloud:
    image: nextcloud
    restart: always
    ports:
      - 8080:80
    depends_on:
      - db
    links:
      - db
    volumes:
      - /var/www/html:/var/www/html
      - /srv/data:/srv/data
    secrets:
      - mysql_nextcloud_password
    environment:
      - MYSQL_PASSWORD_FILE=/run/secrets/mysql_nextcloud_password
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=db

secrets:
  mysql_root_password:
    file: ./secrets/mysql_root_password.txt
  mysql_nextcloud_password:
    file: ./secrets/mysql_nextcloud_password.txt

You can access it on port 8080 and perform the initial setup manually. For the database server address, use the db hostname. You’ll have to use a reverse proxy for HTTPS.

You could also try OpenCloud, which is a Go rewrite of ownCloud.

AIO

Yeah, that one is basically a take-it-or-leave-it approach. It’s a lot easier to customize when running your own Docker stack. It grew over the years and the team tries to sell it as an all-in-one SharePoint replacement (which it can be), but that also means it turned into an even more convoluted system.

I was looking into alternatives earlier this year, maybe one of them could be a solution for you:

• Owncloud infinite scale
• opencloud.eu (fork of ocis)
• syncthing (very good, depending on what exactly you’re looking for)
• Pydio Cells

There are others, or servers like WebDAV itself.

There are a number of ways to install nextcloud, and docker is only one of those.

Yes, NC isn’t ideal in many ways, but it shouldn’t be as painful as you’re describing to run it.