Scenario Description
JumpServer's default file upload size is set to 4GB. This article mainly describes how to modify the default file upload size and timeout settings.
Note: If deployed in a cluster, each node needs to be updated.
Configuration Description
File Size Limitations
Modify the parameter <CLIENT_MAX_BODY_SIZE=4096m> in the JumpServer configuration file to set the default file upload size limit.
vi /opt/jumpserver/config/config.txt
# Nginx File Upload and Download Size Limit
#
CLIENT_MAX_BODY_SIZE=4096m
Restart the JumpServer service to take effect
jmsctl restart
Timeout Configuration
Timeouts can be configured differently based on the system platform of the assets, such as koko and lion.
Linux Timeout
Login to the backend server of JumpServer to perform operations.
# Enter the jms_web container
docker exec -it jms_web /bin/bash
# Modify the routing file
vi /etc/nginx/conf.d/default.conf
# Modify the content in location /koko/
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 6000; (The units above are in seconds, and can be set according to your needs.)
# Save the changes
# Check the Nginx syntax
nginx -t
# Reload the configuration to take effect
nginx -s reload
At this point, the timeout setting has been modified. After successful testing, you can map this file to the host for persistence.
Windows Timeout
Login to the backend server of JumpServer to perform operations.
# Enter the jms_web container
docker exec -it jms_web /bin/bash
# Modify the routing file
vi /etc/nginx/conf.d/default.conf
# Modify the content in location /lion/
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 6000; (The units above are in seconds, and can be set according to your needs.)
# Save the changes
# Check the Nginx syntax
nginx -t
# Reload the configuration to take effect
nginx -s reload
At this point, the timeout setting has been modified. After successful testing, you can map this file to the host for persistence.