• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question HTTP 413 error with Ubuntu Apache/SVN

MarkGorst

New Pleskian
Server operating system version
Ubuntu 24.04.1 LTS
Plesk version and microupdate number
Obsidian v18.0.66_build1800250106.19 os_Ubuntu 24.04
There are similar threads but none seem to address my specific problem. I have an Ubuntu 24.04.1 LTS server which is configured as an Apache/SVN server. All worked fine until installing Plesk Obsidian v18.0.66_build1800250106.19 os_Ubuntu 24.04. If I now submit a file larger than 1Mb to the SVN server I get "Unexpected HTTP status 413 'Request Entity Too Large'" error.

Somewhere there is a configuration limit - but I can't work out where. php.ini has it set at 2Gb.

Some solutions suggest going through the "Domains" menu - this is not a webserver, it's an SVN repository and just uses the IP address, not a domain name, so I can't follow that route.

I have found many similar issues, but none quite have the fix I require.

Can you direct me to the setting I need to modify to either increase or remove the file upload size limit please.
 
The main problem here is installing and configuring Apache SVN before installing Plesk. Plesk utilizes both Apache and Nginix to control the web sites so a lot of the configs you've originally had for your SVN would had been overwritten quite a bit. It's usually best to either install Plesk first then add a new Apache config in /etc/apache2/conf-available and/or /etc/apache2/sites-available or better yet keep the 2 services completely separated on 2 different servers.

In either case, you'll need to make a new config in /etc/apache2/conf-available then to enable the config you can either do a2enconf newConfigFile or make a symbolic link to it to /etc/apache2/conf-enabled (or you can just make the conf directly in /etc/apache2/conf-enabled but that isn't proper).

You can refer to (Plesk for Linux) Apache and Nginx Configuration Files for more information about files locations (replace httpd with apache2 since you're using a Debian based OS and not RHEL and so you'll need to double check the path of everything as well).
 
Back
Top