The permanent fix for this is expected with the 2.1 release, however there is not a scheduled date at this time.
Workaround:
A script is attached to this case that will set the maximum attachment size to the correct setting of 50 megabytes.
Since that front end environment resets each time it is started, it is necessary to run the script after bootup each time the appliance is restarted. This can be done manually, or can be accomplished automatically by adding it to a system startup file. If adding it to a system startup file, it is recommended to deactivate this script prior to updating to v2.10.
The steps outlined below will use the rc.local script to wait 90 seconds after bootup to run the script.
- Download and unzip the script attached to this article
- Copy the script to /home/ops on the services VM
- SSH into the services VM as the ops user and run the following commands:
$ chmod +x /home/ops/nginx-attachment-update
$ sudo chmod +x /etc/rc.d/rc.local
$ sudo echo sleep 90 && /home/ops/nginx-attachment-update >> /etc/rc.d/rc.local
Deactivating:
If it becomes necessary to deactivate this script, for example prior to upgrading to 2.10 when it is released, perform the following:
- SSH into the services VM as the ops user and run the following commands:
$ chmod -x /home/ops/nginx-attachment-update
$ sudo chmod -x /etc/rc.d/rc.local