ngreis

Hi I was trying to install nextcloud docker, and it asked me for a seperate ip for it. I set it inside my LAN range, and started the container. Since i could not get to that ip, my scan tool did not find a ip in the LAN, and i did not find it inside the unifi clientes page, i guesse i needed something more. I started to google a bit, and found this setting in Docker settings: HOST ACCESS TO CUSTOM NETWORKS. I read that enabling that would allow for what i needed, or at least it was what i think it would do. After selecting that option, and activating the Docker back i lost connectivity to the unraid UI, i cant access any docker nor the shares in my network PC. So i guess i needed something more and messed this up. Can anyone please tell me how to revert that setting via CLI or tell me what i did wrong and how to undo it? This is installed as a VM inside a ESXI host, so i can access the CLI form the ESXI console, i cant putty into it nor access anything on the network. Also after rebooting on the ESXI console the unraid CLI says the IP to access the web ui is the same as it was, but when i try it, it does not work I have 1 virtual nic on the server, if i recall the bonding was set to true on the unraid server network settings, but i cant rememeber much more from the top of my head. Can anyone please tell me how to revert that setting via CLI, or tell me what i did wrong and fix it? Kind regards Nuno Reis

Hello Could you setup a docker container for a steam game called Space Enginers? Thx in advance Ngreis

Hello Should i rerun all this with the :test flag or can i use de "normal" repo? I also had a wife that got in the way, and the 3 kids, cat, dog and mother in law, XD its a full house here! Best regards Nuno Reis

We got UI Just got this in the logs. ERROR: Cannot open "/C:\urbackup": No such file or directory (2) Apart from that, UIseems to work, hoing to test some stuff

I am also running dual Xeon X5590 i think or X5690, as a matter of fact, form the unraid CPU, widget: Intel® Xeon® CPU X5650 @ 2.67GHz if we wat to be precise Will try the :test thing. EDIT: Same error as the last 2 users.

Hello Did all of the above things in the thread, issue still the same. Running 6.7.0 also. Will also wait for a fix for that bug. Best regards Nuno Reis

2019-07-31 08:07:58,322 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22830330100704 for <Subprocess at 22830330192056 with name urbackup in state STARTING> (stdout)> 2019-07-31 08:07:58,323 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22830330191944 for <Subprocess at 22830330192056 with name urbackup in state STARTING> (stderr)> 2019-07-31 08:07:58,323 INFO exited: urbackup (exit status 132; not expected) 2019-07-31 08:07:58,323 DEBG received SIGCHLD indicating a child quit 2019-07-31 08:07:59,326 INFO spawned: 'urbackup' with pid 48 2019-07-31 08:07:59,353 DEBG 'urbackup' stderr output: /home/nobody/start.sh: line 15: 53 Illegal instruction /usr/bin/urbackupsrv run --config /config/urbackup/config/urbackupsrv --no-consoletime My error log also, the same.