• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Request-URI Too Long (Apache)

LionKing

Regular Pleskian
Server operating system version
Linux server (Ubuntu)
Plesk version and microupdate number
Plesk Obsidian Web Host Edition Version 18.0.58 Update #2
Hello.
In our CRM system we are receiving this error:
1708618591658.png
Basically it stems from that we have a lot text in a leads description field which obviously organically grows a lot as the sales reps fill out information about a client prospect and record the history of the calls and conversation they have with a prospect. Now it seems we reached the limit and now in some leads sales reps are denied by the server to save more information in the lead description field...

So how can we increase the allowed data size on our Plesk server / domain hotel were we run our CRM system?

Thanks in advance.
Kind regards
 
You can try to add two lines to the Apache "additional directives" sections http and https in the "Apache and Nginx Settings":
LimitRequestLine 16380
LimitRequestFieldSize 16380
(or a bigger number)
 
You can try to add two lines to the Apache "additional directives" sections http and https in the "Apache and Nginx Settings":
LimitRequestLine 16380
LimitRequestFieldSize 16380
(or a bigger number)
What numbers would you recommend for a CRM system @Peter Debik ?
Obviously as the nature of CRMs is; they contain a lot of prospect/customer data which grows over time as sales reps enters sales/customer data into it..
 
I have no recommendation here. it's kind of odd in the first place that an application creates URIs that burst the default limits.
 
Hmm.. that doesn't seem to take any effect. I did restart the whole server to make sure the configurations are reread and applied.

Thoughts @Peter Debik

Thanks in advance.
 
Back
Top