Debaser

ooh i see, i think there was a new version released 2 days ago (0.4.4) where when i installed the mod pack via curse a few days ago it was 0.4.3. I see the container is using 0.4.4 so upgrading the client now to test thanks for the info edit: yep that was it, all good now, thanks!

Hey, thanks for the container, makes it a lot easier than uploading mods to mineos. Running into an issue with AllTheMods7 container. It's up and running, I can see it, I can see my connection attempt in the logs, but I get an error `mismatched mod channel list` in the client when connecting. This seems to be a mismatch of mods or mod versions on the client vs the server. I don't play minecraft, just hosting a server for friends so I don't really know how to troubleshoot the mods. I downloaded the package and launched from the CurseForge app. Any easy way to compare what mods are mismatched? Thanks

if anyone else stumbles across this with the same issue, it's because of the network type on the docker container. at least it was in my case. i had it set to custom with its own IP. needed to set it to Host to allow inbound connections. here's the reddit thread where someone helped me understand this: here's my config for the reverse proxy if interested server { listen 443 ssl; server_name nvr.redacted.xyz; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:$ ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; client_body_buffer_size 400M; location / { proxy_set_header X-Real_IP $remote_addr; proxy_pass https://192.168.1.204:7443/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; } }

having issues getting the unifi video container working behind nginx reverse proxy. anyone having any luck? getting a 502 bad gateway here's my config map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { listen 80; server_name nvr.domain.xyz; client_max_body_size 4G; location / { proxy_redirect off; proxy_set_header Host $host; proxy_pass http://192.168.1.10:7080/; } } server { listen 443 ssl http2; server_name nvr.domain.xyz; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl on; set $upstream 192.168.1.10:7443; location / { proxy_pass https://$upstream; proxy_redirect https://$upstream https://$server_name; proxy_cache off; proxy_store off; proxy_buffering off; proxy_http_version 1.1; proxy_read_timeout 36000s; proxy_set_header Host $http_host; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Referer ""; client_max_body_size 0; } }

Spoke too soon, looks like it's throwing a 502 timeout after the upload completes 1.5 hrs later. Where would I be looking to change the timeout interval?

Good call I ran a grep on my cache drives where my containers are installed grep -R client_max_body_size /mnt/cache/appdata Most configs were already set to client_max_body_size 0; But I missed in the letsencrypt nginx proxy.conf was set to client_max_body_size 10m; So ran a quick command to change it over sed -i 's/client_max_body_size 10m;/client_max_body_size 0;/g' /mnt/cache/appdata/letsencrypt/nginx/proxy.conf Seems to be uploading now without a problem. Thanks for the shove in the right direction

Hey guys, trying to upload large files to my nextcloud, but getting an error 413 Request Entity Too Large I'm running this behind my letsencrypt docker on a reverse proxy. I've tried editing the site config for both the letsencrypt nginx as well as nextcloud's nginx as follows letsencrypt nginx client_max_body_size 20G; client_body_buffer_size 400M; nextcloud nginx # set max upload size client_max_body_size 20G; fastcgi_buffers 64 4K; Restarted both containers fron unRAID and still getting this error when I try to sync my large file. The file is 14GB if that makes a difference Any suggestions? Thanks