Bungy

Already done. You should just need to update your container and all will work. Sent from my Nexus 5X using Tapatalk

Wow sooooo official. Hopefully that doesn't go on my permanent record!

Did you read the moderator comments? It explicitly states the container is deprecated. Sent from my Nexus 5X using Tapatalk

Sorry, but the openhab docker is deprecated now. I haven't pushed an update to it in a LONG time as I've switched to home-assistant for my home automation needs. I find it to be a much easier platform to configure and develop on. If you're set on using openhab, your best bet is to use the official openhab docker found here (https://hub.docker.com/r/openhab/openhab/). There isn't an unraid template for it, but I'm sure one can be created with little effort.

Migrating mysql dockers may be difficult as linuxserver likely uses a different directory structure. Your best bet is to use mysqldump to dump the sql tables and then import them back into the new docker. Also, just FYI, it's actually the official mysql docker. I'm not the author of the container.

You can pass through block devices to guest VMs without using iSCSI. In fact, its super easy to do. First, login via SSH or Telnet and type this command: v /dev/disk/by-id Locate the disk you wish to pass through and copy its name. Now go create your VM and under vDisk location, select "Manual" and in the path field, type /dev/disk/by-id/ and then paste in the name of the disk you wish to pass through. You can optionally include the partition so if you want, you can have one disk with 3 partitions and pass through different partitions to different VMs if you want. What does iSCSI gain you over this method? It gains me nothing for my use case. Your method is likely faster, I just didn't know about it! I'm actually very excited to try that out.

For those interested in trying out iSCSI and figuring out if it works for you, I have a working install with the proper activated kernel modules. I currently am using targetcli in a docker and it works great. There is no GUI so you have to be comfortable with setting up the iqn, acls, luns, portals, etc. manually. I'm currently using iSCSI to allow guest VMs block level access to drives without having to passthrough drive controllers. One thing to keep in mind is you cannot create block level luns for drives that are already mounted. If you want to use those drives, you'll have to use fileio.

All, I was able to recompile the unraid kernel for Unraid 6.3rc4 to include the necessary headers to get targetcli working on unRAID. I'm still in very early stages of getting things working and learning about iSCSI targets. I'm a bit lost on what benefit you guys are expecting by having unraid as an iSCSI target. I understand the difference between shares and block level access, but the use cases I've seen so far don't seem like they'd gain much from iSCSI. I believe the main arguments are for performance increases, however the performance would still be bottlenecked by the parity write speeds. I believe I'm missing something fundamentally, so anybody can educate me, I'd appreciate it.

Fantastic! Glad that worked for you! Sent from my Nexus 5X using Tapatalk

Make sure that the file has the permissions 0640 and is owned by uid:guid 33:65534. To set those permissions, use the following command: chmod 0640 config.php chown 33:65534 config.php After you set those permissions, it's likely that you cannot edit the file through samba anymore. Instead, use nano to edit the file: nano config.php Nano is built into unraid and is a very easy to use terminal-based text editor. It may be useful to google a quick nano tutorial. It's easy to use, but isn't straight forward your first time using it.

This was an issue with experimental branch, but the master branch should be ok. Can you make sure you're on the newest image? If you're on the newest image, can you post the rest of your configuration so I can replicate? You can leave out the username/password. FWIW, I had a similar issue but it could've just been the VPN_Protocol env variable was missing. I think binhex defaults to nl.privateinternetaccess.com with his vpn dockers so I just switched to it with nzbgetvpn as well. That's a good point. It could be that the VPN_PROTOCL env was not configured and was causing the issue. I'm using the same baseimage as binhex's deluge and sabnzbd dockers now, so the configuration for openvpn in my docker should be exactly the same as those dockers.

This was an issue with experimental branch, but the master branch should be ok. Can you make sure you're on the newest image? If you're on the newest image, can you post the rest of your configuration so I can replicate? You can leave out the username/password.

Oh I see what you're saying. I'll update the template Sent from my Nexus 5X using Tapatalk

Indeed! Bungy are you able to do this? Thanks, and so far I have been loving the NZBGETVPN Docker you've provided. I put a bit of time into it, but didn't get very far. I ran into a self-signed cert issue, and I ran out of time to work on it. I'm a bit swamped with work at the moment, so I can't quite do this right now, but maybe over the weekend. I want to switch to binhex's baseimage and use his awesome openvpn setup, but I'll have to postpone until things calm down a bit. Totally understand, and I'll look forward to when you can. Thank you sir! I was able to update the docker to use binhex's openvpn as the baseimage. You'll need to update your docker to include these environmental variables VPN_ENABLED=yes VPN_PORT=1198 (if using PIA) LAN_NETWORK=192.168.1.0/24 (or whatever your home lan network is) VPN_PROTOCOL=udp (if using PIA, may be tcp for other providers) Let me know if you have any issues. The build should be done in a couple of minutes. Thanks Bungy for this vpn version of nzbget. Just an FYI that this docker is still missing the VPN_PROTOCOL env variable. Also, VPN_ENABLED has a typo (VPN_ENABED). Can you give me a little bit more detail? I'm not seeing the typo or the missing VPN_PROTOCOL env var.

I need to update the description. It's general purpose and can be used with anything Sent from my Nexus 5X using Tapatalk

Strange. I was able to upgrade from 9.0 to 9.1.1 without much issue. I had to disable my apps directory in order to get the upgrade to proceed properly, but it eventually worked. I'm not sure what your issue is, but if you want to stick with owncloud, it may be worth contacting owncloud's support staff or searching their github issues page.

What version were you on previously? My guess is you're doing an upgrade over several versions when you should be upgrading to intermediate versions first. Sent from my Nexus 5X using Tapatalk

That's an improvement - now the logs shows this: 2016-08-08 06:37:13,182 DEBG 'start-script' stdout output: [crit] VPN provider remote protocol not defined (via -e VPN_PROTOCOL), exiting... Whoops, I should have added that you'll need to add the env variable VPN_PROTOCOL=udp (for PIA, it may be tcp for other providers)

Try changing the VPN port to 1198 Sent from my Nexus 5X using Tapatalk

Thanks for this, however after updating my docker won't seem to start and no message listed in the log. Hmm.. not sure what the problem is. Can you post your docker run command (removing username/password information)?

Indeed! Bungy are you able to do this? Thanks, and so far I have been loving the NZBGETVPN Docker you've provided. I put a bit of time into it, but didn't get very far. I ran into a self-signed cert issue, and I ran out of time to work on it. I'm a bit swamped with work at the moment, so I can't quite do this right now, but maybe over the weekend. I want to switch to binhex's baseimage and use his awesome openvpn setup, but I'll have to postpone until things calm down a bit. Totally understand, and I'll look forward to when you can. Thank you sir! I was able to update the docker to use binhex's openvpn as the baseimage. You'll need to update your docker to include these environmental variables VPN_ENABLED=yes VPN_PORT=1198 (if using PIA) LAN_NETWORK=192.168.1.0/24 (or whatever your home lan network is) VPN_PROTOCOL=udp (if using PIA, may be tcp for other providers) Let me know if you have any issues. The build should be done in a couple of minutes.

Indeed! Bungy are you able to do this? Thanks, and so far I have been loving the NZBGETVPN Docker you've provided. I put a bit of time into it, but didn't get very far. I ran into a self-signed cert issue, and I ran out of time to work on it. I'm a bit swamped with work at the moment, so I can't quite do this right now, but maybe over the weekend. I want to switch to binhex's baseimage and use his awesome openvpn setup, but I'll have to postpone until things calm down a bit.

You can ignore that command then. If you remove and recreate the container, everything will be set back to normal. It's more of a minor security concern.

No problem! I'm glad it worked out for you!

Gotcha, that should have been run from inside the docker. Sorry for that problem. If running from unraid do chown sshd:sshd PATH_TO_CONFIG.PHP Your path will be specific to where you keep your config.php file, but probably something like /mnt/users/appdata/owncloud/config/config.php