Oplosophos

Members
  • Posts

    13
  • Joined

  • Last visited

Oplosophos's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I have tried this. I disabled docker, changed the name of the img, shutdown and restarted the server, enabled docker again and attempted to download a docker. It just hung and I got no progress window. I have confirmed that I have a new docker.img file. I have attached the diagnostics from this attempt. Thank you for your help. thunderer-diagnostics-20190902-1701.zip
  2. Thanks Frank and Squid, I'll give this a go hopefully tomorrow and let you know how it goes.
  3. I haven't heard anything back on this, I have attached another diagnostics after trying to set to IPv4 only If anyone has any clue as to what's going on I would greatly appreciate some help. thunderer-diagnostics-20190826-1812.zip
  4. The results of the ping was: root@Thunderer:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=344 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=361 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=283 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=228 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=99.6 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=54 time=73.8 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=54 time=271 ms ^C --- 8.8.8.8 ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6001ms rtt min/avg/max/mdev = 73.857/237.562/361.586/104.199 ms I checked my network protocol, It was set to IPv4 only. I changed it to IPv4 +IPv6 applied and then changed it back to IPv4 only. (I did not start array between changing it and changing it back. I also have IPv6 disabled in my router settings.) Thanks for your help.
  5. Hi, Version 6.6.6 2018-12-01 with AMD 1st Gen CPU/mobo Since moving and getting a great slowdown in my internet speed I have been unable to download or update dockers. Until now I have just been ignoring it. It just times out whenever I attempt to change something. I am currently trying to download a new plex server and I am receiving the following error Aug 11 19:21:51 Thunderer nginx: 2019/08/11 19:21:51 [error] 3585#3585: *6602135 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.2, server: , request: "POST /Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/OfficialPlexRepository/PlexMediaServer.xml HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "thunderer", referrer: "http://thunderer/Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/OfficialPlexRepository/PlexMediaServer.xml" Any assistance with this would be appreciated as I am now without a plex server. Now including Diagnostics thunderer-diagnostics-20190812-0729.zip
  6. Hi, Version 6.6.6 2018-12-01 with AMD 1st Gen CPU/mobo Since moving and getting a great slowdown in my internet speed I have been unable to download or update dockers. Until now I have just been ignoring it. It just times out whenever I attempt to change something. I am currently trying to download a new plex server and I am receiving the following error Aug 11 19:21:51 Thunderer nginx: 2019/08/11 19:21:51 [error] 3585#3585: *6602135 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.2, server: , request: "POST /Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/OfficialPlexRepository/PlexMediaServer.xml HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "thunderer", referrer: "http://thunderer/Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/OfficialPlexRepository/PlexMediaServer.xml" Any assistance with this would be appreciated as I am now without a plex server.
  7. Thank jonnie, I have disabled global C-state in the bios and will monitor this week.
  8. Hi, thanks for the help. I have for the last few months been having crashes in my server requiring me to reset. After running the analytics, I received a hardware error. I have included the log and log tail from the latest crash. I have also included a copy of my hardware profile. I did install Nerdpack and mcelog but cannot find the output. Any advice would be greatly appreciated. System info, Unraid v6.6.6 Mobo: ASUS Prime X370-Pro CPU: Ryzen 7 1700 FCPsyslog_tail.txt thunderer-diagnostics-20190305-0024.zip Hardwareprofile.txt
  9. Hello, I have been trying to set up my letsencrypt docker following this guide. https://cyanlabs.net/tutorials/the-complete-unraid-reverse-proxy-duck-dns-dynamic-dns-and-letsencrypt-guide/ I get the following error from the docker when I run it. Failed authorization procedure. DOMAIN.duckdns.org (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Error getting validation dataIMPORTANT NOTES:- The following errors were reported by the server:Domain: DOMAIN.duckdns.orgType: connectionDetail: Error getting validation data I have also tried a noip dynamic DNS but I received the same error. I also disabled my firewall to check to see if that was the problem but I received the same error. Ideally what I want to do is use the domain I bought in this, but I bought my domain through squarespace and have no idea how to do that. Any advice in this situation would be appreciated.
  10. I have had a full day without issues. I will bring it back up if issues resurface. Thank you for your help.
  11. Much appreciated. Will do so ASAP and update on the result.
  12. I have recently set up my own Unraid Server, Running Unraid 6.3.5 on a AMD Ryzen 1700 on an ASUS Prime X370 Pro motherboard (no overclocking). I cannot recall when the crashes started but they started very early on. The motherboard is running UEFI 0902. SVM is enabled in the UEFI. Usually when I usually come home to find the server unresponsive from the WebGUI. I recently installed the common problems app and have attached the log and syslog tail. I have been using the had reset button to get is started again. The direct display, when connected still displays after crash, but is unresponsive. I ran memtest overnight the other day and testing all memory for 3 passes resulted in 0 errors. Please let me know if you need more information and I am very grateful for any assistance you can provide. FCPsyslog_tail.txt thunderer-diagnostics-20171007-1212.zip