• 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.

Issue ApolloError | Message Response not successful: Received status code 413

JALAL ROOMI

New Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
18.0.66 #2

Plesk Obsidian 18.0.66 Update #2 Web Pro Edition​


OS Ubuntu 22.04.5 LTS
View attachment 27724
i have trouble the attached error please help me to resolve this issueScreenshot 2025-01-14 182250.jpg
 
What happens if you reload the page? What happens if you go back to the main page? Where are you getting this? There's a lot of factors and not enough information provided. HTTP error 413 means that the content is too large. If the panel is behind a proxy such as with cloudflare I could see this happening. But need more information to properly know how to properly guide you. If this is just from plesk itself you can throw the kitchen sink at it and try repairing the installation by running the following command in a terminal shell:

Bash:
plesk repair installation
 
i also run the above command but still same issue

Bootstrapper repair finished.
If problems persist, please check installer logs ('/var/log/plesk/install/plesk_18.0.66_repair.log' and '/var/log/plesk/install/plesk_18.0.66_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Plesk support.
 
And are you still having issues? Are you behind a proxy such as Cloudflare? If so did you tried going to the panel directly via the https://ip:8443 and see if you're able to access the page just fine?

If you've tried everything above and you're still getting that issue, you'll want to open a ticket with Plesk Support (if you've bought your license directly from Plesk) or from the provider you've bought the license from. You can read more about it over at https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk
 
ApolloError usually indicates that the JS script was not able to properly execute. If you haven't already, please try clearing the browser cache or test it using another browser. If the issue still persists, it will be best to submit a ticket as suggested by @scsa20
 
Back
Top