Jump to content

InfInIty

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About InfInIty

  • Rank
    Member
  1. InfInIty

    [Support] Linuxserver.io - Nextcloud

    Also it appears I am still having the same issues with IOS photo sync. Photos appear to sync just fine, but video files through a 413 error. I have went in and changed the client_max_body_size to 4096M, but still get the error. Is there anyone else who has had these issues?
  2. InfInIty

    [Support] Linuxserver.io - Nextcloud

    Well other than the not being able to add apps, it seems nextcloud is working. Its just the app thing. I do need to try photo uploads from IOS as that is what I had issues with before.
  3. InfInIty

    [Support] Linuxserver.io - Nextcloud

    I can look into side loading apps, but I would really prefer to get this working properly. Mine is in a docker container, pointing to a MariaDB docker, all behind a Letsencrypt reverse proxy docker.
  4. InfInIty

    [Support] Linuxserver.io - Nextcloud

    Anyone, I would really like to get this up and running.
  5. InfInIty

    [Support] Linuxserver.io - Nextcloud

    So I have nextcloud setup behind letsencyrpt reverse proxy per Space Invaders Video. I can get into nextcloud and all that, but it seems I am unable to add any applications. I just get a spinning wheel in the left pain under developer documentation. Any ideas? I would like to get this fully functional to start using it to sync photos and such with my phone and not use any other "cloud" storage options.
  6. InfInIty

    FileBot containers

    Is there a way to force filebot to run on this docker from its command line. I have some files that are not getting processed and want to run it manually. I do not have the GUI enabled
  7. InfInIty

    Docker Network Issue

    So i followed Space Invaders guide on setting up the letsencrypt reverse proxy I got it up and running with several services without issue Now when i start trying to move deluge into the proxynet network from host network, it does not display the port mappings on docker homepage. I am able to ping the deluge container from the letsencyrpt container via name, and it returns an IP in the proxynet network scheme I am unable to access the webui at all after i make this change Really not sure what is causing this. I have turned docker on and off, and rebooted the system, still get this issue. Anyone else run into this. I suspect its an issue with docker networking, but maybe not Any help would be greatly appreciated. I am happy to provide logs or whatever is needed to help get this resolved.
  8. InfInIty

    Creating Dockers for Unraid

    I want to develop my own docker, i have dabbled with this in a standard Linux environment, but how would i go about developing one specifically for unraid. If someone could point me in the right direction on this. Maybe just an overview of how its done im sure I can figure the rest out. I would like for it to one day be a community app that anyone could quickly install. Thanks for any help in advance.
  9. InfInIty

    FileBot containers

    Anyone? @coppit
  10. InfInIty

    New Config Question

    Hello everyone. I have 2 8tb drives, currently both part of the array, and I have encryption on the drives I want to move one out to be a parity drive. When i bought the second drive it was not "bigger" than the first so it would not allow me to make it a parity drive I have moved all the data onto the "smaller" drive. According to some post it looks like i need to use the new config tool to make these changes. My concern is will it break my encryption when i do this, or shoudl everything work fine as long as i have the key.
  11. InfInIty

    FileBot containers

    I am having an issue, seems to be specific to movies so far, where filebot is processing but only spitting out part of it. For example a 66gb UHD movie, is getting put into my media folder at 6GB Not sure how this is happening. My work flow is like this. deluge downloads to "incomplete" folder -> on completion moves the file to "completed folder" -> filebot docker is processing out of that folder and putting it in the plex library folder. The incomplete and completed folder are on the same disk and moves are instantanious, at least when i do it manually between them via file explorer. Any ideas?
  12. InfInIty

    [Support] Linuxserver.io - OpenVPN-AS

    So i pulled this docker but cannot get into the WEBUI for it. here is the log [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 gratefully 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: 'America/Chicago' Local time is now: Tue Apr 24 16:51:18 CDT 2018. Universal Time is now: Tue Apr 24 21:51:18 UTC 2018. [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... Detected an existing OpenVPN-AS configuration. Continuing will delete this configuration and restart from scratch. Please enter 'DELETE' to delete existing configuration: OpenVPN Access Server Initial Configuration Tool ------------------------------------------------------ OpenVPN Access Server End User License Agreement (OpenVPN-AS EULA) 1. Copyright Notice: OpenVPN Access Server License; Copyright (c) 2009-2017 OpenVPN, Inc.. All rights reserved. "OpenVPN" is a trademark of OpenVPN, Inc. 2. Redistribution of OpenVPN Access Server binary forms and related documents, are permitted provided that redistributions of OpenVPN Access Server binary forms and related documents reproduce the above copyright notice as well as a complete copy of this EULA. 3. You agree not to reverse engineer, decompile, disassemble, modify, translate, make any attempt to discover the source code of this software, or create derivative works from this software. 4. The OpenVPN Access Server is bundled with other open source software components, some of which fall under different licenses. By using OpenVPN or any of the bundled components, you agree to be bound by the conditions of the license for each respective component. For more information, you can find our complete EULA (End-User License Agreement) on our website (http://openvpn.net), and a copy of the EULA is also distributed with the Access Server in the file /usr/local/openvpn_as/license.txt. 5. This software is provided "as is" and any expressed or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall OpenVPN Inc. be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. 6. OpenVPN Inc. is the sole distributor of OpenVPN Access Server licenses. This agreement and licenses granted by it may not be assigned, sublicensed, or otherwise transferred by licensee without prior written consent of OpenVPN Inc. Any licenses violating this provision will be subject to revocation and deactivation, and will not be eligible for refunds. 7. A purchased license entitles you to use this software for the duration of time denoted on your license key on any one (1) particular device, up to the concurrent user limit specified by your license. Multiple license keys may be activated to achieve a desired concurrency limit on this given device. Unless otherwise prearranged with OpenVPN Inc., concurrency counts on license keys are not to be divided for use amongst multiple devices. Upon activation of the first purchased license key in this software, you agree to forego any free licenses or keys that were given to you for demonstration purposes, and as such, the free licenses will not appear after the activation of a purchased key. You are responsible for the timely activation of these licenses on your desired server of choice. Refunds on purchased license keys are only possible within 30 days of purchase of license key, and then only if the license key has not already been activated on a system. To request a refund, contact us through our support ticket system using the account you have used to purchase the license key. Exceptions to this policy may be given for machines under failover mode, and when the feature is used as directed in the OpenVPN Access Server user manual. In these circumstances, a user is granted one (1) license key (per original license key) for use solely on failover purposes free of charge. Other failover and/or load balancing use cases will not be eligible for this exception, and a separate license key would have to be acquired to satisfy the licensing requirements. To request a license exception, please file a support ticket in the OpenVPN Access Server ticketing system. A staff member will be responsible for determining exception eligibility, and we reserve the right to decline any requests not meeting our eligibility criteria, or requests which we believe may be fraudulent in nature. 8. Activating a license key ties it to the specific hardware/software combination that it was activated on, and activated license keys are nontransferable. Substantial software and/or hardware changes may invalidate an activated license. In case of substantial software and/or hardware changes, caused by for example, but not limited to failure and subsequent repair or alterations of (virtualized) hardware/software, our software product will automatically attempt to contact our online licensing systems to renegotiate the licensing state. On any given license key, you are limited to three (3) automatic renegotiations within the license key lifetime. After these renegotiations are exhausted, the license key is considered invalid, and the activation state will be locked to the last valid system configuration it was activated on. OpenVPN Inc.reserves the right to grant exceptions to this policy for license holders under extenuating circumstances, and such exceptions can be requested through a ticket via the OpenVPN Access Server ticketing system. 9. Once an activated license key expires or becomes invalid, the concurrency limit on our software product will decrease by the amount of concurrent connections previously granted by the license key. If all of your purchased license key(s) have expired, the product will revert to demonstration mode, which allows a maximum of two (2) concurrent users to be connected to your server. Prior to your license expiration date(s), OpenVPN Inc. will attempt to remind you to renew your license(s) by sending periodic email messages to the licensee email address on record. You are solely responsible for the timely renewal of your license key(s) prior to their expiration if continued operation is expected after the license expiration date(s). OpenVPN, Inc. will not be responsible for any misdirected and/or undeliverable email messages, nor does it have an obligation to contact you regarding your expiring license keys. 10. Any valid license key holder is entitled to use our ticketing system for support questions or issues specifically related to the OpenVPN Access Server product. To file a ticket, go to our website at http://openvpn.net/ and sign in using the account that was registered and used to purchase the license key(s). You can then access the support ticket system through our website and submit a support ticket. Tickets filed in the ticketing system are answered on a best-effort basis. OpenVPN Inc. staff reserve the right to limit responses to users of our demo / expired licenses, as well as requests that substantively deviate from the OpenVPN Access Server product line. Tickets related to the open source version of OpenVPN will not be handled here. 11. Purchasing a license key does not entitle you to any special rights or privileges, except the ones explicitly outlined in this user agreement. Unless otherwise arranged prior to your purchase with OpenVPN, Inc., software maintenance costs and terms are subject to change after your initial purchase without notice. In case of price decreases or special promotions, OpenVPN, Inc. will not retrospectively apply credits or price adjustments toward any licenses that have already been issued. Furthermore, no discounts will be given for license maintenance renewals unless this is specified in your contract with OpenVPN Inc. Please enter 'yes' to indicate your agreement [no]: Once you provide a few initial configuration settings, OpenVPN Access Server can be configured by accessing its Admin Web UI using your Web browser. Will this be the primary Access Server node? (enter 'no' to configure as a backup or standby node) > Press ENTER for default [yes]: Please specify the network interface and IP address to be used by the Admin Web UI: (1) all interfaces: 0.0.0.0 (2) br0: 192.168.1.10 (3) virbr0: 192.168.122.1 (4) docker0: 172.17.0.1 (5) bond0: 192.168.1.10 (6) virbr0-nic: 192.168.122.1 Please enter the option number from the list above (1-6). > Press Enter for default [2]: Please specify the port number for the Admin Web UI. > Press ENTER for default [943]: Please specify the TCP port number for the OpenVPN Daemon > Press ENTER for default [443]: Should client traffic be routed by default through the VPN? > Press ENTER for default [yes]: Should client DNS traffic be routed by default through the VPN? > Press ENTER for default [yes]: Use local authentication via internal DB? > Press ENTER for default [yes]: Private subnets detected: ['192.168.1.0/24', '192.168.122.0/24', '172.17.0.0/16'] Should private subnets be accessible to clients by default? > Press ENTER for default [yes]: To initially login to the Admin Web UI, you must use a username and password that successfully authenticates you with the host UNIX system (you can later modify the settings so that RADIUS or LDAP is used for authentication instead). You can login to the Admin Web UI as "openvpn" or specify a different user account to use for this purpose. Do you wish to login to the Admin UI as "openvpn"? > Press ENTER for default [yes]: > Specify the username for an existing user or for the new user account: Note: This user already exists. > Please specify your OpenVPN-AS license key (or leave blank to specify later): Initializing OpenVPN... Adding new user login... useradd -s /sbin/nologin "admin" Writing as configuration file... Perform sa init... Wiping any previous userdb... Creating default profile... Modifying default profile... Adding new user to userdb... Modifying new user as superuser in userdb... Getting hostname... Hostname: TaylorUnraid Preparing web certificates... Getting web user account... Adding web group account... Adding web group... Adjusting license directory ownership... Initializing confdb... Generating init scripts... Generating PAM config... Generating init scripts auto command... Starting openvpnas... Error: Could not execute server start. [cont-init.d] 40-openvpn-init: exited 0. [cont-init.d] 50-interface: executing... MOD Default {u'admin_ui.https.ip_address': u'all'} {u'admin_ui.https.ip_address': 'eth0'} MOD Default {u'cs.https.ip_address': u'all'} {u'cs.https.ip_address': 'eth0'} MOD Default {u'vpn.daemon.0.listen.ip_address': u'all'} {u'vpn.daemon.0.listen.ip_address': 'eth0'} MOD Default {u'vpn.daemon.0.server.ip_address': u'all'} {u'vpn.daemon.0.server.ip_address': 'eth0'} [cont-init.d] 50-interface: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done.
  13. InfInIty

    Undo LetsEncrypt

    Anyone? This surely has to be possible
  14. InfInIty

    Undo LetsEncrypt

    So I setup the lets encrypt options in unraid 6.5.0. I would like to undo this and change everything back to the default way of accessing unraid. I want to undo this so i can switch to using organizr so i can have a single landing page to manage everything with unraid and all my dockers on it.
  15. InfInIty

    FileBot containers

    My apologies if I missed my answer somwhere in this post. I want to set this container up to run headless and run the AMC script. It can watch the input folder, run the amc script to the output folder. I loaded this through the community apps plugin, and unfortunatly cannot get to the GUI, all though its really not needed if the way i want to run this is possible. Anyone with some tips on how to get this setup like that would be greatly appreciated.