January 15, 20251 yr Recently updated to 7.0 stable, and starting to try to implement the new Tailscale features. I've been using the plugin for months now, but the Serve feature and TLS Certs that come with those will come very handy for certain services that require HTTPS but I don't want to be publicly available. All of the linuxserver.io containers worked perfectly on initial start-up, but some of the others I have are not running as successfully. Notably, trying to run Actual Server comes up with these error logs: Executing Unraid Docker Hook for Tailscale Detecting Package Manager... Detected Advanced Package Tool! Installing packages... Please wait... Packages installed! Tailscale not found, downloading... Please wait... ERROR: Can't get Tailscale JSON ERROR: Unraid Docker Hook script throw an error! Starting container without Tailscale! Starting container... After this, the container starts normally and functions just fine other than no Tailscale connectivity. No google-fu has come up with anything relating to this error. Anyone have tips for how this could be resolved?
January 15, 20251 yr Solution 2 hours ago, ndauphin583 said: Anyone have tips for how this could be resolved? This will be fixed in the next version from Unraid. Thanks for the report! As a workaround you can currently use the Tailscale sidecar method or TSDProxy if you need the container in your Tailnet or you can share the Container network with a container where the Unraid Tailscale integration is working.
January 15, 20251 yr Author Sweet, thanks for the update! Are we expecting that update to come relatively soon, or will it be long enough that I should go ahead and use one of these alternatives?
January 21, 20251 yr I am having the same issue with some containers. Did you use one of the work arounds?
January 22, 20251 yr 8 hours ago, Jsdphilly said: with some containers Can you please be a bit more specific with which containers so that I can take a look at it?
January 28, 20251 yr I, myself, am encountering this same error with FreePBX. I get errors that Ntfy can't connect to Tailscale, and CaddyV2 doesn't even seem to be trying. Having hit the roadblock, I haven't tried any others. Edited January 28, 20251 yr by bradbrownjr
January 28, 20251 yr 12 minutes ago, bradbrownjr said: Having hit the roadblock, I haven't tried any others. Please always include the repository from the containers so that it easier for me to look into why and possible alternatives. EDIT: I just tried FreePBX and it seems to work just fine: I assume for Caddy v2 you are trying to run it with Tailscale Serve correct? If that is the case you have to disable port 443 in Caddy v2 since Tailscale Serve is using that port already, you can of course change that but I'm not sure if that's what you want if your goal is to route everything through Tailscale. For me it also starts fine, here is the log: Do you possibly have any Unifi network gear on your network with IDS/IPS enabled and is maybe a bit to strict since I already had such issues in another thread.
January 30, 20251 yr On 1/28/2025 at 3:49 PM, ich777 said: I assume for Caddy v2 you are trying to run it with Tailscale Serve correct? If that is the case you have to disable port 443 in Caddy v2 since Tailscale Serve is using that port already, you can of course change that but I'm not sure if that's what you want if your goal is to route everything through Tailscale. So it's not possible to have caddy with tailscale and use default ports like 80 and 443 like Alex show here ?
January 30, 20251 yr 12 minutes ago, AmbyDK said: So it's not possible to have caddy with tailscale and use default ports like 80 and 443 like Alex show here ? I don't think that that's the same as in the linked video because he doesn't use a Docker container for Caddy or am I wrong? I'll watch the full video later and report back. In the meantime could you please explain what you want to do? I assume you want to host multiple services through Caddy in your Tailnet correct? This should be however be possible but I have to look into that.
January 30, 20251 yr 26 minutes ago, ich777 said: I don't think that that's the same as in the linked video because he doesn't use a Docker container for Caddy or am I wrong? I'll watch the full video later and report back. In the meantime could you please explain what you want to do? I assume you want to host multiple services through Caddy in your Tailnet correct? This should be however be possible but I have to look into that. Sure. I basically want the same solution as Alex, but in Unraid, but I cannot get an answer from caddy when using 80 and 443. It works on 8443 and 8080. Using: ghcr.io/hotio/caddy:latest Changed parameters (Unraid is set to 1443, so no conflict there.) Tailscale Serve is set to (Tried leaving this blank also. No change): Everything else is default. { http_port 8080 https_port 8443 } (cloudflare) { tls { dns cloudflare KEY } } # HomePage home.domain.dk { reverse_proxy http://192.168.1.100:3050 import cloudflare }
January 30, 20251 yr 3 hours ago, AmbyDK said: Sure. I basically want the same solution as Alex, but in Unraid, but I cannot get an answer from caddy when using 80 and 443. It works on 8443 and 8080. Ah now I get it! Please look at the Caddyfile from Alex here, as you can see he doesn't have ports 8080 and 8443 in his Caddyfile because he all routes that through Tailscale but he uses Cloudflare for his public DNS records but keep in mind that these domains will not be accessible from the outside only if you share it out to someone that has Tailscale installed and you have shared your machines (and of course in your Tailnet it will work too). So to speak you could use your (purchased) domain name from everywhere in the world but only if you are connected to your Tailnet, this means your public FQDNs will be forwarded to your Tailnet. I hope you understand what I mean, this is a bit complicated to explain or I did a bad job at explaining.
January 30, 20251 yr 2 minutes ago, ich777 said: Ah now I get it! Please look at the Caddyfile from Alex here, as you can see he doesn't have ports 8080 and 8443 in his Caddyfile because he all routes that through Tailscale but he uses Cloudflare for his public DNS records but keep in mind that these domains will not be accessible from the outside only if you share it out to someone that has Tailscale installed and you have shared your machines (and of course in your Tailnet it will work too). So to speak you could use your (purchased) domain name from everywhere in the world but only if you are connected to your Tailnet, this means your public FQDNs will be forwarded to your Tailnet. I hope you understand what I mean, this is a bit complicated to explain or I did a bad job at explaining. yes I linked to the same video. However man issue is when I follow the caddyfile structure , I get no answer. in short: I suspect unraid , Tailscale & caddy together is the issue port-wise as Alex has no issue when using proxmox and Ubuntu.
January 30, 20251 yr 6 minutes ago, AmbyDK said: yes I linked to the same video. I know I just watched it because I'm not familiar with Caddy... 6 minutes ago, AmbyDK said: However man issue is when I follow the caddyfile structure , I get no answer. Did you set it up exactly the same as Alex? From my understanding this should work fine on Unraid too. It's really hard to test because I don't want to mess up my whole Tailnet nor my Cloudflare. I might can try it over the weekend if I can find some free domain names, but this should work totally fine on Unraid too as long as the Cloudlare token is correct and you set up the subdomains correctly so that they point to your Tailnet of course only as long as you are connecting from a machine with Tailscale enabled because it just forwards the traffic. You wont get any answer from Caddy directly anymore because you have no ports open, all just works then through Cloudflare DNS and of course through Tailscale.
January 30, 20251 yr 4 minutes ago, ich777 said: I know I just watched it because I'm not familiar with Caddy... Did you set it up exactly the same as Alex? From my understanding this should work fine on Unraid too. It's really hard to test because I don't want to mess up my whole Tailnet nor my Cloudflare. I might can try it over the weekend if I can find some free domain names, but this should work totally fine on Unraid too as long as the Cloudlare token is correct and you set up the subdomains correctly so that they point to your Tailnet of course only as long as you are connecting from a machine with Tailscale enabled because it just forwards the traffic. You wont get any answer from Caddy directly anymore because you have no ports open, all just works then through Cloudflare DNS and of course through Tailscale. I guess a test would be to spin up a ubuntu and to see if it answers correctly with 80 and 443.
January 30, 20251 yr 11 minutes ago, AmbyDK said: I guess a test would be to spin up a ubuntu and to see if it answers correctly with 80 and 443. It won‘t since the Caddyfile doesn‘t has these directives in place. Alex also didin‘t show that it answers on port 80 or 443.
January 30, 20251 yr 8 minutes ago, ich777 said: It won‘t since the Caddyfile doesn‘t has these directives in place. Alex also didin‘t show that it answers on port 80 or 443. I assumes as he is able to use the below url and the caddyfile, it answers correctly on port 80 in his example?
January 30, 20251 yr 26 minutes ago, AmbyDK said: I assumes as he is able to use the below url and the caddyfile, it answers correctly on port 80 in his example? Nope, that's not how that works. Cloudflare is translating his DNS into his Tailscale IP/Domain and then you are basically connecting through the Tailscale IP/Domain. This method that he uses here never connects through the servers port it just connects through your Tailscale IP/Domains.
January 31, 20251 yr 14 hours ago, ich777 said: Nope, that's not how that works. Cloudflare is translating his DNS into his Tailscale IP/Domain and then you are basically connecting through the Tailscale IP/Domain. This method that he uses here never connects through the servers port it just connects through your Tailscale IP/Domains. OK. Then I dont really know what's wrong. I followed the example. Only difference is unraid vs Proxmox.
January 31, 20251 yr 2 hours ago, AmbyDK said: OK. Then I dont really know what's wrong. I followed the example. Only difference is unraid vs Proxmox. But Alex also doesn't connected through port 80 or 443 directly, Cloudflare redirects directly to the Tailscale Domain name and therefore you are connecting directly to Tailscale <- of course this only works if Tailscale is installed on the machine that you are trying to connect. However what you can try is to put the Caddy container on br0 (with host access enabled in the Docker settings). I'll look into that ASAP.
January 31, 20251 yr On 1/22/2025 at 8:01 AM, ich777 said: Can you please be a bit more specific with which containers so that I can take a look at it? Hey! My Grist (https://www.getgrist.com/) container is throwing the same error message: ERROR: Can't get Tailscale JSON ERROR: Unraid Docker Hook script throw an error! A fix in the plugin would be very much appreciated. Also any tips on how to solve the issue of the plugin myself. For me, it is not yet pressing enough of an issue to employ the work around using the Tailscale Docker container. Cheers!
February 1, 20251 yr 4 hours ago, Purkan said: A fix in the plugin would be very much appreciated. Are we talking about the plugin or the Taggle switch in the Docker templates? A fix is coming for the toggle switch on the Docker page in the next Unraid version. I haven‘t looked into this container but most likely ca-certificates is missing or a really old version.
February 5, 20251 yr On 2/1/2025 at 3:40 AM, ich777 said: Are we talking about the plugin or the Taggle switch in the Docker templates? Sorry for the ambiguity! I meant the toggle switch in the Docker templates. The other one works like a charm!
February 5, 20251 yr 30 minutes ago, Purkan said: Sorry for the ambiguity! I meant the toggle switch in the Docker templates. A fix is coming in the next Unraid version, issue is that ca-certificates is probably missing in the container. You can also install it by hand in the container and restart the container afterwards, this should also work for now.
April 26, 20251 yr On 2/5/2025 at 8:33 PM, ich777 said: A fix is coming in the next Unraid version, issue is that ca-certificates is probably missing in the container. You can also install it by hand in the container and restart the container afterwards, this should also work for now. I have the same issue with a different container (pihole-unbound). Haven't received any response on developer's GitHub. Could you please elaborate on what certificates are needed on the container and how we can manually install them? Thanks!
April 26, 20251 yr 28 minutes ago, viper1190 said: pihole-unbound Do you have a link to the container? You forgot to include the maintainer. Please also post your docker run command (with Tailscale enabled) and the exact error message.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.