Everything posted by chalk
chalk replied to patrickstigler's topic in Docker ContainersAny chance you could add the obs-multi-rtmp plugin? https://github.com/sorayuki/obs-multi-rtmp, advanced scene switcher https://github.com/WarmUpTill/SceneSwitcher, and the WebSockets Server Settings https://github.com/obsproject/obs-websocket plugins? Thanks!
[Support] SpaceinvaderOne - Macinabox
chalk replied to SpaceInvaderOne's topic in Docker ContainersSame issue here! Hopefully someone can help with this.
[Support] A75G Repo
chalk replied to A75G's topic in Docker Containersblue iris in a docker? Amazing work! Thank you very much!
As reported by deusxanime under the Wireguard thread. I am having this exact same issue. I noticed a possible bug/issue with WireGuard on unRAID. I have a docker container that runs on a custom network and I needed it to talk to a container on bridge so I went into docker settings and enabled "Host access to custom networks". After doing so (and all the required stop/start/reboot), the containers could talk on the network and I thought all was well. Later that week I tried to use my WG VPN tunnel access (LAN access and tunnel through server to my home internet WAN) on my laptop and phone, which I'd used previously and worked great then, since I was on an untrusted Wifi network. After connecting, I was able to access LAN resources on the unRAID server, but could not get the WG client systems to go out to the internet when I had WG turned on on them. I thought back to what had changed and all I could think of was the setting above. So today, since I had to restart unRAID to add a disk, I disabled that setting to test it out and after restarting I tried WG tunnel access and lo and behold it is working again! I can get to LAN resources as well as out to the WAN/internet while connected to WG on the clients. So it seems like something with enabling the "Host access to custom networks" setting breaks WG's ability to allow VPN clients to tunnel through it and use the WAN while connected.
How can we raise a bug report for this issue?
I am having this exact same issue. Prior to enabling "Host access to custom networks" Wireguard worked perfect for over a year. Since i have made this change it it no longer works.
Creating Unraid Template for existing Docker
chalk posted a topic in General SupportHello, I am looking for a little guidance on how to create an unraid template for a docker container. I am looking to run the following docker on my Unraid server: https://hub.docker.com/r/falconchristmas/fpp https://github.com/FalconChristmas/fpp Would anyone be able to point me in the right direction on how to get started with this? Thanks!
I also woke up to this issue. Rolled back and everything is working fine.
I tried adding this to my nginx configuration but I am still getting the error message. :(
I am having the exact same issue. After doing some digging I was able to correct this issue by doing the following: From the console of the nextcloud container console run the following command from within the /config/www/nextcloud directory: sudo -u abc php occ maintenance:mode --off Rebooted the container and I was able to log back into the old version.