danioj

As the description indicates, every time you update / reinstall the container you have to reset the password. As a reminder, you do this from the Cli. docker exec -it openvpn-as passwd admin Also, you will have to re-add any uses you use beyond admin too. docker exec -it openvpn-as adduser <user> Nice and quick though!!

Hi Ashe. I am not surprised there are some kinks. Your outcome though is similar to mine, it works - just needs to be cleaned up. I think I will collude somewhat with Andrew and see if I can get it finalised. Ill spend some time on it this week.

I'm going to try and smile at that moniker, but truth be told I hate with a passion Andy. Much prefer Andrew or Squid or even a$$hole Nothing on my end ever needs to be done regarding updates to xml's. The application feed (by Kode / hosted by lsio) handles everything automatically and is automatically updated every two hours. If you happen to browse the categories looking for ZNC and its already installed, then you will not see it unless you either go to Installed Apps, or alternatively within the settings, you can turn off separating installed from not installed. IE: I've checked, ZNC is indeed there and everything is working as is. Sorry buddy ... no more abbreviations of your name! I should know better, I hate it with a passion when people call me Danny. Daniel or at a push Dan please!! I've obviously misunderstood how the system works. When it was mentioned the "xml needs updating" I VERY wrongly assumed that this was a manual process and also that it was on your end. WRONG! Lol! So I'll take this an opportunity to learn. Thanks for clarifying for me!!

Hey Andy!! The Linuxserver.io znc container has been moved from the lsiodev repository to the main linuxserver repository. I only spotted today that it doesn't appear in CA any more. A little birds tells me that there is some xml that needs to be updated to make it appear again!?

I need a little more. What isn't working? I can't connect to the server from inside or outside my network. I sent you a PM. Happy to help. I noticed an issue with the networking mode of the container when you choose to just open UDP port and also share port 943 for Connect and Admin Interfaces. Essentially when you setup like this the container doesn't seem to work in Host mode as is recommend. My resolution to this was to switch to Bridge mode and map 1194 and 943 to the Host. EDIT: God I can't spell. In the pic, ump is supposed to say udp. Toodles off to correct.

I need a little more. What isn't working?

I've just updated my container remotely and played a video fine. Tried Kodi too. Played fine. I need more. What is in your server logs?? Sent from my iPhone using Tapatalk I just read your post again - are you saying that your Emby container is not even showing in the Docker tab? Sent from my iPhone using Tapatalk

I've just updated my container remotely and played a video fine. Tried Kodi too. Played fine. I need more. What is in your server logs?? Sent from my iPhone using Tapatalk

Sorry, I have to disagree. A reverse proxy acts as an intermediary between the client and the web application you're accessing. It adds an additional layer between the client and the web application. A reverse proxy (in the scenario of using it to expose applications to the Internet) is available on the internet so generally anyone (unless you are going to set some really tight firewall rules) who knows the url will have access to that application. Although setting additional security like SSL (which just encrypts client to server) it is still directly connected to the web. In this case you are also going to be relying on the security system of each application for access. Much of the applications we all use (in a home server scenario) have different levels of maturity when it comes to their vulnerability to attack. In addition many of these applications authors advise (such as unRAID) not to expose their interfaces directly to the Internet. In contrast, a VPN has an additional layer of security as a client has to first authenticate itself with a server before a user has access to the VPN. If you therefore trust users of your LAN (which most people I know who use unRAID in a home setting would) you can even leave the applications unsecured by userids and passwords) as the security is managed by the VPN server. I would also add that if there are vulnerabilities I would be more confident of the ongoing security of OpenVPN (being a widely used enterprise technology) and exploits being patched than the exploits being found, patched etc in many of these applications we all use. Sent from my iPhone using Tapatalk

uh, no... Sorry. Post corrected.

I advise strongly against this if it is to be then exposed to the Internet. If it is on the LAN then it's fine. I guess there are use cases where HTTPS is required on your LAN too.

This product requires a bit tinkering. You could just load a linux VM and do a basic reverse proxy w/ SSL offloading to your storage server. Just another thought. Please don't expose you're unRAID GUI to the Internet. unRAID is not hardened for such a use. My view is that unRAID 6.1.9 would fail even a basic security audit. It has not been patched since its release. I would say that 6.2 RC4 is better but again it's not intended to be exposed to the Internet. Doing so will expose you to what I consider unacceptable risk. Those risks are mitigated (somewhat) by the advice to keep it securely behind a firewall and not exposing the system or its GUI to the Internet. A good source of information on the current state of unRAID security is here: http://lime-technology.com/forum/index.php?topic=50643.0 I personally do expose one of my unRAID Server's to the Internet for the purpose of facilitating a VPN connection and also serving a basic web site via the Docker platform which is running on unRAID. While it is not whiteout risk, I feel this risk is mitigated by the fact that both dockers I use for this are updated regularly (or in the case of Apache, daily) and as such I feel that security patches are applied in sufficient time to deal with known threats. That doesn't mean however that there isn't a risk. As NAS points out deep into the thread I posted above, the risk I am managing through doing this can be described as: The specific post in that above thread about doing what I do is here: http://lime-technology.com/forum/index.php?topic=50643.msg488115#msg488115 Down to the help. If you're happy to accept the risk of exposing applications (hosted on a VM or the Docker Platform) running on unRAID to the Internet then I have a solution for you. Before I do, it was previously noted that a reverse proxy could be used. While this is true I would advise against this for your unRAID GUI. Many people use this method for accessing other applications on their LAN (usually GUI's of other Docker containers). These applications often have their own security system built in (which may or may not be that hardened themselves) and often with the addition of .htaccess password protection this can be reasonably ok. It's important to note though that these applications often don't provide you access to the functionality that the unRAID GUI does though. For that reason I'd say stay away from reverse proxy for unRAID GUI access. In fact, I personally don't use reverse proxy for application access at all. I use a VPN connection. For completeness sake here is a link to the linuxserver.io apache docker container: https://lime-technology.com/forum/index.php?topic=43858.0 The following is an excellent guide we have posted on the website for setting up Apache to work as a reverse proxy: https://www.linuxserver.io/index.php/overview-reverse-proxy-with-docker/installation-of-apacheweb-docker/ However, I will recommend OpenVPN-AS. OpenVPN Access Server is a full featured secure network tunneling VPN software solution that integrates OpenVPN server capabilities, enterprise management capabilities, simplified OpenVPN Connect UI, and OpenVPN Client software packages that accommodate Windows, MAC, Linux, Android, and iOS environments. OpenVPN Access Server supports a wide range of configurations, including secure and granular remote access to internal network and/ or private cloud network resources and applications with fine-grained access control. https://openvpn.net/index.php/access-server/overview.html Over at linuxserver.io we have a docker container running this application that you can use. https://lime-technology.com/forum/index.php?topic=43317.0 The easiest way to install this (and other apps) is via the Community Applications plugin. Also a linuxserver.io creation. This plugin will allow you to easily search for and add any of the unRaid docker or plugin applications, along with some related optional utilities (automatic updates of plugins, backup of appdata shares) http://lime-technology.com/forum/index.php?topic=40262.0 The application as setup in the container almost works "straight out of the box". It's as simple as installing the container, configuring some basic options (well documented in the support thread), changing and creating a password, creating a port forward on your firewall and downloading the .ovpn profile file to your client. 15 mins of tinkering and you can connect to your LAN securely (noting what I have already said above) from a remote location as if you were local. That's how I would (and do) deal with your access issue. Sent from my iPhone using Tapatalk

Essentially I think this container is always going to be behind somewhat as Emby have a VERY regular release schedule. As containers go, I feel it gets maintained and updated very well. I keep an eye on this link: https://github.com/MediaBrowser/Emby/releases As long as there isn't something that critical in there (with respect to a recent release) - which I don't think there is (for me at least) at this time, I don't worry about it.

This post relates to SSD TRIM Plugin. I have just upgraded my Main Server from 6.1.9 to 6.2.0 RC3. This morning I received a notification of the following error: fstrim: /mnt/cache: the discard operation is not supported This never happened on 6.1.9 but also I'm appreciative of the fact that no-one else has reported this (based on a forum search of the error) but can't be the only person running this Plugin on 6.2.0 RC3. I've checked the Plugin and it is up to date. I'm running the cache in raid0 configuration: dconvert=raid1 -mconvert=raid1 The pool contains 3 SSD drives: CT250BX100SSD1_1514F00579EC - 250 GB (sdb) CT250BX100SSD1_1514F0057C13 - 250 GB (sdc) Samsung_SSD_850_EVO_250GB_S21MNXAGA24112P - 250 GB (sdi) Btrfs Pool: 750GB capacity - 47.5GB used - 703 GB free Can anyone help please!?

You haven't provided me with enough detail to be sure BUT it sounds to me like youre misunderstanding how docker works. The docker path config ice pube has provided is almost typical. However I would make one minor amendment: /config /mnt/cache/appdata/emby/ /movies /mnt/user/media/movies /tv /mnt/user/media/tv If you mirror this then the path you enter into Emby for mapping your directory is NOT /mnt/user/media/tv or /mnt/user/media/movies it is just /moves and /tv. If you want, think of them like shortcuts or symlinks! I hope this makes it clearer for you! Emby is awesome!

I am not familiar with your personal setup, so please excuse me if I am appearing ignorant, but I am struggling to see what the maintenance overhead would be. You don't have to regenerate the certificates yourself. You just direct the user to the OpenVPN Connect page. They log in with their userID and password (which you have generated with a few one liners on the command line) and they download their auto connect certificate for the device they are using. Click Click. Done.

No worries mate. My excuse is that its 8:18pm here and Ive had a wine or 2 Interesting observation though. Mine doesn't appear to have been updated either but interestingly I am on 2.0.20. I'll raise it with Sparkly. Haha, nice! I'm supposed to be enjoying a holiday, but just can't resist updating my dockers I do wonder if it's just OpenVPN-as reporting the version incorrectly for some reason I couldn't find a --version command anywhere inside the docker itself though, so it's just a theory atm Ive asked the question, I am sure Sparkly will look into it when he gets a minute. The very fact that you're reporting a different version to me though suggests that the old Container almost certainly did auto update (answer to a previous question in the thread). The new Alpine Container has certainly had the auto update feature removed BUT as you say, we are not showing 2.12. The common thing between us both is that we upgraded from the old Container - Ill test doing a completely fresh install with fresh appdata and see if that works. I deleted my app data config folder for this app and did a completely new install and the GUI is now reporting 2.12. I am not sure if this will end up being the formal advice but if you really MUST have the latest version now (assuming it wasn't the latest version before and the GUI was just not reporting it right) then doing what I suggest will work. Its not a huge drama really as it pretty much works out of the box and the setup and config is only 10 mins of your time. If you don't want to do this though, suggest wait for formal advice from Sparkly.

No worries mate. My excuse is that its 8:18pm here and Ive had a wine or 2 Interesting observation though. Mine doesn't appear to have been updated either but interestingly I am on 2.0.20. I'll raise it with Sparkly. Haha, nice! I'm supposed to be enjoying a holiday, but just can't resist updating my dockers I do wonder if it's just OpenVPN-as reporting the version incorrectly for some reason I couldn't find a --version command anywhere inside the docker itself though, so it's just a theory atm Ive asked the question, I am sure Sparkly will look into it when he gets a minute. The very fact that you're reporting a different version to me though suggests that the old Container almost certainly did auto update (answer to a previous question in the thread). The new Alpine Container has certainly had the auto update feature removed BUT as you say, we are not showing 2.12. The common thing between us both is that we upgraded from the old Container - Ill test doing a completely fresh install with fresh appdata and see if that works.

No worries mate. My excuse is that its 8:18pm here and Ive had a wine or 2 Interesting observation though. Mine doesn't appear to have been updated either but interestingly I am on 2.0.20. I'll raise it with Sparkly.

Hi sparkly! Unless I'm looking in the wrong place Access Server version: 2.0.24 I'm definitely on the xenial version, just based on the logs: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-time: executing... Current default time zone: 'Europe/London' Local time is now: Sat Aug 6 10:40:29 BST 2016. Universal Time is now: Sat Aug 6 09:40:29 UTC 2016. [cont-init.d] 20-time: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-openvpn-init: executing... [cont-init.d] 40-openvpn-init: exited 0. [cont-init.d] 50-interface: executing... MOD Default {} {} MOD Default {} {} MOD Default {} {} MOD Default {} {} [cont-init.d] 50-interface: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Any ideas? Have you updated the container? I thought I'd made that clear in my post? Yes, I updated it this morning, and restarted it about 5 mins ago to see if that made a difference too, it did not You were very quick off the mark with your reply. I realised that after I had posted and hit delete almost instantly but like I said, you were just too quick for me I have just forced my container to update with the following results: Everything is working fine. I have noticed that I have had to reset the admin password via this command: and recreate the users I had via this command: But once I did that, everything is working fine. Note, that the auto update "feature" has been removed.

Brad just let me onto this app and I have to say it looks fantastic. I am certainly a big +1 for iOS support as I do not use android and have reflected as such on your feedback Forum. I did notice that you mention your focus is Android as there is already an iOS app? That there may be, but yours seems to be head light years ahead! I would certainly pay for your app for iOS. Congratulations on a great development!

For those who are lazy and don't want to go looking, drop to the command line on your server either on console, telnet or ssh and do the following: Then follow on screen prompts.

I had an issue recently which saw that folders could not be created. I then checked and for some reason the group:owner of the destination folder had changed to root:root so the service did not have the permissions to do anything with that folder, creating files or otherwise meaning that downloads remained in the incomplete folder indefinitely. ls - all The above command confirmed this for me. So I changed the owner and the permissions of the destination folder (recursive) and all started working again: chown -R owner-user:owner-group directory Example: chown -R nobody:users /directory chown -R ### /directory Example: chmod -R 777 /directory I think I have the commands correct. Hope it words for you.

Have you experienced any issues or are you just preparing for possible issues? I have upgraded to latest version and everything seems to be running just fine.

i was under the impression this container auto-updated on restart.... I believe it does, meaning a restart of the container should unless the repo it grabs from is not up to date. I just did a reset to test and low and behold just like all the other linuxserver.io containers it seemed to grab packages from the repo before it started.