mattmill

I have managed to resolve this by adding APACHE_BODY_LIMIT=0 To my container environment variables https://help.nextcloud.com/t/server-replied-413-request-entity-too-large-to-put/154278/6?u=mattmill

Hello, I'm getting 413 error when uploading large files using the windows client. So far I have: Added the environment variable PHP_UPLOAD_LIMIT=20G to my unraid container. This change is reflected in the Nextcloud Web UI but I still get the 413 errors. Added client_max_body_size 20G; to my NGINX Prxoy Manager config. Doesn't make any difference. Added php_value upload_max_filesize 20G and php_value post_max_size 20G to .htaccess. Again this is reflected in the Web UI but isn't really needed IMO as the environment variable above does the same thing. Has anyone got any other idea why I am still getting this error?

Has anyone managed to successfully port forward using Unriads built in vpn manager?

Does anyone know if port forwarding to rTorrent works when using VPN to Docker? Setup a WG connection to Mullvad with a port forward configured. However in ruTorrent the port is shown as closed. I have done a port mapping in the containers config but it seems unable to pass through the port.

Got it working now. For anyone who stumbles upon this I had to install nano (my prefered editor) apk add nano Then run to open the groups nano /etc/group I then manually added to the group file. Your GID (281 below) may differ on your host machine. docker:x:281:zabbix Save and reboot docker container and it now works Just note that your GID may differ from the one above (281). To find your docker group ID run the below on your host machine getent group docker | awk -F: '{printf "Group %s with GID=%d\n", $1, $3}' Thanks for the pointers @VRx

Thanks for this, this was something I didn't do. However after doing this the docker service is still reported as down in Zabbix.

Nice work on this! Is there anyway to monitor docker containers with this plugin? I am passing /var/run/docker.sock to the container but Zabbix reports the Docker service as down. Anyone had success?

My server pulled the latest build last night but now I can't log in? My details are saved in Bitwarden so they are definitely correct. Has something changed?

Unmanic server is running Ubuntu. It's a rented dedicated server so like you, I am not punishing my main server.

@Josh.5 I’m trying to do something a little more advanced with unmanic. I am running unmanic in a docker container on a server which is separate from my media server. However when I mount my media server share via SSHFS onto the unmanic server, unmanic won’t pick up any of the files? I can transfer the files manually via SFTP and it works but that will take ages. Any ideas why unmanic won’t detect files when using SSHFS?

Also having this exact problem after doing my weekly updates on Sunday. Can't seem to find a solution though?

Been using for a while now and was wondering if there is anyway of setting up Lets Encrypt on this docker?

That's worked! Thank you for your help getting this sorted!

I have removed that line now but it still wont start properly. supervisord.log

I have removed those 2 lines but im still having the issue. supervisord.log

Heres the supervisor log with debug on. supervisord.log

i have attatched my supervisor log and a screenshot of what files i get from mullvad when i download the linux configuration. I should add that i changed it from mullvad_nl.conf to mullvad_nl.ovpn supervisord.log

Cant seem to get Mullvad to work. Looks like theyve changed their config downloads. The certificates are now separate files. Anyone any ideas?