• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue 10389#0: \996867 upstream sent too big header while reading response header from upstream

T

tomass

New Pleskian
i got a website which is built using CMS Made Simple and one section of the admin panel(CMSMS) i.e. Content>Pages section is throwing bad gateway error, the rest section the admin panel is working fine. And earlier before the 500 error, whenever i tried to create a page through Content>Pages it just directed me to admin login page!!
 
You must log in or register to reply here.

Similar threads

H
Resolved Laravel app "502 Bad Gateway" on page reload only
Replies
2
Views
4K
halnex
H
C
Resolved Website runs into a 504 Gateway Time-out after server restore
Replies
5
Views
7K
celebrir
C
A
Issue 502 Gateway error with HTTP POST Requests but not GET requests
Replies
3
Views
6K
Maarten
M
cipcip
Issue Error : upstream timed out (110: Connection timed out) while reading response header from upstream
Replies
3
Views
8K
Peter Debik
P
B
Issue Error upstream sent too big header
Replies
7
Views
7K
BNO
B
Back
Top