I have NextCloud installed via Ubuntu Snap. But I want to take the docker route instead. Every “how to” only shows how to set it up with reverse proxy configuration. I need to be able to do this without it. Any help?

Update: Figured it out! Made a domain name in Cloudflare Tunnels that point to https://localhost:11000. Then on NextCloud aio domain verification, I put the domain name that I made.

@techgearwhips@lemmy.world
creator
link
fedilink
English
11Y

I tried the all in one a few times. I run it from localhost:8080 and the NextCloud setup keeps asking me to put in a domain name. I just want to be able to run from localhost with no domain needed.

Strit
link
fedilink
English
31Y

You should be able to just run the docker container and expose port 8080, then visit http://localhost:8080 to complete the setup. You won’t have SSL or anything though. If it still asks for domain name, maybe you can put in localhost.local ?

@techgearwhips@lemmy.world
creator
link
fedilink
English
11Y

Does not work. This comes up:

“DNS config is not set for this domain or the domain is not a valid domain! (It was found to be set to ‘’)”

@techgearwhips@lemmy.world
creator
link
fedilink
English
01Y

Honestly don’t need SSL. And I will try that localhost.local when I get back to my server. Thanks.

@deleted@lemmy.world
link
fedilink
English
11Y

There’s environment entry to disable domain check but it’ll not run as you must configure reverse proxy at least to get the certificate. I spent 3 hours yesterday until I gave up and removed it.

It’s kinda misleading stating it can run locally with no reverse proxy without mentioning it’s necessary to complete the installation process.

Source: nextcloud local installation guide.

I don’t think localhost.local would resolve from inside nextcloud docker container. If that’s the case, just try localhost instead.

@techgearwhips@lemmy.world
creator
link
fedilink
English
1
edit-2
1Y

Localhost definitely won’t work because I will get the error “Domain must contain at least one dot!”.

@Decronym@lemmy.decronym.xyz
bot account
link
fedilink
English
1
edit-2
1Y

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
HTTP Hypertext Transfer Protocol, the Web
SSL Secure Sockets Layer, for transparent encryption
nginx Popular HTTP server

3 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.

[Thread #112 for this sub, first seen 6th Sep 2023, 14:25] [FAQ] [Full list] [Contact] [Source code]

@rambos@lemm.ee
link
fedilink
English
3
edit-2
1Y

Have you tried LSIO image?

This is my docker-compose:

`version: “3” services:   nextcloud:     image: lscr.io/linuxserver/nextcloud:latest     container_name: nextcloud     environment:       - PUID=1000       - PGID=100       - TZ=Europe/Zagreb

    volumes:       - /home/config/nextcloud:/config       - /srv/dev-disk-by-uuid-22495ee1-7931-4383-8ba5-7e8fb0f463f9/data500/data/nextcloud:/data     ports:       - 4443:443     restart: unless-stopped`

I can open it at https://192.168.0.40:4443

I am using nginx reverse proxy, but Im quite sure its working without one out of the box

@rambos@lemm.ee
link
fedilink
English
11Y

My code block is messed up somehow, but docker-compose is just modified one from the link, but with my volume paths, puid, pgid, TZ and port

@deleted@lemmy.world
link
fedilink
English
11Y

I found it while toying with CasaOS. it did work flowlessly without hassle.

https://hub.docker.com/r/linuxserver/nextcloud/

version: “2.1” services: nextcloud: image: lscr.io/linuxserver/nextcloud:latest container_name: nextcloud environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC volumes: - /path/to/appdata:/config - /path/to/data:/data ports: - 443:443 restart: unless-stopped

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 125 users / day
  • 420 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog