Jump to content

EdgarWallace

Members
  • Content Count

    821
  • Joined

  • Last visited

Community Reputation

4 Neutral

About EdgarWallace

  • Rank
    Advanced Member
  • Birthday 09/05/1963

Converted

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

871 profile views
  1. Great @bonienl Worked very well, thank you very much: root@Tower:~# /usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker -b2 -u "/mnt/disk2/iTunes/Music/Eric Clapton/I Still Do" Finished - verified 12 files, skipped 0 files. Found: 0 mismatches, 1 corruption (updated). Duration: 00:00:04. Average speed: 149 MB/s
  2. Oh great@bonienl. Thanks a lot. Gesendet von iPad mit Tapatalk
  3. On every run the server is providing a wrong error message: BLAKE2 hash key mismatch, /mnt/disk5/iTunes/Music/Wolfgang Haffner/Kind of Cool/02 So What.aif is corrupted However the file is perfectly ok. Is there any way to update the hash key manually?
  4. Thanks a lot for your clarification @aptalca Making sure that I am leaving my server on during the night from time to time.
  5. @aptalca, yes I am usually shutting it down. I was hoping that the renewal is also running, when the container is starting.
  6. @trurl, thanks for your help in moving that into the correct thread. @saarg, I have never modified anything within the container because it was running as expected - until March 1st. I read, that letsencrypt is producing these file one after one e.g. /mnt/user/system/docker/appdata/letsencrypt/etc/letsencrypt/live/myurl.com/cert.pem is pointing towards the correct file in /mnt/user/system/docker/appdata/letsencrypt/etc/letsencrypt/archive/myurl.com/cert7.pem so having many of these files seems to be fine. I was asking mainly if there is a known issue with the container, because the log it isn't showing anything unusual. However, I might have overlooked something so it is attached now. Thanks for your help. letsencrypt.log
  7. Thanks a lot @saarg I don't understand why the certificate wasn't renewed this time (March 1s). It was always working in the past. E.g. cert1.pem - cert6.pem are available in the respective directory but cert7.pem was missing and added with my manual action. Subdomain was always defined as (no changes from my side were made since ages): , I am using this container only for Nextcloud and I am accessing it via https://myurl.com/index.php/login
  8. I fixed my issue with: open console of letsencrypt container run command: certbot renew First time ever letsencrypt wasn't doing the certificate renewal process automatically. Anyone has experienced the same? Is there anything I can do about it?
  9. Seems that Let's Encrypt didn't renew the certificate. I was searching but didn't found anything that is showing how to solve that renewal issue. Any hint?
  10. I am having well running Nextcloud and Let's Encrypt Docker (log is saying: [services.d] done and Server ready). On March 1st the SSL Certificate was loosing validity and now all my devices (macos, iphone, iPad) can't access Nextcloud anymore. After done some search I thought that I have to download the renewed key at /mnt/user/system/docker/appdata/letsencrypt/keys/letsencrypt There are a couple of keys (cert.pem, fullchain.pem etc.) that are linked to e.g. /mnt/user/system/docker/appdata/letsencrypt/etc/letsencrypt/archive/myURL/cert.pem Whatever file I am loading into one of my devices it is telling me that it was loosing validity March 1st. Thanks for any help.
  11. I am having well running Nextcloud and Let's Encrypt Docker (log is saying: [services.d] done and Server ready). On March 1st the SSL Certificate was losing validity and now all my devices (macos, iphone, iPad) can't access Nextcloud anymore. After done some search I thought that I have to download the renewed key at /mnt/user/system/docker/appdata/letsencrypt/keys/letsencrypt There are a couple of keys (cert.pem, fullchain.pem etc.) that are linked to e.g. /mnt/user/system/docker/appdata/letsencrypt/etc/letsencrypt/archive/myURL/cert.pem Whatever file I am loading into one of my devices it is telling me that it was loosing validity March 1st. Thanks for any help,
  12. The upgrade went well on both of my servers. I love that all my Macs are running Time Machine now via SMB. Only (minor) issue is around my APC (APC Smart-UPS SC, 450VA). Some data is missing on the Weg GUI where Grafana/InfluxDB Docker is showing all information available. Please see my screen shots.
  13. Yes, the Fan Speed Mode will be kept forever....my settings are shown below.
  14. I was looking into the file system of my Selfsat device. It is basically a Linux device and there is no such a file. I honestly don‘t know what happened because it was working until any of the TVheadend updates.
  15. My main server contains a X11SSL-CF board. IPMI was running very well but since a while the Fan Speed Mode is set at FULL. Hence my fans are running at full speed and only if I am setting it back to Standard or Optimal, IPMI plugin is taking back control and the fans are running at much lower speed. BIOS version is 2.2 from 05/23/18, Firmware is 1.48 from 06/22/18, Redfish 1.0.1 Maybe I overlooked something during the recent IPMI updates?