pbear

Hello, About the docker Dozzle, Even when we change the env variable WebUI for another value, the daemon still listens to 8080. This env. variable is by default in the template.

Problem solved with the new v6.12.6 indeed 👍 Thanks for your work.

I confirm this v6.12.6 solved the ipv6 problem I had since v6.12.4 , the sshd now listen well on every ip \o/ Thank you for this release, have a nice day everybody.

Hello, Well, I already did send my diagnostics file to the support by email, had opened a thread and even opened a thread on discord. The only answer I got was from the support (email) who adviced me to wait for the next release. Anyway I updated my thread with extra infos and a new diganostic file. Thanks,

So I had downgraded to 6.12.3. But now that the v6.12.5 is out I tried it: the ipv6 works with the docker. But I still can't connect to the server itself, the ssd still does not listen to ipv6. ⚡ root@unraid:~# netstat -tulpn | grep 22 LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=31080,fd=3)) I tried restarting the /rc.sshd script and it populates my ssh_config like that: ListenAddress 10.0.2.2 # br0 ListenAddress 192.168.12.2 # br1 ListenAddress 0 # which is wierd , IMHO. I don't know this "0" And there should be one line "ListenAdress ::" I believe. The script gives a error message when restarting: "/etc/rc.d/rc.library.source: line 74: printf: 0xmetric: invalid hex number" ⚡ root@unraid:~# sed -n '73,74p' /etc/rc.d/rc.library.source [[ -n $b ]] && d= a=${a%$f*}${f}$(for q in ${b//./ }; do printf "$d%03x" "0x$q"; d=.; done) [[ -z $m ]] && echo $a || echo $a/$m Could be a syntax error in this other script ? unraid-diagnostics-20231129-1955.zip

As I already had with 6.12.4, I cannot connect to my unraid server through his ipv6. I had downgraded to 6.12.3 until now for this reason (among others). ⚡ root@unraid # ss -tlpn | grep :22 tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=24054,fd=3)) I don't know why it doesn't listen on [::]:22 Any idea ? (But with this version, unlike v6.12.4, the ipv6 works with my docker containers.)

@aglyons I did a rollback because my ipv6 didn't work at all since I upgraded to 6.12.4. I contacted the support and their answer is to wait another release, indeed. But when I came back to 6.12.3 I also had to switch back to macvlan because with IPVLan all my containers have the same Mac address and my ubiquiti UDM isn't able to detect them as "separate clients". So I couldn't route them individually anymore (because they don't appear in the drop menu in the interface of the UDM). Did you find a solution ?

Hello, As I got no answer, I ended up contacting the support. But as I said I also have trouble with ipv6 on the unraid itself (with the sshd not listening anymore on the ipv6).

Hello, After I upgraded to v6.12.4, it looks like my ipv6 does not work correctly anymore. First I couldn't ssh my server because the ssh doesn't listen to ipv6 anymore, only ipv4: root@unraid:~# netstat -tulpn | grep 22 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 7411/sshd: /usr/sbi Second, the ipv6 is not available for docker containers. The ipv6 subnet doesn't appear in the EDIT view of the containers. So I had to remove it from each of them to be able to start them. My docker network type is ipvlan. My config is the following: Also, I have a error message: I believe it's not related to ipv6 but it also appeared with the last update. What can I do ? KR,

I see that the template already set a limit to 12G. Isn't it another container that gobbles up all the RAM ?

Hello, I got the alert message again. **Out Of Memory errors detected on your server** I have 4 VM running, using a total of 20G on the 64G available. I have around 32 docker containers running, is it too much ? I join the diagnostic file form today. Could it be analysed ? Thanks, unraid-diagnostics-20230820-0944.zip

Ok, nothing special on the diagnostic file ? I'll update this thread if this happens again.

Did something change with a recent update ? I cannot connect to the web interface anymore. I checked through the console, and no deamon are listening on 8080 (or 9090) anymore: Do I have to do something ? KR,

Hello, Today in the report of the plugin Fix Common Problems, I see: * **Out Of Memory errors detected on your server** So could you check why ? I join my diagnostic report file. For now: Yesterday evening, as we were watching a movie through Appletv4k (Plex) and the unraid server (Plex container), the Plex server suddently crashed. It came back by itself after ~1 minute. Maybe there is a link between both events. Thank you, unraid-diagnostics-20230813-1908.zip

Hello, I see the same error messages in my libvirt logs: 2023-04-21 05:06:45.301+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error 2023-04-21 05:16:47.245+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error 2023-04-21 05:26:49.130+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error 2023-04-21 05:36:51.072+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error 2023-04-21 05:46:52.946+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error 2023-04-21 05:56:54.872+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error Also, when I reboot my unraid server I receive an email about an error: Event: VM Autostart disabled Subject: vfio-bind-error Description: VM Autostart disabled due to vfio-bind error Importance: alert I'm not sure that both events are related.

Hello, But how to send this sequence in through the QUEMU noVNC windows ?

I invested in a little eaton UPS so it is not about power outage but I install every unraidOS update, so I reboot it frequently. My longest uptime is 6-7 months at most.

Safari most of the time since we are full of Mac at home Brave and Firefox when under windows. Definitely not bigbrother-chrome.

Hello @MarkusMcNugen The CrushFTP v10.3 is out, can you update the docker ? Thanks

Hello, I have the same problem

Hello, Thank you for the troddit container. Is there a way to change the default listening port (when running custom/br0 dedicated ip) ? KR,

Hello, I have a problem with some of my containers and ipv6 Let's talk about Jackett for example (and I tried the different releases available on the App Store and I hv the same problem). I've configured the container with Network Type: custom br0 and I have set a ipv4 and ipv6 (10.0.1.39, 2a01:my:pre:fix:10:0:1:39). But Jackett couldn't reach some websites so I've investigated and found out in the log of my firewall (pfsense appliance) that it is using another ipv6 ! (which is not allowed in the firewall of course, if I do, Jackett works perfectly) Logs: [2a01:my:pre:fix::42:aff:fe00:127]:42308[ipv6destination]:443 1) I don't know why it is using this host ID 42:aff:fe00:127 2) I cannot find this ipv6 on my unraid server docker inspect --format {{.NetworkSettings.Networks.br0.GlobalIPv6Address}} $(docker ps -q) | grep :127 docker inspect --format {{.NetworkSettings.Networks.br0.IPAMConfig.IPv6Address}} $(docker ps -q) | grep :127 ==> nothing (But maybe I'm not using the best commands to investigate.) Can someone help me ? Rmq: ipv6 is working as expected with most of my containers only 2-3 have this problem. Rmq: "IPv6 privacy extensions" is disabled in the network settings. Rmq: I've replaced a part of my network id with "my:pre:fix" for privacy purpose, but of course it is configured with the correct one. KR, P'Bear

" This Docker image allows Plex Pass account holders to get early access to new features which is great. " Yes I've read but I what are currently those new features ? It's not obvious Plus when you say "To be clear, the binhex-plex Docker Image still allows you access all the additional features you get with a Plex Pass account, it just means you will get delayed". Since it's an older version (v4.69.1 vs official v4.72.0) haven't we already those new features included ?

Hello, sorry if it's a dumb question but we bought a Plex pass so I'm trying this container but we cannot find the difference with our regular Plex server. Plus this Plex is v4.69.1 and our regular docker Plex container (plexinc/pms-docker) is v4.72.0 So could you explain what are differences and advantages of this one when we have a Plex pass ? Thank you and happy new year !

Hello, About Pritunl, when you say in the description "until UnRAID supports ipv6" is it an old description out-of-date or is there something specific missing ? Because unraid works with ipv6 for vm and docker containers. KR,