Jump to content

MrMoosieMan

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

2 Neutral

About MrMoosieMan

  • Rank
    Advanced Member

Recent Profile Visitors

425 profile views
  1. Two questions: 1) Any idea why am I getting this error when trying to install? Unable to find image 'metmma/metamma:latest' locally /usr/bin/docker: Error response from daemon: pull access denied for metmma/metamma, repository does not exist or may require 'docker login'. See '/usr/bin/docker run --help'. The command failed. 2) Once installed, how to I use it? Thanks in advance!
  2. I'm very new to setting up LetsEncrypt. I'm having an issue with obtaining my cert. FYI...I am a routing and security engineer and feel confident my network is configured properly. I'm only tell you this so that you will feel somewhat confident in my network. Certainly not telling you this to sound like a know-it-all/jackass. Also, just to add, I have verified two-way communication between the container and LetsEncrypt using the ports I specified via packet-captures. When I start the container I can see it communicating with devices on the internet but I'm still getting the below error. I have verified that "MyNon-DDNSdomainName.com" and "plex.MyNon-DDNSdomainName.com" resolves correctly to my public IP. I'm stumped - DNS forwarding and port-forwarding appears to be working yet I'm getting "connection refused" Variables set: PUID=99 PGID=100 TZ=America/New_York URL=MyNon-DDNSdomainName.com SUBDOMAINS=plex EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= EMAIL=me.me@gmail.com STAGING= Created donoteditthisfile.conf 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 SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d plex.MyNon-DDNSdomainName.com E-mail address entered: me.me@gmail.com http validation is selected Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for plex.MyNon-DDNSdomainName.com Waiting for verification... Challenge failed for domain plex.MyNon-DDNSdomainName.com http-01 challenge for plex.MyNon-DDNSdomainName.com Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: Domain: plex.MyNon-DDNSdomainName.com Type: connection Detail: Fetching http://plex.MyNon-DDNSdomainName.com/.well-known/acme-challenge/WZ75elsNMJQFuroOl-8itA8JOfBER7fnN9emxDcn4Ys: Connection refused To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
  3. Hello! I was having issues with my unRAID box not responding so I rebooted it from the CLI. Once it came back up, I was unable to access the GUI. I am able to SSH to it. Do you mind taking a look at my diagnostics file and giving me you're thoughts? Also, I should add that I received the below errors when creating the diagnostics file. When I KVM into the server I can see its stuck and will not move beyond a certain point (see attached picture) root@Tower:~# diagnostics Starting diagnostics collection... Warning: file_get_contents(/var/local/emhttp/cpuload.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 88 Warning: file(/var/local/emhttp/diskload.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 89 Warning: parse_ini_file(/var/local/emhttp/disks.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 90 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 91 Warning: implode(): Invalid arguments passed in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 100 done. ZIP file '/boot/logs/tower-diagnostics-20190716-1021.zip' created. Thanks in advance! tower-diagnostics-20190716-1021.zip
  4. I have the same issues and am unable to locate a solution.
  5. I see no way of doing this. I would think you would spin up another instance of the Docker container for the 2nd network. I have a few instances of Plex running on different networks using this method.
  6. I'm at a loss. My unRAID server's interface seems to lockup after the Docker process has been running for 10+ minutes. If I access the Docker page and attempt to stop a container it just hangs. It has no issues without Docker running. Please note I have no VMs and I've disabled it. After a few days of troubleshooting I decided to rebuild my USB stick in hopes it would resolve the issue - no luck. I'm not really sure how to find the issue at this point. I've attached my diagnostics file. Any help you can give is much appreciated. tower-diagnostics-20190221-1504.zip
  7. I upgraded my server to the latest BIOS but I'm still get the errors. Any other ideas?
  8. I created a thread this a couple of days ago in the General forums but I believe the issue I'm having is related to the Docker process. When I start Docker and the containers begin to run I start get the below errors in my SYSLOG. Any ideas how to resolve this? I attached my diagnostics file if that helps. Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265) Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._PMM, AE_NOT_EXIST (20180531/psparse-516) Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _PMM (20180531/power_meter-338) Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132) Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265) Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._GAI, AE_NOT_EXIST (20180531/psparse-516) Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _GAI (20180531/power_meter-130) Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132) Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265) Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._PMM, AE_NOT_EXIST (20180531/psparse-516) Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _PMM (20180531/power_meter-338) Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132) Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265) Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._GAI, AE_NOT_EXIST (20180531/psparse-516) Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _GAI (20180531/power_meter-130) Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132) tower-diagnostics-20190218-1506.zip
  9. Does anyone have any idea how I can fix this?
  10. I beleive I corrected that issue. The problem I'm seeing is when I start the Docker process I start getting a ton of "kernel: ACPI Error" errors. I have no idea what they mean or how to resolve them. As a test I blew away my Docker instance and rebuilt it but I keep getting the errors once Docker starts. ErrorWarningSystemArrayLogin Feb 19 17:14:46 Tower rpcbind[21703]: connect from 10.10.10.5 to getport/addr(mountd) Feb 19 17:15:15 Tower ool www[21535]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update Feb 19 17:15:15 Tower emhttpd: req (47): cmdStatus=apply&csrf_token=**************** Feb 19 17:15:15 Tower emhttpd: Starting services... Feb 19 17:15:15 Tower emhttpd: shcmd (778): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 40 Feb 19 17:15:15 Tower root: Creating new image file: /mnt/user/system/docker/docker.img size: 40G Feb 19 17:15:16 Tower rpcbind[22142]: connect from 10.10.10.5 to getport/addr(mountd) Feb 19 17:15:16 Tower root: btrfs-progs v4.17 Feb 19 17:15:16 Tower root: See http://btrfs.wiki.kernel.org for more information. Feb 19 17:15:16 Tower root: Feb 19 17:15:16 Tower root: Label: (null) Feb 19 17:15:16 Tower root: UUID: 71d890e8-8fff-4e82-803e-518e20daad64 Feb 19 17:15:16 Tower root: Node size: 16384 Feb 19 17:15:16 Tower root: Sector size: 4096 Feb 19 17:15:16 Tower root: Filesystem size: 40.00GiB Feb 19 17:15:16 Tower root: Block group profiles: Feb 19 17:15:16 Tower root: Data: single 8.00MiB Feb 19 17:15:16 Tower root: Metadata: DUP 1.00GiB Feb 19 17:15:16 Tower root: System: DUP 8.00MiB Feb 19 17:15:16 Tower root: SSD detected: no Feb 19 17:15:16 Tower root: Incompat features: extref, skinny-metadata Feb 19 17:15:16 Tower root: Number of devices: 1 Feb 19 17:15:16 Tower root: Devices: Feb 19 17:15:16 Tower root: ID SIZE PATH Feb 19 17:15:16 Tower root: 1 40.00GiB /mnt/disk4/system/docker/docker.img Feb 19 17:15:16 Tower root: Feb 19 17:15:16 Tower kernel: BTRFS: device fsid 71d890e8-8fff-4e82-803e-518e20daad64 devid 1 transid 5 /dev/loop2 Feb 19 17:15:16 Tower kernel: BTRFS info (device loop2): disk space caching is enabled Feb 19 17:15:16 Tower kernel: BTRFS info (device loop2): has skinny extents Feb 19 17:15:16 Tower kernel: BTRFS info (device loop2): flagging fs with big metadata feature Feb 19 17:15:16 Tower kernel: BTRFS info (device loop2): checking UUID tree Feb 19 17:15:16 Tower emhttpd: shcmd (780): /etc/rc.d/rc.docker start Feb 19 17:15:16 Tower root: starting dockerd ... Feb 19 17:15:18 Tower avahi-daemon[3199]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Feb 19 17:15:18 Tower avahi-daemon[3199]: New relevant interface docker0.IPv4 for mDNS. Feb 19 17:15:18 Tower avahi-daemon[3199]: Registering new address record for 172.17.0.1 on docker0.IPv4. Feb 19 17:15:18 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Feb 19 17:15:20 Tower root: Starting docker_load Feb 19 17:15:46 Tower rpcbind[24376]: connect from 10.10.10.5 to getport/addr(mountd) Feb 19 17:21:14 Tower kernel: eth0: renamed from veth72fd6b5 Feb 19 17:21:14 Tower kernel: device br0 entered promiscuous mode Feb 19 17:21:16 Tower rpcbind[11535]: connect from 10.10.10.5 to getport/addr(mountd) Feb 19 17:21:18 Tower kernel: eth0: renamed from veth576a504 Feb 19 17:21:22 Tower kernel: eth0: renamed from vethd1051bb Feb 19 17:21:26 Tower kernel: eth0: renamed from veth4c8653f Feb 19 17:21:30 Tower kernel: eth0: renamed from vethc32b208 Feb 19 17:21:37 Tower kernel: eth0: renamed from veth71198f6 Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132) Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265) Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._PMM, AE_NOT_EXIST (20180531/psparse-516) Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _PMM (20180531/power_meter-338) Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132) Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265) Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._GAI, AE_NOT_EXIST (20180531/psparse-516) Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _GAI (20180531/power_meter-130) Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132) Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265) Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._PMM, AE_NOT_EXIST (20180531/psparse-516) Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _PMM (20180531/power_meter-338) Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132) Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265) Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._GAI, AE_NOT_EXIST (20180531/psparse-516) Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _GAI (20180531/power_meter-130) Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132)
  11. When I click on it and open it within my browser I get a bunch of text (see attached). text.txt
  12. This was the link I was using - https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg
  13. I'm getting the following error when trying to update the application - any ideas? plugin: updating: community.applications.plg Cleaning Up Old Versions plugin: downloading: https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2019.02.18a-x86_64-1.txz ... failed (Invalid URL / Server error response) plugin: wget: https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2019.02.18a-x86_64-1.txz download failure (Invalid URL / Server error response)
  14. My unRAID interface is acting strangely. I logged into today to find my Docker tab missing. I rebooted the box and the tab came back but the containers are taking time to load and some of the applications never start. I looked through my log and found the errors contained in the attached syslog file. Do you mind taking a look and let me know what you think is wrong? tower-diagnostics-20190218-1506.zip syslog.txt