Runi215

Hi, quick question about Owncast. I'm using a intel IGPU and I was wondering where I should point Owncast to /dev/dri. The container description states the following: At 'Device' at the bottom here in the template add '/dev/dri' but I don't see any Device variable. I tried adding it to Nvidia Visible Devices, but that doesn't seem to work. Do I need to add it to Extra Startup Parameters with a key? Am I not seeing something or is this Device key missing? Thanks in advance.

My other reverse proxies are working correctly. Docker log: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 70-aliases: executing... [cont-init.d] 70-aliases: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 70-aliases: executing... [cont-init.d] 70-aliases: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. appdata/nextcloud/log/nginx/error.log: 2020/11/30 16:58:18 [crit] 377#377: *79 SSL_write() failed while sending response to client, client: 192.168.0.1, server: _, request: "GET /apps/text/js/files.js?v=9575ceb6-0 HTTP/1.1", host: "cloud.xxxxxxxxxx.nl" 2020/11/30 16:58:18 [crit] 377#377: *83 SSL_write() failed while sending response to client, client: 192.168.0.1, server: _, request: "GET /apps/recommendations/js/main.js?v=9575ceb6-0 HTTP/1.1", host: "cloud.xxxxxxxx.nl" 2020/11/30 16:58:18 [crit] 377#377: *86 SSL_write() failed while sending response to client, client: 192.168.0.1, server: _, request: "GET /apps/comments/js/comments.js?v=9575ceb6-0 HTTP/1.1", host: "cloud.xxxxxxxx.nl"

Hi all, I tried updating my Nextcloud container with the help of this SpaceInvader One video (https://www.youtube.com/watch?v=un4L5inokZE) and it broke. I tried reinstalling, but when I try to enable the reverse proxy I get a 504 Gateway Time-out. Sometimes I can get through to Nextcloud but the site is incredibly slow. I tried to fix it, but I don't really understand what is wrong. It can find the docker container, but most of the time it times out. Does anyone know what to do? The nextcloud.subdomain.conf file: server { listen 443 ssl; listen [::]:443 ssl; server_name cloud.*; include /config/nginx/ssl.conf; # add_header X-Frame-Options "SAMEORIGIN" always; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_max_temp_file_size 2048m; } }