Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need global custom variable for client_max_body_size like custom.ini for php #1384

Closed
demyxco opened this issue Feb 1, 2019 · 2 comments
Closed

Comments

@demyxco
Copy link

demyxco commented Feb 1, 2019

Increasing upload limits for custom.ini does nothing when .conf from nginx/nginx-proxy hinders it. Duplicate error appears when adding client_max_body_size to user.conf and WordPress throws a 413 error when uploading a file that's over 100mb.

What I've tried but didn't work:

  • Modified client_max_body_size in /var/lib/docker/volumes/domaintld_config_nginx/_data/nginx.conf && ee site reload domain.tld
  • Modified client_max_body_size in /var/lib/docker/volumes/domaintld_config_nginx/_data/conf.d/main.conf && ee site reload domain.tld
  • Modified client_max_body_size in services_global-nginx-proxy_1:/etc/nginx/nginx.conf && ee service reload nginx-proxy
# Custom PHP settings

upload_max_filesize = 1G
post_max_size = 1G

**System Information**

# ee cli info
+-------------------+----------------------------------------------------------------------------+
| OS                | Linux 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 |
| Shell             | /usr/bin/zsh                                                               |
| PHP binary        | /usr/bin/php7.2                                                            |
| PHP version       | 7.2.14-1+ubuntu18.04.1+deb.sury.org+1                                      |
| php.ini used      | /etc/php/7.2/cli/php.ini                                                   |
| EE root dir       | phar://ee.phar                                                             |
| EE vendor dir     | phar://ee.phar/vendor                                                      |
| EE phar path      | /root                                                                      |
| EE packages dir   |                                                                            |
| EE global config  | /opt/easyengine/config/config.yml                                          |
| EE project config |                                                                            |
| EE version        | 4.0.10                                                                     |
+-------------------+----------------------------------------------------------------------------+

# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic

# docker version
Client:
 Version:           18.09.1
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        4c52b90
 Built:             Wed Jan  9 19:35:31 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.1
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       4c52b90
  Built:            Wed Jan  9 19:02:44 2019
  OS/Arch:          linux/amd64
  Experimental:     false

# docker-compose version
docker-compose version 1.23.2, build 1110ad01
docker-py version: 3.6.0
CPython version: 3.6.7
OpenSSL version: OpenSSL 1.1.0f  25 May 2017
@lucasff
Copy link

lucasff commented Mar 1, 2020

Also had the same issue and found out that the best way to solve this is creating a new docker image and using this one instead. https://hub.docker.com/r/lukeshard/nginx-proxy

@demyxco
Copy link
Author

demyxco commented Mar 1, 2020

@lucasff wow, I completely forgot I submitted an issue here a year ago and it's still open. I'm gonna close this because I left EE a long time ago and I wrote my own WordPress/Docker stack

@demyxco demyxco closed this as completed Mar 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants