NS8 Wordpress upload size limit

Support
, ,
1

NethServer Version: NS8
Module: Wordpress

Hi Everyone,

I have a fresh install of NS8 on a Rocky linux as per documentation.
I have installed Wordpress successfully and now am trying to import a backup from another server.
The issue i am facing is that the backup is around 1GB large, and the upload limitation by default is set to 256M.
I have tried to increase the limit as per documentation, but it does not take effect:

“To modify php settings go to /home/wordpress1/.config/state/config/uploads.ini and adjust your settings, your modifications are included inside the backup”

I have tried to save the wordpress settings and also rebooted the server, but the upload limit of 256 remains on wordpress.

The logs do only record 2 error/fail while i am saving the wordpress settings, but this does not tell me anything nor am i sure it is even relevant:

2025-03-24T19:30:18Z [1:wordpress1:systemd] Stopped Podman mariadb-app.service.
2025-03-24T19:30:18Z [1:wordpress1:systemd] Stopping Podman wordpress.service…
2025-03-24T19:30:18Z [1:wordpress1:systemd] Removed slice cgroup user-libpod_pod_f2e52de8507cd5bc5f5132cb6831217b7c67ff56448bd447c432d1bf394aec4d.slice.
2025-03-24T19:30:18Z [1:wordpress1:systemd] user-libpod_pod_f2e52de8507cd5bc5f5132cb6831217b7c67ff56448bd447c432d1bf394aec4d.slice: Consumed 1.934s CPU time.
2025-03-24T19:30:18Z [1:wordpress1:podman] wordpress
2025-03-24T19:30:18Z [1:wordpress1:systemd] user-libpod_pod_f2e52de8507cd5bc5f5132cb6831217b7c67ff56448bd447c432d1bf394aec4d.slice: Failed to open /run/user/1004/systemd/transient/user-libpod_pod_f2e52de8507cd5bc5f5132cb6831217b7c67ff56448bd447c432d1bf394aec4d.slice: No such file or directory
2025-03-24T19:30:18Z [1:wordpress1:podman] f2e52de8507cd5bc5f5132cb6831217b7c67ff56448bd447c432d1bf394aec4d
2025-03-24T19:30:18Z [1:wordpress1:systemd] Stopped Podman wordpress.service.
2025-03-24T19:30:18Z [1:wordpress1:systemd] Starting Podman wordpress.service…
2025-03-24T19:30:18Z [1:wordpress1:systemd] Created slice cgroup user-libpod_pod_d6f7bef6fb749defb704928c023c14c8ae611f73e779bce0aa87a0e565699ff7.slice.
2025-03-24T19:30:18Z [1:wordpress1:podman] d6f7bef6fb749defb704928c023c14c8ae611f73e779bce0aa87a0e565699ff7
2025-03-24T19:30:18Z [1:wordpress1:systemd] Started libcrun container.

2025-03-24T19:30:18Z [1:wordpress1:mariadb-app] 2025-03-24 19:30:18+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2025-03-24T19:30:18Z [1:traefik1:traefik] 192.168.1.182 - - [24/Mar/2025:19:30:18 +0000] “GET /cluster-admin/api/cluster/task/1dfdbcff-59d8-433e-9764-7b1edcdd5790/context HTTP/2.0” 200 239 “-” “-” 519 “cluster-admin-https@file” “http://127.0.0.1:9311” 16ms
2025-03-24T19:30:18Z [1:wordpress1:mariadb-app] 2025-03-24 19:30:18+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.11+maria~ubu2204 started.
2025-03-24T19:30:18Z [1:wordpress1:wordpress1] error: ‘Can’t connect to server on ‘localhost’ (111)’
2025-03-24T19:30:18Z [1:wordpress1:wordpress1] amysqladmin: connect to server at ‘localhost’ failed
2025-03-24T19:30:18Z [1:wordpress1:wordpress1] Check that mariadbd is running and that the socket: ‘/run/mysqld/mysqld.sock’ exists!
2025-03-24T19:30:18Z [1:wordpress1:agent@wordpress1] task/module/wordpress1/42211ae8-c197-4d6b-92a9-96e44cd6f87a: action “get-configuration” status is “completed” (0) at step validate-output.json
2025-03-24T19:30:18Z [1:wordpress1:mariadb-app] 2025-03-24 19:30:18+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2025-03-24T19:30:18Z [1:traefik1:traefik] 192.168.1.182 - - [24/Mar/2025:19:30:18 +0000] “GET /cluster-admin/api/module/wordpress1/task/42211ae8-c197-4d6b-92a9-96e44cd6f87a/context HTTP/2.0” 200 288 “-” “-” 522 “cluster-admin-https@file” “http://127.0.0.1:9311” 3ms
2025-03-24T19:30:18Z [1:traefik1:traefik] 192.168.1.182 - - [24/Mar/2025:19:30:18 +0000] “GET /cluster-admin/api/module/wordpress1/task/42211ae8-c197-4d6b-92a9-96e44cd6f87a/context HTTP/2.0” 200 288 “-” “-” 523 “cluster-admin-https@file” “http://127.0.0.1:9311” 4ms
2025-03-24T19:30:18Z [1:traefik1:traefik] 192.168.1.182 - - [24/Mar/2025:19:30:18 +0000] “GET /cluster-admin/api/module/wordpress1/task/42211ae8-c197-4d6b-92a9-96e44cd6f87a/status HTTP/2.0” 200 182 “-” “-” 524 “cluster-admin-https@file” “http://127.0.0.1:9311” 3ms
2025-03-24T19:30:18Z [1::agent@cluster] task/cluster/ab30fa36-d58a-4e36-aff9-1f02176c8471: action “list-backup-repositories” status is “completed” (0) at step validate-output.json

The output of the config file:

image
image727×312 78.5 KB

Could anyone suggest any further steps?

2

The post_max_size needs to be adapted too like

memory_limit=1024M
upload_max_filesize=1024M
post_max_size =1024M

EDIT:

I also added memory_limit as @michelandre recommended.

3

Salut @Ruaraidh and @mrmarkuz

It is absolutely essential to respect the relationships between these 3 parameters.

memory_limit > post_max_size > upload_max_filesize

In your case, the limit you have to increase is upload_max_filesize.
You must adjust the other two parameters accordingly.

Michel-André

upload_max_filesize
(PHP: Integers - Manual) => PHP: Description of core php.ini directives - Manual.

post_max_size.
PHP: Description of core php.ini directives - Manual.

memory_limit
PHP: Description of core php.ini directives - Manual.

2 Likes
4

Thanks, the upload is working without increasing the memory_limit but as it seems recommended I changed my post accordingly.

1 Like