Jump to content

AlexNathan345

Members
  • Content Count

    60
  • Joined

  • Last visited

Community Reputation

0 Neutral

About AlexNathan345

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    London, United Kingdom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks Squid for trying to help again. I tried the above without look - still the same problem I'm afraid. Reading around it seems that to resolve this one can either re-create the certs which doesn't work on unRAID per command above, or to disable certificate checking altogether (docker --tlsverify=false - again doesn't seem to work on unRAID) which I'd be happy with but can't find anywhere to do this... Very frustrating the whole thing as it just started to happen whilst I was on holiday and clearly hadn't done anything with the server.
  2. Is there any way of running something similar to docker-machine regenerate-certs default on unRAID? In other words, is there a way of re-generating the SSL certificates docker uses?
  3. Stopping docker, creating a new image and then installing a docker (either from existing template or totally new one) doesn't work - I still get the same errors. However, installing a new plugin from CA or updating existing ones works fine (without errors). Did the diagnostics file shed any light on the problem? Or do you think any installed plugins could interfere with docker? Perhaps ones that installed incorrectly (although they all seem to work)? I have these plugins installed (all are the latest version): CA Auto Update Applications CA Backup / Restore Appdata CA Cleanup Appdata CA Resource Monitor Community Applications Dynamix Active Streams Dynamix Auto Fan Control Dynamix Cache Directories Dynamix Local Master Dynamix SSD TRIM Dynamix System Information Dynamix System Statistics Fix Common Problems Nerd Tools Preclear Disks SNMP ssh Plugin Statistics SwapFile Unassigned Devices Nerd Tools has the following packages installed: perl-5.24.0-x86_64-1.txz python-2.7.13a-x86_64-2.txz python3-3.5.2-x86_64-1.tgz screen-4.4.0-x86_64-1.txz subversion-1.9.5-x86_64-1.txz tmux-2.5-x86_64-1.txz unrar-5.4.5-x86_64-1.txz utempter-1.1.6-x86_64-2.txz Thanks for your help!
  4. I'll try this suggestion, thank you. In the meantime I attached the diagnostics file. unraidserver01-diagnostics-20170714-1047.zip
  5. Can anyone help please as I urgently need to install a docker I deleted by accident but cannot do so due to the same error? Would attaching a diagnostics file help? Thanks so much in advance.
  6. PS: Re-booting the server and updating unRAID to the latest version 6.3.5 didn't solve the problems. Any other suggestions to resolve this please?
  7. No, date and time are correct as reported by the 'date' command. Or is there a different date/time for dockers?
  8. Whenever I try to update (or download) any docker containers I get the following error message (this example is for the Emby container): Error: Get https://registry-1.docker.io/v1/repositories/emby/embyserver/tags/latest: x509: certificate is valid for *.tvaas.com, not registry-1.docker.io But the messages are the same for the other ones except for the repository link. I have no idea what this means or how to fix it - can anyone help please? Re-starting the dockers or the docker service didn't help. Thanks!
  9. Hi, I just re-downloaded your LMS docker and it won't start anymore. Used to run fine, didn't change the config folder or anything else, just re-downloaded the latest version of the container. Any idea what could be going on here? Thanks a lot. Update: I just noticed a new variable that wasn't there before: /var/run/dbus mapped to /var/run/dbus - could this be (part of) the problem? Update 2: Having read the previous post I changed bridge mode to host mode and the docker now starts. Strange thing is, it has been working fine in bridge mode for months until this afternoon...
  10. Same issue here, the docker starts but than stops. Can't start at all. Is there an earlier version I can revert back to until this is fixed? ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- finding fastest mirror 1. ubuntu.mirrors.uk2.net Latency: 6 ms Org: UK2 Status: Up to date Speed: 1 Gbps 2. mirror.sov.uk.goscomb.net (current) Latency: 6 ms Org: Goscomb Technologies Limited Status: Up to date Speed: 1 Gbps 3. archive.ubuntu.com Latency: 6 ms Org: Canonical Ltd. Status: Up to date Speed: 100 Mbps New config file saved to /defaults/sources.list We are now refreshing packages from apt repositories, this *may* take a while Ign http://ubuntu.mirrors.uk2.net trusty InRelease Get:1 http://ubuntu.mirrors.uk2.net trusty-updates InRelease [65.9 kB] Hit http://ppa.launchpad.net trusty InRelease Hit http://ppa.launchpad.net trusty/main amd64 Packages Get:2 http://ubuntu.mirrors.uk2.net trusty-security InRelease [65.9 kB] Get:3 http://ubuntu.mirrors.uk2.net trusty Release.gpg [933 B] Get:4 http://ubuntu.mirrors.uk2.net trusty-updates/main Sources [346 kB] Get:5 http://ubuntu.mirrors.uk2.net trusty-updates/restricted Sources [5,217 B] Ign http://ubuntu.mirrors.uk2.net trusty InRelease Get:1 http://ubuntu.mirrors.uk2.net trusty-updates InRelease [65.9 kB] Hit http://ppa.launchpad.net trusty InRelease Hit http://ppa.launchpad.net trusty/main amd64 Packages Get:2 http://ubuntu.mirrors.uk2.net trusty-security InRelease [65.9 kB] Get:3 http://ubuntu.mirrors.uk2.net trusty Release.gpg [933 B] Get:4 http://ubuntu.mirrors.uk2.net trusty-updates/main Sources [346 kB] Get:5 http://ubuntu.mirrors.uk2.net trusty-updates/restricted Sources [5,217 B] Get:6 http://ubuntu.mirrors.uk2.net trusty-updates/universe Sources [194 kB] Get:7 http://ubuntu.mirrors.uk2.net trusty-updates/multiverse Sources [5,943 B] Get:8 http://ubuntu.mirrors.uk2.net trusty-updates/main amd64 Packages [964 kB] Get:9 http://ubuntu.mirrors.uk2.net trusty-updates/restricted amd64 Packages [23.5 kB] Get:10 http://ubuntu.mirrors.uk2.net trusty-updates/universe amd64 Packages [464 kB] Get:11 http://ubuntu.mirrors.uk2.net trusty-updates/multiverse amd64 Packages [14.3 kB] Get:12 http://ubuntu.mirrors.uk2.net trusty Release [58.5 kB] Get:13 http://ubuntu.mirrors.uk2.net trusty-security/main Sources [147 kB] Get:14 http://ubuntu.mirrors.uk2.net trusty-security/restricted Sources [3,920 B] Get:15 http://ubuntu.mirrors.uk2.net trusty-security/universe Sources [41.8 kB] Get:16 http://ubuntu.mirrors.uk2.net trusty-security/multiverse Sources [2,547 B] Get:17 http://ubuntu.mirrors.uk2.net trusty-security/main amd64 Packages [602 kB] Get:18 http://ubuntu.mirrors.uk2.net trusty-security/restricted amd64 Packages [20.2 kB] Get:19 http://ubuntu.mirrors.uk2.net trusty-security/universe amd64 Packages [167 kB] Get:20 http://ubuntu.mirrors.uk2.net trusty-security/multiverse amd64 Packages [4,853 B] Get:21 http://ubuntu.mirrors.uk2.net trusty/main Sources [1,335 kB] Get:22 http://ubuntu.mirrors.uk2.net trusty/restricted Sources [5,335 B] Get:23 http://ubuntu.mirrors.uk2.net trusty/universe Sources [7,926 kB] Get:24 http://ubuntu.mirrors.uk2.net trusty/multiverse Sources [211 kB] Get:25 http://ubuntu.mirrors.uk2.net trusty/main amd64 Packages [1,743 kB] Get:26 http://ubuntu.mirrors.uk2.net trusty/restricted amd64 Packages [16.0 kB] Get:27 http://ubuntu.mirrors.uk2.net trusty/universe amd64 Packages [7,589 kB] Get:28 http://ubuntu.mirrors.uk2.net trusty/multiverse amd64 Packages [169 kB] Fetched 22.2 MB in 6s (3,646 kB/s) Reading package lists...
  11. Ok, thanks for clarifying. Since I only use ownCloud to sync files within the local network I'll keep it on http for the time being. And if I need external access there's always VPN to keep things simple.
  12. Hi, I hope you can help me. I added your owncloud docker, mapped all the folders and got it to start fine. However, I can only access owncloud via http (locally). Whenever I try https locally I can't get to the admin pages but get an error message instead: FIREFOX Secure connection failed. An error occurred during a connection to 10.148.106.30:8000. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. CHROME This site can’t provide a secure connection xxx.xxx.xxx.xxx sent an invalid response. ERR_SSL_PROTOCOL_ERROR OWNCLOUD SYNC TOOL FOR WINDOWS Error: SSL handshake failed. How can I get HTTPS working with this container please? Thanks for your help.
  13. Hi, I just did and it lists all my hard drives with a colon but no temperatures at all. Drives are all spun down though. Hope this helps, Alex. PS: I'm on the latest version of the plugin.
  14. I just set the EDGE variable to '1' then re-started the Docker and then updated to v8.1 via the ownCloud admin web page. This process seems to have worked ok but the admin page now shows 4 warnings (PHP, internet connectivity, security and caching) that don't sound critical. Is this the correct way of updating? Or should I have done things differently?