Marv

Members
  • Content Count

    215
  • Joined

  • Last visited

Community Reputation

3 Neutral

1 Follower

About Marv

  • Rank
    Member

Converted

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

1153 profile views
  1. Did the container stopped working for anyone else since upgrading to 6.8.3? I just get "server execution error" when trying to start it. This is the only container I have this problem with
  2. Upgade went without any issue for me and everyhing is working as expected. But I noticed that my server needs much more time to boot now. Is there anything in the changelog that can explain this?
  3. Ok thanks. I'll try this later. Just out of curiosity: Is it possible to use the default config file under "site-confs" to just handle my Nextcloud subdomain (cloud.mydomain.com) and another config for Emby (emby.mydomain.com) under "proxy-confs"? The reason I'm asking is because I don't really have a use case for my main domain (mydomain.com) or my DNS url and just want the two subdomains to be "visible". So when entering either mydomain.com or my DNS domain I want to get pointed to cloud.mydomain.com for example. Is this possible?
  4. But my container is named "Nextcloud" actually. That's why I'm using: set $upstream_nextcloud Nextcloud; Isn't this correct then?
  5. Hi, I'm trying to move my Nextcloud setup from a subfolder setup to a dedicated subdomain using a CNAME record pointing to my DNS. But I'm struggling to get this to work. Here are the files I adjusted, maybe someone can have a look at this please: Letsencrypt container: config\nginx\proxy-confs\nextcloud.subdomain.conf server { listen 443 ssl; listen [::]:443 ssl; server_name cloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.
  6. Sorry for the late response. I don't use Ryzen. The error is gone for me since some Emby update.
  7. Ok, thanks for your clarification
  8. 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:3
  9. 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.
  10. 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 t
  11. 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)
  12. 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
  13. 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.
  14. 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 unMAR