Replies: 90 comments 456 replies
-
|
hi , |
Beta Was this translation helpful? Give feedback.
-
|
log file is pretty long, gonna attach it below. i'm fairly new to this so I'm not 100% sure what to make of it. |
Beta Was this translation helpful? Give feedback.
-
|
I believe you have a typo in your Caddyfile. Can you add |
Beta Was this translation helpful? Give feedback.
-
|
You are correct, I had missed the |
Beta Was this translation helpful? Give feedback.
-
|
This should be sufficient |
Beta Was this translation helpful? Give feedback.
-
|
awesome, was able to close it down and restart it, Caddy is happier now, but I'm still having DNS issues. Going thru the docker resource about it, but not 100% how i will go about fixing it. edit: realizing the log is throwing a fit about |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
|
Yes, I've been running this setup for a few weeks now, and |
Beta Was this translation helpful? Give feedback.
-
|
Nice! |
Beta Was this translation helpful? Give feedback.
-
|
See #5460 |
Beta Was this translation helpful? Give feedback.
-
|
This is amazing @flll , I am trying to achieve the same since a month. But I am not using docker. Can you KINDLY make a script like the one for nextcloud with nginx as server, caddy as reverse proxy, tailscale and cloudflare as DNS. regards |
Beta Was this translation helpful? Give feedback.
-
|
Thankyou for the kind advice. I will go for it on Monday. Well I thought that I already am in lcx,doesn't it mean the same docker hardening? |
Beta Was this translation helpful? Give feedback.
-
|
Can you please enlighten the disadvantage? |
Beta Was this translation helpful? Give feedback.
-
|
with that AIO, can caddy be installed on different separate container/ VM . ( for example: caddy in a separate proxmox LCX container and nextcloud AIO in a separate Proxmox VM. but both VM and LXC are on same network but different subnets. Is this possible? |
Beta Was this translation helpful? Give feedback.
-
I would recommend using Kubernetes or Docker Swarm. |
Beta Was this translation helpful? Give feedback.
-
Docker-based deployment has very few disadvantages. |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
|
I used the nginx.conf from the projects readme (link in my original comment) What is I simply used the docker compose from the README (I had to comment and uncomment some lines) |
Beta Was this translation helpful? Give feedback.
-
|
apology, it's |
Beta Was this translation helpful? Give feedback.
-
|
Is your configuration something like this? |
Beta Was this translation helpful? Give feedback.
-
|
@flll what about my case? |
Beta Was this translation helpful? Give feedback.
-
|
@A4alli |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your work @flll . But no matter how many times I try the procedure, the hostname I give in the compose environment doesn't get created in the tailscale and rather a random ephemeral hostname is created after manually authenticating using the url in the log. My Internet and Network connection is fine. But I cannot log into the nextcloud instance even with the the randomly generated hostname in my tailnet. |
Beta Was this translation helpful? Give feedback.
-
- - TS_HOSTNAME = nextcloud
+ - TS_HOSTNAME=nextcloudThere should be no space between the key and value in the key-value pair. |
Beta Was this translation helpful? Give feedback.
-
|
That was it, I'm into nextcloud! Thank you so much my Japanese friend. The docker compose file as in the guide complained of map and kepair format and so I edited it but didn't know that space will cause issues. I see couple of errors in the caddy log of refusing connection to fonts.json, should I be concerned? Also two more questions,
|
Beta Was this translation helpful? Give feedback.
-
|
This error seems to be due to Caddy failing to connect to nextcloud-aio-apache.
Yes, using an OAuth key makes it ephemeral.
Example ACL configuration: {
"groups": {
"group:admin": ["[email protected]", "flll@github"],
"group:azuki": ["[email protected]"],
},
"acls": [
{
"action": "accept",
"src": ["group:admin"],
"dst": ["tag:nextcloud:*"],
},
]
}Note that "autogroup:admin" and "group:admin" are completely different groups. Please refer to Tailscale's autogroup documentation for more details. |
Beta Was this translation helpful? Give feedback.
-
Thank you as well. I was able to respond quickly because I've made the same mistake before, haha. |
Beta Was this translation helpful? Give feedback.
-
|
Non-ephemeral will make new nodes? Or ephemeral?? |
Beta Was this translation helpful? Give feedback.
-
|
Did anyone get this error? docker compose up tailscale-1 | boot: 2024/10/24 22:18:21 Running 'tailscale up' |
Beta Was this translation helpful? Give feedback.
-
Thank you for your help and for this amazing guide @flll . I was setting the host name to the same name as my server and I did not realized that it was making new machine server-1 in tailscale. Thank you again for your help!!! |
Beta Was this translation helpful? Give feedback.
-
|
This was also the root of my issue. Remember that the hostname to provide both in compose.yml and the Nextcloud admin console is the new, ephemeral hostname created by Tailnet, not the current hostname of your physical machine! |
Beta Was this translation helpful? Give feedback.
-
|
@MateuszFido what do you mean by new, ephemeral hostname created by Tailnet? Where can I find those? |
Beta Was this translation helpful? Give feedback.
-
|
I read everything in this guild but still can not access Nextcloud using my endpoint |
Beta Was this translation helpful? Give feedback.
-
|
The value of Supposing that your Tailnet name is |
Beta Was this translation helpful? Give feedback.
-
|
Nice guide! Thanks so much. or Note: same goes for the |
Beta Was this translation helpful? Give feedback.
-
|
Yes the |
Beta Was this translation helpful? Give feedback.
-
|
well I am using only via tailscale network. So I will not need any ports to forward. next I toggol on HTTPS in tailscale Admin counsel which give me lets encrypt https. right now Im stuck on provisioning screen. I cannot visit my nextclous AIO via tailscale domain. I am pasting the required data asked by @flll, when he will analyze about what is wrong. |
Beta Was this translation helpful? Give feedback.
-
|
Even with tailscale, you need those port to make it accessible inside your tailscale network |
Beta Was this translation helpful? Give feedback.
-
How to open up these ports in tailscale, whether it has to be done on the newly created nextcloud node or the host/server node in tailscale n/w. |
Beta Was this translation helpful? Give feedback.
-
|
I am running the whole system without any port forwarding or opening. Only in the docker compose there are the port mappings, to make the container accessible. The AIO master Container is only accessible over the ipadress from the Host running the Master container. But the rest of nextcloud does not need any port changing and is only accessible over your Domain you give into the environment variables. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, one question: Should I "sudo dnf install tailscale" on my host, then follow all this docker compose things? because how would I declare ACL dst 'nextcloud.your-tailnet.ts.net'? Or do I add my device manually in tailscale admin? I might be very less informed about ACL and tags, but I am trying to learn and doing all this to use nextcloud-aio is tiring, but I am trying my best. Thanks! PS: I was using this |
Beta Was this translation helpful? Give feedback.
-
|
Hey @flll What I did:
I am sure I misunderstood a lot of things, looking for pointers, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
New Setup:
|
Beta Was this translation helpful? Give feedback.
-
Please check the following conditions:
If it's not working even though the order is correct, execute the following commands: These commands will delete existing docker containers and networks.
Please configure ACL according to your environment. |
Beta Was this translation helpful? Give feedback.
-
|
@flll Brother, I finally did it. Nextcloud-AIO worked!!! What I did?
Thanks a lot! |
Beta Was this translation helpful? Give feedback.
-
|
@blazing-ph0enix Crossing your fingers is indeed an essential step in solving technical problems! 😄 It's wonderful that you're planning to share what you've learned with others. A guide for beginners will be incredibly helpful for many people. I'm looking forward to your future experiments. If you make any new discoveries, please do share them. Your experiences will be a valuable source of information for the community. Keep up the great work. And remember, if you ever run into any issues, don't hesitate to ask for help. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the guide, it's great but I cannot make it work for myself. My compose.yaml: My ACL: Caddy seems to recognize the domain name correctly, i.e. it resolves $NC_DOMAIN correctly. Tailscale logs: Tried opening 443 (TCP and UDP), 80, 8080 (out of desperation) in firewall and even disabling the firewall completely, none of it helped Seems that no matter what I do, in the nextcloud container I see: Pinging the domain name within tailscale works without problems |
Beta Was this translation helpful? Give feedback.
-
|
@MateuszFido
If you need to redo it, execute the following commands: These commands will delete existing docker containers and networks. |
Beta Was this translation helpful? Give feedback.
-
|
Yep, did those many times, my friend Finally got it today: the same issue as @Kendellb, the hostname to configure is the new, ephemeral hostname generated by Tailscale, not the current hostname of the physical machine hosting Nextcloud in tailnet. Initially, I thought your machine was just named "nextcloud" in your tailnet before running all the containers. It's worth remembering that setting the hostname provided to Nextcloud in the admin console cannot be undone - so just removing the containers, and even doing This was totally unclear to me from the guide, maybe it could be mentioned? Anyway, thanks a lot, it's a great setup nonetheless 👍 |
Beta Was this translation helpful? Give feedback.
-
|
I'm still having this issue. I'm using the ephemeral hostname but still having issues |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Right now, Unhealthy, because I haven't deleted old machines from admin console |
Beta Was this translation helpful? Give feedback.
-
Can't use my pc right now. Will try tomorrow. |
Beta Was this translation helpful? Give feedback.
-
|
Any update |
Beta Was this translation helpful? Give feedback.
-
Yes, I will make a new comment for my specific case, I will add all the logs in it |
Beta Was this translation helpful? Give feedback.
-
|
@flll if you please jump in to here to see the issues, KINDLY |
Beta Was this translation helpful? Give feedback.
-
|
Finally access the domain. |
Beta Was this translation helpful? Give feedback.
-
The funnel feature will expose your service to the public internet.
This error message indicates that debug information is currently hidden. While it's recommended to keep error details concealed in production environments for security purposes, you can temporarily enable detailed error display when troubleshooting is necessary. Once you've resolved the issue, it's advisable to return to the default secure configuration where error details are hidden from end users.
Please remove all containers and networks, then redeploy.
If you're unsure how to use it or don't plan to use it, I recommend not using it.
If Nextcloud is working, WebDAV should also be available by default.
Security settings are already included in nextcloud-aio-apache,
Are you trying to use both cloudflared and tailscaled tunnels? |
Beta Was this translation helpful? Give feedback.
-
|
Amazing. My nextcloud is functioning well by default. I mean from starting. I think I have no need to remove and redeploy. But of course security and setup warnings will stay the same as in the pastebin. (Or should it remove and redeploy and will get rid of the warnings) Point 6. You have pasted a diagram. A bit confusion, if you may please help me with it. I want to use cloudflare as DNS not a reverse proxy or tunnel. I have caddy-dns-cloudflare-module. |
Beta Was this translation helpful? Give feedback.
-
|
@flll @szaimen https://help.nextcloud.com/t/security-and-setup-warnings-nextcloud-aio-30-0-1/208752/2 |
Beta Was this translation helpful? Give feedback.
-
|
moreover @flll the notify-push failed in here according to your guide |
Beta Was this translation helpful? Give feedback.
-
THIS IS CREATING A TONS OF CLONE MACHINE IN MY TAILSCALE |
Beta Was this translation helpful? Give feedback.
-
|
Hey, So I have tried a lot of things, now my experience is like this:
Apache logs: Nextcloud logs: Redis: Database: Notify Push: Nextcloud Mastercontainer Logs: My ACL of Tailscale: |
Beta Was this translation helpful? Give feedback.
-
|
Your tailscale is not connected as per above logs |
Beta Was this translation helpful? Give feedback.
-
|
For me this guide work fine. Only problem is apache container showing unhealthy. But working |
Beta Was this translation helpful? Give feedback.
-
|
I apologize for the delayed response. cURL error 6: Could not resolve host: server.rohu-nessie.ts.netThis error suggests that the nextcloud-aio network is constantly being created, and Tailscale might not be properly connecting to the network Here are the steps to resolve this:
docker compose down
# Stop containers containing "nextcloud" in their name
docker stop $(docker ps -a | grep nextcloud | awk '{print $1}')
# Remove containers containing "nextcloud" in their name
docker rm $(docker ps -a | grep nextcloud | awk '{print $1}')
I didn't find any issues with the ACL settings. |
Beta Was this translation helpful? Give feedback.
-
Please disable the ephemeral setting.
It's recommended to keep the default state configuration.
This is likely a temporary issue.
Often this is due to insufficient permissions on the client-side Tailscale. |
Beta Was this translation helpful? Give feedback.
-
Thankyou 😍 |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone tried to deploy using the portainer stack? Caddy log: I have double-checked my NC_DOMAIN variable. compose.yml: services:
nextcloud-aio-mastercontainer:
image: nextcloud/all-in-one:latest
init: true
restart: always
container_name: nextcloud-aio-mastercontainer # This line cannot be changed.
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config
- /var/run/docker.sock:/var/run/docker.sock:ro
networks:
- nextcloud-aio
ports:
- 0.0.0.0:8080:8080
environment:
APACHE_PORT: 11000
APACHE_IP_BINDING: 127.0.0.1
SKIP_DOMAIN_VALIDATION: true
caddy:
image: caddy:alpine
restart: unless-stopped
container_name: caddy
environment:
NC_DOMAIN: nextcloud.[redacted].ts.net # Change this to your domain ending with .ts.net in the format {$TS_HOSTNAME}.{tailnetdomain}
volumes:
- type: bind
source: /home/surya/Caddyfile
target: /etc/caddy/Caddyfile
- type: volume
source: caddy_certs
target: /certs
- type: volume
source: caddy_data
target: /data
- type: volume
source: caddy_config
target: /config
- type: volume
source: tailscale_sock
target: /var/run/tailscale/ # Mount the volume for /var/run/tailscale/tailscale.sock
read_only: true
network_mode: service:tailscale
tailscale:
image: tailscale/tailscale:latest
container_name: tailscale
environment:
TS_HOSTNAME: nextcloud # Enter the hostname for your tailnet
TS_AUTH_KEY: tskey-client-kYthXvJbHD21CNTRL-[redacted] # OAuth client key recommended
TS_EXTRA_ARGS: --advertise-tags=tag:nextcloud # Tags are required when using OAuth client
init: true
restart: unless-stopped
volumes:
- /dev/net/tun:/dev/net/tun
- type: volume
source: tailscale
target: /var/lib/tailscale
- type: volume
source: tailscale_sock
target: /tmp # Mounting the entire /tmp folder to access tailscale.sock
cap_add:
- NET_ADMIN
- NET_RAW
networks:
- nextcloud-aio
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer # This line cannot be changed.
caddy_certs:
name: caddy_certs
caddy_data:
name: caddy_data
caddy_config:
name: caddy_config
tailscale:
name: tailscale
tailscale_sock:
name: tailscale_sock
networks:
nextcloud-aio:
name: nextcloud-aio
driver: bridge
enable_ipv6: false
driver_opts:
com.docker.network.driver.mtu: "9001" # Jumbo Frame
com.docker.network.bridge.host_binding_ipv4: "127.0.0.1" # Harden aioTailscale ACL: "groups": {
"group:admin": ["js-surya@github"],
"group:users": ["[email protected]", "[email protected]"],
},
"tagOwners": {
"tag:nextcloud": ["group:admin"],
},
"acls": [
// Allow general unrestricted access (you can comment this out if needed).
{"action": "accept", "src": ["*"], "dst": ["*:*"]},
// Allow users in "group:users" to access any devices tagged with "nextcloud".
{"action": "accept", "src": ["group:users"], "dst": ["tag:nextcloud:*"]},I'm not an IT expert, and I'm relatively new to this. My IP is behind CGNAT, and I want to access my Nextcloud server outside my local network using Tailscale. I'm eager to learn, so any suggestions or help would be appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
NC_DOMAIN=nextcloud.talscale.ts.net Remember there is = and than no space |
Beta Was this translation helpful? Give feedback.
-
TS_HOSTNAME=nextcloud # Hostname in Tailnet
NC_DOMAIN=nextcloud.mydomain.ts.net # Format: {$TS_HOSTNAME}.{$tailnetdomain}.ts.net
TS_AUTH_KEY=tskey-client-kYthXvJbHD21CNTRL-mykey # OAuth client key recommended
TS_EXTRA_ARGS=--advertise-tags=tag:nextcloud # For OAuth client key usageHere is my .env config |
Beta Was this translation helpful? Give feedback.
-
|
check my config files above that work |
Beta Was this translation helpful? Give feedback.
-
|
Apache is always unhealthy docker exec -it nextcloud-aio-apache bash -x /healthcheck.sh
|
Beta Was this translation helpful? Give feedback.
-
|
Same here |
Beta Was this translation helpful? Give feedback.
-
|
check my last comment below for solution with serve.json |
Beta Was this translation helpful? Give feedback.
-
|
Checked it. Is there a way to check if a port is open to public? Will try and report. |
Beta Was this translation helpful? Give feedback.
-
|
what about your security and setup warnings? |
Beta Was this translation helpful? Give feedback.
-
|
@flll Wanted to mention that I was able to get this working without needing caddy at all. I think it simplifies things a bit. Tailscale can natively proxy Note this employs tailscale serve (as opposed to tailscale funnel) so will only expose the service to your tailnet, not publicly. You could set a funnel flag to true in the json config below to expose it publicly, though some security and performance caveats would apply if you did.
|
Beta Was this translation helpful? Give feedback.
-
I am utilizing the native proxy method provided by @patrick-theprogrammer, as detailed in 1 and 2, without employing Caddy as a sidecar. Please take a look at his compose file and serve-config.json there, you can find the serve config variable and volume. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @patrick-theprogrammer! This feels like a much better approach for me personally ( A couple of things to note in case others run into similar issues:
nextcloud-aio:
image: nextcloud/all-in-one:latest
container_name: nextcloud-aio-mastercontainer # app requirement
depends_on:
- nextcloud-tailscale
ports:
- 8080:8080 <----------------------------
|
Beta Was this translation helpful? Give feedback.
-
|
No need of exposing port 8080. You call [tailscal].ts.net:8443 |
Beta Was this translation helpful? Give feedback.
-
|
Hey all, i got the setup working with Tailscale server, thx for the info and guide. |
Beta Was this translation helpful? Give feedback.
-
|
use funnel but it will expose to internet |
Beta Was this translation helpful? Give feedback.
-
|
hi guys, I seem success for most part, all container runs fine, without error or unheathy, I checked the node nextcloud also shows green on tailscale admin console. I can access the 8080 port and setup the install, but afterwards I cannot open the main page: It seems DNS error but I don‘t know how to fix, I already enable the |
Beta Was this translation helpful? Give feedback.
-
|
Oh I fixed by enable the https certificates and wait a while it would get the cert for my domain, but now it opens very very slow, any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
actually I am confused, I install the nextcloud-aio just in docker-desktop in windows, also I pinged the nextcloud node, 0 loss with almost 0 delay... |
Beta Was this translation helpful? Give feedback.
-
|
#5439 works for me, speed is normal |
Beta Was this translation helpful? Give feedback.
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
I have gotten Nextcloud up and running on my test computer. Now I'm trying to get it running on another computer. My set up goes smoothly until I try to access localhost:8080 to provision Nextcloud. I get a message saying "Bad Request. Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please. Apache/2.4.62 (Unix) Server at localhost Port 8080" This worked fine on my other computer. Any ideas of what is causing this? I tried checking the firewall, but I don't see any problems there. |
Beta Was this translation helpful? Give feedback.
-
|
I succeded to install nextcloud on docker (on windows) using tailscale |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for the write up! What I did:
In tailscale admin:
My issues:
The unhealthy container is quite annoying as it happened on my first Manjaro device, I grabbed another old laptop and which ran Ubuntu, I tried again and also got the unhealthy container. I completely reset the manjaro device and still get unhealthy containers. I also tried (as described above) to move from the v1.82.0 to the /latest and /stable branches in the dockerfile, but to no avail. Could someone tell me If I'm missing something? I really feel it shouldn't be this hard ':-| |
Beta Was this translation helpful? Give feedback.
-
|
Oh I made a few errors down the line too, which I eventually figured out, being:
|
Beta Was this translation helpful? Give feedback.
-
|
Following up, I
I'm at a loss. I literally did nothing more on this system than the bare minimum to be able to run the script, and it fails on the exact same thing every time. Anyone got a clue? |
Beta Was this translation helpful? Give feedback.
-
|
Finally got it to work, what did the trick
but the biggest thing: Ignore the failed to start tailscale message. If you just ignore it and go on with the next command in the tutorial it works somehow... |
Beta Was this translation helpful? Give feedback.
-
|
Does it mean that in future I can't change setup and use Nextcloud AIO with public domain? |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, I don't know what I'm doing wrong. I am able to do everything properly until the settings of AIO.
I have noticed that after doing everything my tailscale is adding a new machine nextcloud-1.tail####.ts.net I have set nextcloud.tail####.ts.net as my domain in the AIO settings Here's my compose.yml
Here's my Caddyfile
|
Beta Was this translation helpful? Give feedback.
-
|
I am at the same point as you. The containers seem to work just fine but I cannot reach my Nextcloud "This website cannot provide a secure connection. nextcloud.#####.ts.net has sent an invalid response." |
Beta Was this translation helpful? Give feedback.
-
|
Up and running on ubuntu 24.02 server Compose.ymlCaddy.DockerfileCaddyfileACL Settings in Tailnet
|
Beta Was this translation helpful? Give feedback.
-
|
How did you make it work. I tried mine with 2 different windows computer and a VM using ubuntu. I always get the issue connecting to my server after the initial setup with https://localhost:8080 |
Beta Was this translation helpful? Give feedback.
-
|
I have tried this several times from scratch on a windows machine with docker. I have used everything as recommended except I use a brand new auth key instead of oauth (I haven't figured out acl for tailscale). My containers are healthy. There're no problems I see in my logs. But if I try to access LocalHost:8080, or 27.0.0.1:8080, I receive the following error.
If instead I try nextcloud.[mytailscale].ts.net I get: ERR CONNECTION TIME OUT. Anyone have an idea of what I'm doing wrong? |
Beta Was this translation helpful? Give feedback.
-
|
Just a suggestion… maybe try https:// instead of http://…? Just a thought
I know how frustrating it can be to get a setup going.
…On Mon, Jun 9, 2025 at 9:01 AM Byte-sized1 ***@***.***> wrote:
I have tried this several times from scratch on a windows machine with
docker. I have used everything as recommended except I use a brand new auth
key instead of oauth (I haven't figured out acl for tailscale). My
containers are healthy. There're no problems I see in my logs. But if I try
to access LocalHost:8080, or 27.0.0.1:8080, I receive the following error.
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
Apache/2.4.62 (Unix) Server at localhost Port 8080
If instead I try nextcloud.[mytailscale].ts.net I get: ERR CONNECTION
TIME OUT.
Anyone have an idea of what I'm doing wrong?
—
Reply to this email directly, view it on GitHub
<#5439 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZZHXVKNNKZ3IRTVXX7F7HD3CWVWHAVCNFSM6AAAAABQGBXP2KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNBRGE3DONY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
hi i got DNS_PROBE_POSSIBLE error when i tried this method, how do i fix it? |
Beta Was this translation helpful? Give feedback.
-
|
I am having difficulty getting Talk to work with this setup. Looking through the logs, curl can't resolve the tailnet domain. Has anyone else had this issue? |
Beta Was this translation helpful? Give feedback.
-
|
Figured this out. Due to a bug in tailscale's docker right now (tailscale/tailscale#14467), the NC_DOMAIN does not resolve for the server itself unless the container's host machine is also connected to tailscale. This means when the backend for talk tries to connect to the standalone-signaling endpoint, it fails with a DNS error since it uses the domain name |
Beta Was this translation helpful? Give feedback.
-
|
This worked for me, but since the latest nextcloud update, there seems to some communication problem: when I try to connect to nextcloud from my tailnet, caddy shows this log entry:
Somehow caddy is unable to reach the apache container. Can someone point me into the right direction on this? |
Beta Was this translation helpful? Give feedback.
-
|
Turns out I was stupid, had the mastercontainer in a wrong network, that's why caddy couldn't find the apache container. |
Beta Was this translation helpful? Give feedback.
-
|
How to modify this docker file to add other drives on system. Note: I dont want to use 'external storage' menu. I need the drive to show up in system under 'Disks' . It should show up under here.
|
Beta Was this translation helpful? Give feedback.
-
|
Awesome, thanks for the update!
…On Sun, Jun 29, 2025 at 9:22 AM Mitch ***@***.***> wrote:
Figured this out. Due to a bug in tailscale's docker right now (
tailscale/tailscale#14467
<tailscale/tailscale#14467>), the NC_DOMAIN
does not resolve for the server itself unless the container's host machine
is also connected to tailscale. This means when the backend for talk tries
to connect to the standalone-signaling endpoint, it fails with a DNS error
since it uses the domain name
—
Reply to this email directly, view it on GitHub
<#5439 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZZHXVJPXGAGYGOUJN4NTCT3GAHDZAVCNFSM6AAAAABQGBXP2KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRRGAZTOMA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Disclaimer: It might be possible that the config below is not working 100% correctly, yet. Improvements to it are very welcome!
This setup integrates Nextcloud All-in-One (AIO) with Tailscale, using Caddy as a reverse proxy.
Since Tailscale currently only allows communication with localhost(127.0.0.1), we use a sidecar with Caddy to communicate with AIO.
serve.jsonconfiguration (This document does not provide an example ofserve.json)1. Set Environment Variables
Set the following environment variables:
Note
We will not create a .env file, but instead write directly into the compose.yml file later.
If you do create a .env file, compose will automatically read it. In this case, set the key-value format in service[].environment[] of the compose.yml to keys only, allowing compose to pass variables to the service.
Ensure NC_DOMAIN is in the correct format.
When using OAuth client key, set tags in TS_EXTRA_ARGS and define them in ACL.
For more detailed information, please refer to:
https://tailscale.com/blog/docker-tailscale-guide
2. Configure Docker Compose File
Create a compose.yml file with the following content. Replace environment variables as appropriate.
compose.yml
Important
Make sure to replace
NC_DOMAIN,TS_HOSTNAME,TS_AUTH_KEY, andTS_EXTRA_ARGSwith your actual values before running the docker compose file.3. Create Caddyfile and Caddy.Dockerfile
Create a Caddyfile in the current directory with the following content:
Caddyfile
{ layer4 { 127.0.0.1:3478 { route { proxy { upstream nextcloud-aio-talk:3478 } } } 127.0.0.1:3479 { route { proxy { upstream nextcloud-aio-talk:3479 } } } } } https://{$NC_DOMAIN} { reverse_proxy nextcloud-aio-apache:11000 { header_up X-Forwarded-Proto "https" header_up Host {host} } } http://{$NC_DOMAIN} { reverse_proxy nextcloud-aio-apache:11000 { header_up X-Forwarded-Proto "http" header_up Host {host} } }Note
Do not manually replace the
{$NC_DOMAIN}variable. It will be automatically populated with the value set in your environment variables.Create Caddy.Dockerfile
4. Set Up Nextcloud AIO
docker compose up --build --pull always --waitanddocker compose logs --followhttps://$NC_DOMAIN/(e.g., https://nextcloud.your-tailnet.ts.net/)If it doesn't work
Please try the following:
Docker Reset Commands
If things don't work, use the following commands to reset
Caution
Only use this if nothing else works.
CLICK!
After force stopping, check that the Nextcloud entry is no longer visible in the Tailscale admin console
Thank you for your advice, frazar
Latest Updates
beta, so I also changed the command todocker compose up --pull always.service:tailscaleBeta Was this translation helpful? Give feedback.
All reactions