guillelopez

In my case to get USB working to boot unraid as a Proxmox VM I needed to move the USB drive to another port on the server, as in the first one I don't know why, was refusing to recognize the passthrough USB as bootable device on the VM. Ended installing the USB drive on an interior port on the server. Now works without problem.

For me since 6.12.6 the server gets stuck more often when running a process on simple docker containers like Jdownloader2 or Krussader. The CPU goes full overload even if I have the the containers pinned to only few cpu cores.

User and Pass no longer works with Nordvpn, at least over docker. It seems they made some changes on their servers. Now you need to go to your Nordvpn account and create a token. Then try use TOKEN="xxx". It should work also on bubuntux/nordvpn as it is included in its "how to use" at Git. But I completely abandoned to use that repository after many constant bugs on every single update. It has been like a year that had been a pain in the ass to use it.

I changed the repository to use Nordvpn on my Unraid server to https://hub.docker.com/r/tmknight88/nordvpn/ Now it seems to be necessary to use the Token value instead of User and Password, but this repository seems to work perfect, at least for me. Here is the most important environment variables I put to get it to work: but in his github there are also other environment variables that you can use. https://github.com/tmknight/docker-nordvpn And if anyone want to add the icon URL, I used this one: Logo

I downgraded the container editing it with the repository: bubuntux/nordvpn:v3.12.3 And now is working again for me. Hope that helps you. I guess something is wrong in the last update, so we have to use this meanwhile

@Echolot I didn't even thought about something like that hahaha. I thought that may be It were some kind of latency on my local lan that produced that kind of error, as modifying it on nano from ssh console, changes should be made locally. I updated to 1.4.1 with latest tag and now can modify config without restart. 🤘

With dev-config tag I don't have the reload issue. Seems to work that 500ms delay. Unfortunely for the new "stopOnTimeoutIfCpuUsageBelow" parameter, I don't have a use case yet to test it.

On Sublime I was using UTF-8, but yes after restart ContainerNursery, same config file works. It's just when saving it with the container running. Tried to edit and save it from cli with nano on the Unraid system, and instead it works fine at how it should be, no need to restart the container. So definetly something related with the text editor. Would like know what text editor does @kjames2001 use. But for me this is not a big deal. Just restart the container or use nano on cli.

This what @Kjames should be refering. This happens when I modify the config.yml on Sublime on my desktop Mac, and save it with the container running. Need to restart the container to be able get the change working. This also happened on Unraid with the previus package. If it helps in anyway I run 6.10.0-rc1 Unraid version. I also run ContainerNursery on a Proxmox server where I have some containers, and there I don't have the same issue. But there I modify the config.yml on cli with nano. PD: the configurable port works perfect, I changed to 90 on Unraid and use the default 80 on proxmox. Maybe I going to migrate all the config to proxmox as then I don't have to add the port on the local domains. But still I would be happy to still runing on Unraid to perfom test for you.

I removed the domain port on the config file and updated, working perfect. Will make some test with the configurable port at night when I come back home. Thanks a lot for your work. EDIT: Forgot to say that the guide on first post is great even for noobs like me 😄

@Echolot At least to add the port on the domain part in config.yml was an easy temporary walkaround. @kjames2001 I'm glad I was helpful. I also use Pi-hole on a raspberry pi, and my router is a pfSense, but couldn't get working it with the Pi-hole local DNS or with the pfSense DNS Resolver. Probably something messy on my config, or I'm forgetting to do some steps. But, for me, the most elegant solution seems to be the provided on the GitHub Project with NginxProxyManager, that let you specify the forward port. Need to learn how to properly implement it on my system.

That did the trick, I used Bridge Network on ContainerNursery and maped 80 to 8080, then used my Unraid ip as proxyHost. But I need to change also the domain on config.yml to use http://filebrowser.rack:8080, with just http://filebrowser.rack there, ContainerNursery told me on browser "Proxy configuration is missing for http://filebrowser.rack:8080" So my config.yml looks like this: proxyHosts: - domain: filebrowser.rack:8080 containerName: FileBrowser proxyHost: 192.168.1.9 proxyPort: 85 timeoutSeconds: 1800 - domain: krusader.rack:8080 containerName: Krusader proxyHost: 192.168.1.9 proxyPort: 6080 timeoutSeconds: 1800 And ContainerNursery config: Let me know, if you have time, to do more test with other configurations so we can find a perfect use to Unraid. Thanks for your help and your really nice app.

Well I managed to get it nearly working. I created some host names on my desktop /etc/hosts file. "192.168.1.4 filebrowser.rack" and "192.168.1.4 krusader.rack" I changed the network on your container to custom and used the 192.168.1.4 ip for it. (as I don't want to change Unraid 80 port and can't use ports on /etc/host file, this seemed for me the best solution) and my config.yml is this: proxyHosts: - domain: filebrowser.rack containerName: FileBrowser proxyHost: localhost proxyPort: 87 timeoutSeconds: 1800 - domain: krusader.rack containerName: Krusader proxyHost: localhost proxyPort: 6080 timeoutSeconds: 1800 But I only get an infinite waking up FileBrowser or waking up Krusader. On ContainerNursery logs I get Host not reachable. Tried to change localhost for the unraid ip, and still no luck. Also tried internal containers ips (172.17.0.3 or 172.17.0.8) with their normal ports and also no luck.

Good news then I managed to configure it so ContainerNursery log said it can detect the other containers, and using the Bridge Network I maped the port to 86 and with the host-ip:86 but still didn't got it working properly, just was able to after 1800s the app turning off the other containers. I think I should try to learn today something about DNS resolvers and this kind of stuff. I access my containers with the ip:port, i'm a simple man 😅 I was following the GitHub Project guide, but get confused with the Domains and NginxProxyManager part, as I not used to it. But as I said, something new to learn. Thanks!

Would love to see a guide to config this. Seems to need a reverse proxy also? I'm not used to local domain names and not sure how to create them to work with my docker containers. I'm not sure if I need to install something different or use my pfSense system. And does not the container 80 port interfere with the Unraid server 80 port? But seems a great add to the repository, so thanks for your work!