Jump to content

Marv

Members
  • Content Count

    210
  • Joined

  • Last visited

Community Reputation

3 Neutral

1 Follower

About Marv

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

790 profile views
  1. Sorry for the late response. I don't use Ryzen. The error is gone for me since some Emby update.
  2. Ok, thanks for your clarification
  3. Hi, I recognized these errors in my logs from time to time: Feb 11 06:55:38 server kernel: ffdetect[7993]: segfault at 38 ip 0000000000403a38 sp 00007ffe0bc961a0 error 4 in ffdetect[400000+15000] Feb 11 06:55:38 server kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 Feb 11 06:55:38 server kernel: ffdetect[7994]: segfault at 38 ip 0000000000403a38 sp 00007ffc20f107b0 error 4 in ffdetect[400000+15000] Feb 11 06:55:38 server kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 Can someone tell me what's going on there please?
  4. I'm looking in /config/log/letsencrypt/letsencrypt.log After another try changing the subdomains the logfile got updated again. I don't know why it wasn't working before. But it seems to be solved somehow.
  5. I have the same problem that I got an email that my cert is going to expire. I didn't change anything in my docker config for over a year so I don't really know what was causing this. So I tried adding a subdomain in the container settings which triggert a cert renewal. But I still got the problem that the renewal process is somehow not working properly. When checking the letsencrypt logfile it didn't get changed for more than 20 days now. This is the last entry: cronjob running on Sat Jan 19 02:08:00 CET 2019 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/xxxxxxxserver.com.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert not yet due for renewal - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The following certs are not due for renewal yet: /etc/letsencrypt/live/xxxxxxxserver.com/fullchain.pem expires on 2019-02-18 (skipped) No renewals were attempted. No hooks were run. Even the manual renewal by adding a subdomain did not trigger a log entry. Whats going on here?
  6. You update the Nextcloud version from the Nextcloud webUI. It doesn't get updated by updating the docker container. To get rid of your error add add_header Referrer-Policy no-referrer always; into '/config/nginx/site-confs/default' (Nextcloud's appdata folder)
  7. I can't seem to get this working. What file do I need to edit? I tried '/config/nginx/site-confs/default' inside the nextcloud container and my nginx container aswell
  8. Unfortunately that's not solving the 'caldav/carddav' issue. Adding the header solves the Referrer-Policy issue. If anyone knows how to resolve 'caldav/carddav' this would be great.
  9. Hi, there seems to be a bug when using "wait" values for docker containers and then rearranging the order of the docker containers. This won't update the list order. So the start order of the docker containers stays the same as before. these are my settings in the webUI and this is the start order of the containers Sep 28 18:32:08 unMARV rc.docker: EmbyServer: started succesfully! Sep 28 18:32:08 unMARV rc.docker: EmbyServer: wait 5 seconds Sep 28 18:32:13 unMARV rc.docker: JDownloader-2: started succesfully! Sep 28 18:32:13 unMARV rc.docker: JDownloader-2: wait 5 seconds Sep 28 18:32:19 unMARV rc.docker: Letsencrypt-Nginx: started succesfully! Sep 28 18:32:19 unMARV rc.docker: Letsencrypt-Nginx: wait 5 seconds Sep 28 18:32:24 unMARV rc.docker: MariaDB: wait 5 seconds Sep 28 18:32:24 unMARV rc.docker: MariaDB: started succesfully! Sep 28 18:32:30 unMARV rc.docker: Nextcloud: started succesfully! Sep 28 18:32:30 unMARV rc.docker: Nextcloud: wait 5 seconds Sep 28 18:32:35 unMARV rc.docker: TeamSpeak: started succesfully! Sep 28 18:32:35 unMARV rc.docker: TeamSpeak: wait 5 seconds Sep 28 18:32:41 unMARV rc.docker: Tvheadend: wait 5 seconds Sep 28 18:32:41 unMARV rc.docker: Tvheadend: started succesfully! Sep 28 18:32:46 unMARV rc.docker: cAdvisor: started succesfully! diagnostics-20180928-2323.zip
  10. EmbyServer 5 JDownloader-2 5 Letsencrypt-Nginx 5 MariaDB 5 Nextcloud 5 TeamSpeak Tvheadend 5 cAdvisor
  11. So this is what I defined via the webUI and this is the order the containers start Sep 28 18:32:08 unMARV rc.docker: EmbyServer: started succesfully! Sep 28 18:32:08 unMARV rc.docker: EmbyServer: wait 5 seconds Sep 28 18:32:13 unMARV rc.docker: JDownloader-2: started succesfully! Sep 28 18:32:13 unMARV rc.docker: JDownloader-2: wait 5 seconds Sep 28 18:32:19 unMARV rc.docker: Letsencrypt-Nginx: started succesfully! Sep 28 18:32:19 unMARV rc.docker: Letsencrypt-Nginx: wait 5 seconds Sep 28 18:32:24 unMARV rc.docker: MariaDB: wait 5 seconds Sep 28 18:32:24 unMARV rc.docker: MariaDB: started succesfully! Sep 28 18:32:30 unMARV rc.docker: Nextcloud: started succesfully! Sep 28 18:32:30 unMARV rc.docker: Nextcloud: wait 5 seconds Sep 28 18:32:35 unMARV rc.docker: TeamSpeak: started succesfully! Sep 28 18:32:35 unMARV rc.docker: TeamSpeak: wait 5 seconds Sep 28 18:32:41 unMARV rc.docker: Tvheadend: wait 5 seconds Sep 28 18:32:41 unMARV rc.docker: Tvheadend: started succesfully! Sep 28 18:32:46 unMARV rc.docker: cAdvisor: started succesfully!
  12. I tried that, but it didn't work. Unraid always keeps the same order
  13. Hi, update went without a problem. I just can't seem to get my Dockers started in the order I defined with the new timers. How is this supposed to work? It seems that unraid just starts my containers in one specific order (not the order of the webUI) and adds the delays.