aptalca
-
Posts
3,064 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by aptalca
-
-
No issues in the log. Are you sure it is listening on the correct interface? What address did you try to access?I have used this openvpn docker for a while but recently when i installed on a new machine and i can not access the web ui
here is the 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.ioWe gratefully accept donations at:https://www.linuxserver.io/donations/-------------------------------------GID/UID-------------------------------------User uid: 99User gid: 100-------------------------------------[cont-init.d] 10-adduser: exited 0.[cont-init.d] 20-time: executing...Current default time zone: 'America/Los_Angeles'Local time is now: Mon Aug 28 19:15:04 PDT 2017.Universal Time is now: Tue Aug 29 02:15:04 UTC 2017.[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 ServerInitial Configuration Tool------------------------------------------------------OpenVPN Access Server End User License Agreement (OpenVPN-AS EULA)1. Copyright Notice: OpenVPN Access Server License;Copyright (c) 2009-2013 OpenVPN Technologies, Inc.. All rights reserved."OpenVPN" is a trademark of OpenVPN Technologies, Inc.2. Redistribution of OpenVPN Access Server binary forms and related documents,are permitted provided that redistributions of OpenVPN Access Server binaryforms and related documents reproduce the above copyright notice as well asa 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 softwarecomponents, some of which fall under different licenses. By using OpenVPNor any of the bundled components, you agree to be bound by the conditionsof the license for each respective component. For more information, you canfind our complete EULA (End-User License Agreement) on our website(http://openvpn.net), and a copy of the EULA is also distributed with theAccess 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 merchantabilityand fitness for a particular purpose are disclaimed. In no event shallOpenVPN Technologies, Inc. be liable for any direct, indirect, incidental,special, exemplary, or consequential damages (including, but not limitedto, procurement of substitute goods or services; loss of use, data, orprofits; or business interruption) however caused and on any theory ofliability, whether in contract, strict liability, or tort (includingnegligence or otherwise) arising in any way out of the use of thissoftware, even if advised of the possibility of such damage.6. OpenVPN Technologies, Inc. is the sole distributor of OpenVPN Access Serverlicenses. This agreement and licenses granted by it may not be assigned,sublicensed, or otherwise transferred by licensee without prior writtenconsent of OpenVPN Technologies Inc. Any licenses violating this provisionwill be subject to revocation and deactivation, and will not be eligiblefor refunds.7. A purchased license entitles you to use this software for the duration oftime denoted on your license key on any one (1) particular device, up tothe concurrent user limit specified by your license. Multiple license keysmay be activated to achieve a desired concurrency limit on this givendevice. Unless otherwise prearranged with OpenVPN Technologies, Inc.,concurrency counts on license keys are not to be divided for use amongstmultiple devices. Upon activation of the first purchased license key inthis software, you agree to forego any free licenses or keys that weregiven to you for demonstration purposes, and as such, the free licenseswill not appear after the activation of a purchased key. You areresponsible for the timely activation of these licenses on your desiredserver of choice. Refunds on purchased license keys are only possiblewithin 30 days of purchase of license key, and then only if the license keyhas not already been activated on a system. To request a refund, contact usthrough our support ticket system using the account you have used topurchase the license key. Exceptions to this policy may be given formachines under failover mode, and when the feature is used as directed inthe OpenVPN Access Server user manual. In these circumstances, a user isgranted one (1) license key (per original license key) for use solely onfailover purposes free of charge. Other failover and/or load balancing usecases will not be eligible for this exception, and a separate license keywould have to be acquired to satisfy the licensing requirements. To requesta license exception, please file a support ticket in the OpenVPN AccessServer ticketing system. A staff member will be responsible for determiningexception eligibility, and we reserve the right to decline any requests notmeeting our eligibility criteria, or requests which we believe may befraudulent in nature.8. Activating a license key ties it to the specific hardware/softwarecombination that it was activated on, and activated license keys arenontransferable. Substantial software and/or hardware changes mayinvalidate an activated license. In case of substantial software and/orhardware changes, caused by for example, but not limited to failure andsubsequent repair or alterations of (virtualized) hardware/software, oursoftware product will automatically attempt to contact our online licensingsystems to renegotiate the licensing state. On any given license key, youare limited to three (3) automatic renegotiations within the license keylifetime. After these renegotiations are exhausted, the license key isconsidered invalid, and the activation state will be locked to the lastvalid system configuration it was activated on. OpenVPN Technologies, Inc.reserves the right to grant exceptions to this policy for license holdersunder extenuating circumstances, and such exceptions can be requestedthrough a ticket via the OpenVPN Access Server ticketing system.9. Once an activated license key expires or becomes invalid, the concurrencylimit on our software product will decrease by the amount of concurrentconnections previously granted by the license key. If all of your purchasedlicense key(s) have expired, the product will revert to demonstration mode,which allows a maximum of two (2) concurrent users to be connected to yourserver. Prior to your license expiration date(s), OpenVPN Technologies,Inc. will attempt to remind you to renew your license(s) by sendingperiodic email messages to the licensee email address on record. You aresolely responsible for the timely renewal of your license key(s) prior totheir expiration if continued operation is expected after the licenseexpiration date(s). OpenVPN Technologies, Inc. will not be responsible forany misdirected and/or undeliverable email messages, nor does it have anobligation to contact you regarding your expiring license keys.10. Any valid license key holder is entitled to use our ticketing system forsupport questions or issues specifically related to the OpenVPN AccessServer 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 thelicense key(s). You can then access the support ticket system through ourwebsite and submit a support ticket. Tickets filed in the ticketing systemare answered on a best-effort basis. OpenVPN Technologies, Inc. staffreserve the right to limit responses to users of our demo / expiredlicenses, as well as requests that substantively deviate from the OpenVPNAccess Server product line. Tickets related to the open source version ofOpenVPN will not be handled here.11. Purchasing a license key does not entitle you to any special rights orprivileges, except the ones explicitly outlined in this user agreement.Unless otherwise arranged prior to your purchase with OpenVPN Technologies,Inc., software maintenance costs and terms are subject to change after yourinitial purchase without notice. In case of price decreases or specialpromotions, OpenVPN Technologies, Inc. will not retrospectively applycredits or price adjustments toward any licenses that have already beenissued. Furthermore, no discounts will be given for license maintenancerenewals unless this is specified in your contract with OpenVPNTechnologies, Inc.Please enter 'yes' to indicate your agreement [no]:Once you provide a few initial configuration settings,OpenVPN Access Server can be configured by accessingits 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 beused by the Admin Web UI:(1) all interfaces: 0.0.0.0(2) br0: 192.168.0.3(3) docker0: 172.17.0.1(4) virbr0: 192.168.122.1(5) bond0: 192.168.0.3(6) virbr0-nic: 192.168.122.1Please 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 [no]:Private subnets detected: ['192.168.0.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 ausername and password that successfully authenticates youwith the host UNIX system (you can later modify the settingsso that RADIUS or LDAP is used for authentication instead).You can login to the Admin Web UI as "openvpn" or specifya 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: UNDyllanPreparing 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. -
Openvpn and openvpn-as are separate products. The first is the actual platform and the backend, and is open source. The second is a frontend server based on the first, but is not open source and is a commercial product.I can't find a public repo for openvpn-as & it seems they use a trac instance on their site instead of github for issues so I logged a support ticket. -
The certs weren't generated properly (could be a port forwarding or a dns issue) them you tried it too many times unsuccessfully and now letsencrypt servers are throttling you.Hello All!New to the community but not new to unRAID. I am currently trying to setup Letsencrypt and keep running into this error every time it goes thru. Its seems as though the folders are not getting created. Here is what I receive just before the docker shuts down:
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
generating self-signed keys in /config/keys, you can replace these with your own keys if required
Generating a 2048 bit RSA private key
...........+++
.....................+++
writing new private key to '/config/keys/cert.key'
-----
Subject Attribute /C has no known NID, skipped
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing...
Creating DH parameters for additional security. This may take a very long time. There will be another message once this process is completed
Generating DH parameters, 2048 bit long safe prime, generator 2
This is going to take a long time
DH parameters successfully created - 2048 bits
SUBDOMAINS entered, processing
Only subdomains, no URL in cert
Sub-domains processed are: -d ***********.ddns.net
E-mail address entered: ******.*******@outlook.com
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
An unexpected error occurred:
There were too many requests of a given type :: Error creating new registration :: too many registrations for this IP
Please see the logfiles in /var/log/letsencrypt for more details.
/var/run/s6/etc/cont-init.d/50-config: line 127: cd: /config/keys/letsencrypt: No such file or directory
[cont-init.d] 50-config: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.When I attempt to go look at the log files listed as /var/log/letsencrypt/letsencrypt.log, the /var/log/letsencrypt folder does not seem to exist......
Try putting in your custom domain (including your custom subdomain) as the url, and enter a subdomain like www, don't set only subdomains to true. Sometimes when you change the subdomains around you can get around the throttling issue.
You still have to fix the dns or port issue.
If that doesn't work, you'll have to wait until letsencrypt accepts requests from you again
-
Try copying a 25gb file from a btrfs drive (or pool) to the same drive. That's when I had issues. Also during unrar and repair where there is simultaneous read and write operations on the same disk.I'm not saying btrfs doesn't have something to do with this issue, but very much doubt it's only that, I never had this problem and I use btrfs in all my servers, for array disks and cache, both single and at some point an 8 device raid10 pool, never noticed this problem, just now did a test that with:
-mover running (25GB from cache to the array)
-manual copy on the console using cp of another 25GB from cache to array
-copying another 25GB over lan from my desktop to cache disk
load average peaked at about 4, this on a dual core pentium G620 and the webGUI was normally usable during all the operations.
-
What I did wasI am having a similar issue with my cache drive which is btrfs as well. Simple things like copying a file over the network into the cache drive kill my docker container speeds loads shoot up into 12.00 and ssh is very slow even doing Ls commands.
if mover ever runs while copying well dockers start crashing.
how do you covert the cache from btrfs to xfs that sounds like it improved things. Can we still mirror without btrfs. I was looking at picking up a second ssd.
1) mount a second ssd through unassigned devices plugin,
2) shut down all Dockers and VMs (turn off the services in the settings so they don't automatically restart when the array starts),
3) rsync all data from cache to unassigned device (rsync preserves permissions, timestamps, etc. with the option "a"),
4) stop the array,
5) change the disk format from btrfs to xfs and
6) restart the array.
It will format the cache drive, which takes about a minute. Then you can transfer your data back to the cache drive and enable the docker and VM services
If you don't have a spare ssd, you can rsync to an array disk as well. Make sure you use a disk share and not a user share for that (ie. /mnt/diskX)-
1
-
-
Another update.
After switching to a single btrfs cache drive, I continued to have minor issues.
Sonarr and Radarr still logged "database locked" error messages (sqlite errors), likely due to high disk io during unrar and repairs, although these were much shorter lived compared to btrfs cache pool and they did not cause any issues apart from log messages.
Then I converted the drive to xfs and have not had any error messages logged.
I am convinced that the disk io is due to btrfs. The issues are much worse in a raid 0 config compared to a single btrfs drive
-
1
-
-
This sucks because the client to client backup was super useful.
I'll look into duplicati -
Not 60 days, over a year. Oct 2018Business is limited to 5TB though. Useless for me. I almost feel like asking for a full refund from the beginning. What's the point of a cloud backup service if they are just going to wipe it randomly with 60 days notice. -
Please read my message three messages above yours.I believe you are refering to these steps, to be exact:
https://github.com/linuxserver/docker-openvpnas#setting-up-the-application
What I did/try to do:
Under Authentication > General change from Local to PAM, and back from PAM to Local again. (It was already on Local for some reason)
Then deleted user(s) in de webgui. (And SSH, userdel)
Then continued to add users under SSH and then add then in the webgui.
I am un able to remove the admin user in the webgui. (As the steps on GitHub mention)
So I deleted the admin user via SSH, userdel. (not webgui...)
Modified the "as.conf" under "/appdata/openvpn-as/etc" and commeted the "boot_pam_users.0=admin" line by putting a hashtag in front of it.
But, as you probably guessed by now, I am still unable to log in with my newly created user(s). (Login failed, both Login and Connect)
I am using Linuxserver's OpenVPN-as, but there seem to be differences, even in the GitHub guide, or is it just me?
Any more info I can provide to help solve this issue? [emoji4]
No need to add users through ssh. No need to delete the admin user. No need to do anything through ssh anymore.
Follow the directions on docker hub or github. It really is super simple to set up. You guys are way over-complicating it.
With regards to switching authentication to pam and back to local, you don't need to do that either. With the latest update, new installs default to local authentication. If you update an older install, it may have been set to pam, in that case, change it to local. If it's already local, you're good to go. -
No need to delete the admin user. It will come back when you update the container anyway. Just follow the steps in the readme to disallow the admin user logging in.Yeah. Already had authentication set to local so that wasn't any problem.
The only issue I had at all was deleting the user "admin" after I configured a new user with admin privileges. Did you know that if you log in as user "admin" you can't delete that user in the GUI.[emoji5]
Once I figured out that I needed to login as the new user the rest was a piece of cake.
Ran the docker update last night and then tested logging in as default admin user, which failed (as desired). Looks good.
The admin user is required for the first time login, that's why the container always creates it. But once the user sets up another account with admin privileges and disables admin user login in the config, admin will just be a useless account that doesn't do anything (and doesn't hurt anything).
If you want to tighten up security, you can create two user accounts, one an admin, specifically for management purposes, and another for users to login with. Only share the certificate for the second user account with your users. Or, you can create many user accounts, one for each real life user (or per device) so you can disable access for a specific individual if needed.
I'm the only vpn user for my server so I use the same certificate on all of my devices. The downside is, if a device is lost or stolen, I would have to generate a new cert and update it on all the other devices. -
The instructions in the readme will apply to existing users.I'm probably jumping the gun with this question, but what will I need to do to add this to my existing docker when it's merged? I see it's already been approved.
Edit: I see the readme changes. That looks simple enough, just not sure how to get the modifications to /root/etc/cont-init.d/40-openvpn-init or if I even need to?
The most important thing is to make sure that authentication is set to local before the other users are created.
In a nutshell, pam users don't survive container updates or reinstalls, and the admin user (a pam user) gets reset.
Local users survive updates and the admin user access (a pam user) can be deactivated in the config file once another local user is given admin privileges -
There is a pr that will provide instructions on how to fix the password resetting issue. It is currently under review and should be merged soon
OK, thanks. Is there any chance to prevent the password resetting? -
Url should be the top domain that you have control over, ie. test.duckdns.org
Hmm, seems like a problem with duckdns. Using the example test.duckdns.org, when setting up duckdns with letsencrypt the Domain name is (duckdns.org) and the Subdomains are (test). Adding tor to the subdomains will give me an error with letsencrypt logs.Domain: tor.duckdns.orgType: ConnectionDetail: Timeout
I've tried adding in my subdomains (test,test.tor) but it didn't work either. I might need to go into the duckdns website and create a subdomain through there and it should work.
Then the subdomains would be tor and whatever else you like -
Duckdns automatically forwards all sub-subdomains to your ip as well. Just set it up with le so that your cert covers it
-
Assuming the ip is correct, your router seems to be not forwarding the request on port 443 to the container properly
Brought to you by linuxserver.ioWe gratefully accept donations at:https://www.linuxserver.io/donations/-------------------------------------GID/UID-------------------------------------User uid: 99User gid: 100-------------------------------------[cont-init.d] 10-adduser: exited 0.[cont-init.d] 20-config: executing...[cont-init.d] 20-config: exited 0.[cont-init.d] 30-keygen: executing...using keys found in /config/keys[cont-init.d] 30-keygen: exited 0.[cont-init.d] 50-config: executing...2048 bit DH parameters presentSUBDOMAINS entered, processingSub-domains processed are: -d sub1.domain.com -d sub2.domain.comE-mail address entered: Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be createdusage:certbot [sUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,it will attempt to use a webserver both for obtaining and installing thecert.certbot: error: argument --cert-path: No such file or directoryGenerating new certificateSaving debug log to /var/log/letsencrypt/letsencrypt.logObtaining a new certificatePerforming the following challenges:tls-sni-01 challenge for domain.comtls-sni-01 challenge for sub1.domain.comtls-sni-01 challenge for sub2.domain.comWaiting for verification...Performing the following challenges:tls-sni-01 challenge for domain.comtls-sni-01 challenge for sub1.domain.comtls-sni-01 challenge for sub2.domain.comWaiting for verification...Cleaning up challengesFailed authorization procedure. sub1.domain.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Connection refused, sub2.domain.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Connection refusedIMPORTANT NOTES:- The following errors were reported by the server:Domain: sub1.domain.comType: connectionDetail: Connection refusedDomain: sub2.domain.comType: connectionDetail: Connection refusedTo fix these errors, please make sure that your domain name wasentered correctly and the DNS A record(s) for that domaincontain(s) the right IP address. Additionally, please check thatyour computer has a publicly routable IP address and that nofirewalls are preventing the server from communicating with theclient. If you're using the webroot plugin, you should also verifythat you are serving files from the webroot path you provided.- Your account credentials have been saved in your Certbotconfiguration directory at /etc/letsencrypt. You should make asecure backup of this folder now. This configuration directory willalso contain certificates and private keys obtained by Certbot somaking regular backups of this folder is ideal./var/run/s6/etc/cont-init.d/50-config: line 127: cd: /config/keys/letsencrypt: No such file or directory[cont-init.d] 50-config: exited 1.[cont-finish.d] executing container finish scripts...[cont-finish.d] done.[s6-finish] syncing disks.[s6-finish] sending all processes the TERM signal.[s6-finish] sending all processes the KILL signal and exiting.
-
So sqlite may be the culprit?
-
@aptalca this is what I get, still not working. And why does it say Feb 19?? I also attached the Webtools log
drwxrwxrwx 1 nobody users 60 Jul 31 10:51 ./
drwxrwxrwx 1 nobody users 232 Jul 31 18:49 ../
drwxrwxrwx 1 nobody users 16 Jul 27 02:50 Services.bundle/
drwxrwxrwx 1 nobody users 76 Feb 19 17:00 WebTools.bundle/
Webtools log.zip
I'm not sure, according to the log, it seems to start. Did you try going to http://unraidip:33400?
If it's still not working, perhaps you can ask in their plex thread -
That is not correct. Do not move plex installation files or you'll likely break it and will have to set it up from scratch.Thanks for your help [mention=1392]Hogwind[/mention] [mention=1728]squirrellydw[/mention], perhaps my solve below may help your situation.TLDR: linuxserver's Unraid Docker default location within /mnt/user/appdata/ was listed as "plex" and not "Plex Media Server".
I was using the Plex docker from linuxserver's repository ("linuxserver/plex").
The default template under "Advanced" sets the root for Plex as /mnt/user/appdata/plex while Plex - or its plug ins - prefers to keep everything in /mnt/user/appdata/Plex Media Server.
I copied everything that was in /mnt/user/appdata/plex into /mnt/user/appdata/Plex Media Server and edited the docker config to point to the new directory.
I could then see WebTools, but it would not launch.
I reinstalled the docker under the new root /mnt/user/appdata/Plex Media Server and now everything works!
The unfortunate side effect was that I had to re-setup Plex like it was brand new.
Hope this helps!
Plex doesn't care or know about the root folder. We mount that folder as "/config" inside the container so all plex knows is that it's files are under /config. Whether it is /mnt/cache/appdata/blah or just /blah on your host does not make a difference to plex.
Plus, your post is confusing because there is another folder called "Plex Media Server" under plex's internal structure (under /config/Library) and if someone moves that folder, they will surely break it.
Leave the mount points as is. If plex is working, there is nothing wrong with them. Set the owner of the plugin files directly and restart plex. That's all that is needed.
PS. The container only checks the top folder's permissions/owner on container start, and fixes them only if that folder's is wrong. So if you add files downstream with wrong permissions, the container won't fix it. In your case, my guess is that when you moved the whole plex folder, you likely changed the entire folder's permissions/owner and the container fixed it, also fixing the webtools permissions/owner.
-
The first couple backups will have to copy everything, but once a backup is slated to be deleted due to its age, then it will wind up getting updated with changed files instead.
That is brilliant -
3 hours ago, SelfSD said:
I'm suddenly no longer able to access the web interface for PlexPy and the log is spitting out this error over and over again every few seconds:
Unable to create the log directory. Logging to screen only. Traceback (most recent call last): File "/app/plexpy/PlexPy.py", line 260, in <module> main() File "/app/plexpy/PlexPy.py", line 186, in main plexpy.initialize(config_file) File "/app/plexpy/plexpy/__init__.py", line 129, in initialize verbose=VERBOSE) File "/app/plexpy/plexpy/logger.py", line 205, in initLogger file_handler = handlers.RotatingFileHandler(filename, maxBytes=MAX_SIZE, backupCount=MAX_FILES) File "/usr/lib/python2.7/logging/handlers.py", line 117, in __init__ BaseRotatingHandler.__init__(self, filename, mode, encoding, delay) File "/usr/lib/python2.7/logging/handlers.py", line 64, in __init__ logging.FileHandler.__init__(self, filename, mode, encoding, delay) File "/usr/lib/python2.7/logging/__init__.py", line 913, in __init__ StreamHandler.__init__(self, self._open()) File "/usr/lib/python2.7/logging/__init__.py", line 943, in _open stream = open(self.baseFilename, self.mode) IOError: [Errno 2] No such file or directory: '/var/run/s6/services/plexpy/None/plexpy.log'
I've removed and reinstalled the docker and it didn't change anything.
I'm not getting this error, but can you check the file "config.ini" in your config folder and see what the parameter "log_dir" is set to?
That's a gui setting and by default it should be "/config/logs". If different, set it to that and restart
-
1
-
-
Yup.@aptalca So I would go to /mnt/cache/appdata/Plex Media Server/Plug-ins
and type in chown -R nobody:users WebTools.bundle
then how can i verify the permissions were changed?
"ls -al" will list permissions and owner info -
Check the permissions of the other folders in that location and match itThats what I did and it's not working. I think it might be a permission thing. Any idea what my permissions should be for the Plug-ins folder for Plex and what I need to to do to verify/change them? This is the path to my plug-ins folder on my cache drive "/appdata/Plex Media Server/Plug-ins" Also attached are the logs from the web tools plugin.If you do "chown -R nobody:users webtoolsfoldername" it should take care of it
-
I actually have done that and according to every cert checking website, the domain hamza219421.duckdns.org has a fully verified SSL certificate. Problem is, when I try to VPN into the server though, I still don't get the green lock despite the certificate being verified by every website I check.
I don't quite understand where you expect to see the padlock icon in vpn.
Your server is set up at the address: https://hamza219421.duckdns.org
That is the address the cert checking websites are checking. That has nothing to do with vpn. Just go to that address in your browser while you're away from home and you'll see your website and the green padlock. If you want to access other services through that address, you'll have to set them up through reverse proxy. There is plenty of info on that in this thread. -
It was supposed to auto update to the latest version. I'll look into itHello Aptalca and thank you very much for your work.
Just wondering if you had any plans to update the Digikam Docker? I've been using your 4.9 version but the latest 5.6 version seems really good and would love to run it on my server.
Thank you again
[Support] Linuxserver.io - OpenVPN AS
in Docker Containers
Posted