Nodiaque

I myself can't get lyrion to work like lms. The original lms detect my Chromecast and dlna device no problem. I can also play directly from the browser on my computer. On lyrion, even after trying all Chromecast and dlna plugin, none see mt Chromecast or dlna device and I can't play anything directly from the browser cause it's saying no player. And when I try from my android phone, it doesn't see my squeeze app.

I just started the new server and had a problem. Scan wouldn't start. Looking at the log, it was saying it's unable to open/write to perfmon.log. When looking at this folder, 2 log file where own by root perfmon.log and server.log. I stopped the docker, changed the owner to nobody:users and started back. Now everything is working fine. It seems the docker still run as root (if I do whoami when I check in remote console, it's root) but the service run on 99:100.

It's weird. Steam normally download the new version itself. Something must happen on your other docker.

It auto download the latest version from steam. If it's not updating, it's because it's not yet available. The docker itself contain nothing from the game itself, just a wrapper to download steam and start downloading through steam. You can check by starting another container with a new folder. If it's the same version, blame steam.

Oh good to know for the custom. My players haven't told me about it although I did change it. I don't have the game, I just host so I can't verify the change. I will have to change some of the script that create that group. I might just remove it from the template and have user follow the guide since it has way more option now then it used to. I'll also have to remove the base template that the docker create right now and let the game create one per default if none present.

I just installed it and did nothing else. Nginx talk using http cause that's the port that is configured in that docker. But Niginx itself is in https. The default swag configuration is to use port 443 and https, but these port aren't in use. And if I try to access nextcloud directly using https, it fail.

Hello, How do we get rid of "Accessing site insecurely via HTTP. You are strongly advised to set up your server to require HTTPS instead. " ? The documentation talk about modifying stuff in apache but doesn't say much. I'm accessing by reverse proxy so I'm already in https, but since the proxy is using http, that's the problem. EDIT: I also have the problem that I cannot run it as --user=99:100 because I'm using redis. Because I'm using redis, it will fail saying it cannot create a file on startup and crash. edit2: unsure if there's another way but I solved the problem with redis by mapping the file redis-session.php outside the container. I also copied the file outside the container and mapped it inside the docker. I'm still trying to find the solution for the HTTP error though

What I feel is the json format as changed since the template was done. It seems the password field as changed since and is no longer working. I'll need to update it. Problem is I don't have access to my development setup right now, I'm undergoing renovation and everything is boxed. For now, you can forgo that configuration and edit the json directly (don't forget to shutdown the docker first)

If you can connect locally but not from the web, you have a firewall problem. Either port forwarding is not correct, your public ip is not the one you think or maybe your isp is blocking it. There's unfortunatly nothing I can do for this. Variables are all in the template, it's field in the docker window when you select the apps. They overwrite the value in the json at startup. Any modification in the json directly will be overwritten by the template for these values. If you want to set them directly, you must delete the variables from the template in the gui (it's been a long time since I've done that template, I'm unsure if that will result in an error, pretty sure it won't). You must not modify the json while the server is running (won't do anything anyway and you risk losing your modification). You can modify the json to add stuff that aren't connected to the modification made by these variables.

no, not at all.... I don't use duckdns as dns resolver... My pfsense has it's own DNS server, unbound. This one is the resolver the lan use per default. I can configure any client to talk to him and it will answer. His upstream DNS are the one from my ISP on the wan side. In pfsense, I have created a DNS entry (cname) for my local service which are on my domain *.myserver.duckdns.org and also an entry for myserver.duckdns.org to resolve on my internal ip. Any client connect to pfsense has a dns client will receive this internal ip. This work perfectly. Since I already had pihole before having pfsense and I liked how it worked (except the fact they can't sync natively), I configured pfsense do any DHCP client get pihole DNS instead except for my unraid server where one is myserver.duckdns.org. In PiHole, I configured the upstream DNS server to be my pfsense. So anything not resolved or in cache will go to pfsense. My unraid server doesn't talk to pihole, and pfsense doesn't talk to pihole. So there's 2 possible resolve path here: DHCP Client like a personnal computer connect to the network and make a DNS query. The Path will be Client -> pihole -> pfsense -> upstream ISP DNS If my unraid servers or any dockers on them make a DNS query, the path will be Docker client -> Docker Host (unraid) -> pfsense -> upstream ISP DNS. The request can stop at pihole or pfsense if the value is known. In my current case, the path for the request will be DHCP client: Client -> pihole (not found forward to upstream) -> pfsense (found in dns entry with local ip) -> pfsense reply -> pihole get the reply and forward to client -> client receive the ip Dockers/Unraid: Unraid -> pfsense (foudn in dns entry with local ip) -> pfsense reply -> docker/unraid receive the ip. I've query all 3 DNS, all 3 always answer with the internal ip since they all go to pfsense to get the ip. If I shutdown all 3 dns, all docker ping give me cannot resolve error..

Hello, I think you missed the point that my unraid server doesn't use pihole itself. Both unraid server have my pfsense as dns resolution, not pihole. By the way, you do control the sequence in which your docker bootup. It start from top to bottom in your unraid docker list (and if you have docker folder, top to bottom of each folder). You can also set a delay to pause between each docker. PiHole is the first docker to boot up. I have some docker that have a wait 30sec on them (after database bootup). Some docker before and after that docker have the problem, others don't. Pihole doesn't even know my server.duckdns.org ip, it ask pfsense for it since it's pfsense that has the entry in the resolver, not pihole. If both pihole would be down when booting and I would be using those as dns resolver for unraid, the ping would just fail as name cannot be resolved, it wouldn't resolve as something else entirely unless it has another DNS server configured somewhere. Docker use host DNS resolution, and the host (unraid) in this situation use pfsense, not pihole. Thank you edit: both my pihole are bridge to have a static ip on the network dedicated. I also have host access to docker. My unraid could use pihole (it was in the past) but it was causing problem when dockers on both server where down thus why I reverted long time ago to use my router resolver, which is also the upstream dns for my piholes. In any case, neither of them should give me the public ip of my network instead of the internal ip that my router give

Hello everyone, I have a problem with DNS resolution in some docker. The problem seems to arrive only after a reboot. My network topology is as follow. I have 2 pihole server running on 2 different unraid. I have pfsense has my router, firewall and dhcp server. The DNS for all DHCP client is configured for these 2 pihole. I have a static configuration for my unraid servers where their DNS is pfsense. Since I want my dns to keep working on my servers if both pihole are down for whatever reason. This also mean that pfsense is my resolver for all of my docker. The 2 pihole servers have my pfsense firewall has the resolver, and pfsense resolve with it's own mechanic. In pfsense, I have created an entry in the dns resolver fo myserver.duckdns.org. Doing so, when I ping myserver.duckdns.org, it refer to my main unraid server from whatever which computer I ping from. Now, I just had a power outage. Found out my main unraid server wasn't on the ups but on the power surge side when I cleaned it earlier this month. Because of that, it died and then rebooted. Upon reboot, I get a warning from my watcher that some service are down but they aren't. The configuration check for https://myserver.duckdns.org:8888/ (port not important) and if there's no answer, it's down. If I open the docker cli for that docker and ping myserver.duckdns.org, I get the public ip! If I open unraid cli and ping myserver.duckdns.org, I get the local ip. During the power outage, pfsense and the other unraid server didn't die. So now, I'm wondering how this docker resolve to my public ip. The docker is using my-bridge (like 99% of my docker), a custom bridge I made age ago when I setup unraid and was in one of space invader tutorial on docker for unraid. resolve.conf on that docker give that configuration: nameserver 127.0.0.11 options ndots:0 I know that if I restart the docker, it will work now. Suddenly, it will get the right ip. This seem to happen to other docker too. All I have to do is restart the docker and it solve the problem, but I don't get why they have the problem in the first place. thank you

hello, I just saw in the community apps there's a new version but when I click update, the log says already last version. But my version is 2023.12.19. I'm on 6.2.11 unraid. I also see 2 Mover Tuning in CA that point here, one is 2023.12.19 and the other is newer but even if I click update on the newer, it seems to only install the old one edit: well when I open the plugin, it shows 2024.08.16 so I guess it's the reporting in CA and in the plugin page that is not right

No problem mate, glad I could get it working! Right now, it seems that my pihole is answering. I had tailscale already setup before but using the docker and I'm switching to the plugins. I was checking my setting at the sametime. Thanks again!

On my client, I have a warning saying "DNS Unavailable. Tailscale can't reach the configured DNS servers. Internet connectivity may be affected". When I do a nslookup, I see it's tailscale dns that answer nslookup nodered.########.duckdns.org Serveur : magicdns.localhost-tailscale-daemon Address: 100.100.100.100 Nom : nodered.########.duckdns.org Address: 192.168.0.4 but it does have the local ip address. Is it because in the Admin Console, under DNS, I entered the local ip of my 2 pihole server? Since it's local ip, tailscale can't reach it from outside the vpn?

Ah. If what I want is to be able to access all of my dockers that are either on that unraid or other server, do I need that?

what does accept-routes do in the end? I notice that it's not enable on tailscale on my pfsense installation

Hello, is there a switch to enable exit-node and set advertise routes? Would be nice to have that in the gui. I tried running tailscale up -advertise-exit-node -accept-routes -advertise-routes=192.168.0.0/24 and I get error that I must run tailscale up --accept-routes --advertise-exit-node --advertise-routes=192.168.0.0/24 --accept-dns=false when I did, I lost access to my server entirely (all docker services and gui, even ping stopped responding) and had to restart my server...

Hello everyone, I've installed a new switch L3 unifi switch on my network. Since I did that, it now sees everyone on my network in the unifi controller and it's reporting 2 active mac on same ip. From what I find out, one of them is the MAC of my NIC and the other one is vhost0. Is there a way for vhost0 to not have an ip on the network and just let whatever docker/vm that use it get an ip? In the network settings, I don't see anywhere to not give it an ip. Thank you

Hello, I have a problem with a specific docker (maybe more but notice on one). When I click on edit, it show me the generic docker template instead of my-dockertemplate.xml that is present and used by the container. Because of that, when I don't pay attention and just want to modify a specific value, the docker get reset with generic template value How can I solve this so it stick to my-dockertemplate that was used to create the docker? thank you

Hello everyone, I'm getting a new switch that have 10G support though SFP+ port. I was wondering what NIC card is recommended and supported by unraid so I can connect my server using it? Thank you!

Hello, You must shutdown the server and when it's completely closed, then you edit the json file. If your editing from a Windows os, I suggest using notepad++ or better yet install code-server application on unraid and edit directly from web (it's the best thing to prevent format conversion).

I never heard of that but I did read about performance problem in the past. I haven't looked back at the game for a while (I know I have player on it and no complaint but I do have a beast), maybe they finally made a Linux version which would ditch the compatibility library for it. I must say, this game is hungry though. As for memory allocation, as far as I know, docker take as much as it need? I never set any memory allocation for any of them and they use whatever they need

That's something with the game itself, not something I can fix

Nah it won't do that. I cannot say why it did it, but it's the game fault if it happened. Could be many reason, corruption could be one. Saw it on various game and not just docker.