{"id":22632,"date":"2026-08-28T13:24:40","date_gmt":"2026-08-28T11:24:40","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&#038;p=22632"},"modified":"2026-08-28T13:24:41","modified_gmt":"2026-08-28T11:24:41","password":"","slug":"error-503-service-unavailable","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/webhosting-cpanel\/fehler-503-service-unavailable\/","title":{"rendered":"Fix 503 Service Unavailable"},"content":{"rendered":"<p class=\"wp-block-paragraph\">The error message <strong>503 Service Unavailable<\/strong> means that a server or service is currently unable to successfully process the request.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Unlike a classic 500 Internal Server Error, a 503 often indicates a <strong>temporary condition<\/strong> out. Possible causes include heavily utilized processes, an application in maintenance mode, faulty background tasks, or issues within a web application.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, we show you how to systematically investigate a 503 error in CURIAWEB web hosting and find out whether the cause lies in the application, PHP, WordPress, scheduled tasks, or resource usage.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> A 503 does not automatically mean that the entire hosting server is overloaded. First, check whether only your website, a specific function, or your hosting account is affected.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">What does 503 Service Unavailable mean?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The HTTP status code <code>503<\/code> belongs to the group of server-side HTTP errors.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Browser sends request\n        \u2193\nServer or application is reached\n        \u2193\nService cannot process request at the moment\n        \u2193\n503 Service Unavailable<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The word <strong>currently<\/strong> is important in this regard. A 503 is generally intended for situations where a service is temporarily unavailable.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What can a 503 error look like?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the application and server configuration, different messages may appear.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples are:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>503 Service Unavailable\n\nService Unavailable\n\nHTTP ERROR 503\n\nThe server is temporarily unable to service your request.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">An application can additionally display its own error or maintenance page.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">differentiate between 503, 500, 508 and 403<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For troubleshooting, it is important to note the status code actually displayed.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Status<\/th><th>Simply put, he<\/th><\/tr><\/thead><tbody><tr><td><code>403 Forbidden<\/code><\/td><td>Access denied<\/td><\/tr><tr><td><code>500 Internal Server Error<\/code><\/td><td>Server-side processing failed internally<\/td><\/tr><tr><td><code>503 Service Unavailable<\/code><\/td><td>Service cannot process request at the moment<\/td><\/tr><tr><td><code>508 Resource Limit Is Reached<\/code><\/td><td>a CloudLinux resource limit has been reached<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">In the event of a 500 error, you can find the appropriate procedure under <a href=\"\/en\/help\/web-hosting-cpanel\/fehler-500-internal-server-error\/\">Fixing a 500 Internal Server Error<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If expressly <code>508 Resource Limit Is Reached<\/code> is displayed, use <a href=\"\/en\/help\/web-hosting-cpanel\/resource-limit-is-reached\/\">Resource Limit Is Reached: Identify and Fix CloudLinux Limits<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">First determine how the 503 occurs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before changing settings, narrow down the symptom.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check in particular:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Is the entire website affected?<\/li>\n\n\n\n<li>Just a specific page or feature?<\/li>\n\n\n\n<li>Only the WordPress admin area?<\/li>\n\n\n\n<li>Just an import, export, or other process?<\/li>\n\n\n\n<li>Does the error occur permanently or only intermittently?<\/li>\n\n\n\n<li>Does it only appear under heavy load?<\/li>\n\n\n\n<li>Does he regularly occur at the same time?<\/li>\n\n\n\n<li>Did the problem start immediately after a change?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This information is particularly important for a 503 because the error often only occurs temporarily.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Note date, time, and URL<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For a 503 error, note the exact time if possible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>28.08.2026\n4:18 PM\nhttps:\/\/example.ch\/\n503 Service Unavailable<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If only a specific action is affected, note this as well.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Website normally accessible\n        \u2193\nStart product import\n        \u2193\n503 Service Unavailable<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The time allows for later comparison with error logs, CloudLinux resources, and scheduled tasks.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. Retest after a short time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Since a 503 may indicate a temporary condition, try accessing the website again after a short time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Distinguish between:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>503 only once\n\u2192 possibly short-term event\n\n503 regularly\n\u2192 look for recurring cause\n\n503 permanently\n\u2192 investigate specific fault or configuration<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A one-off error during an exceptional process does not necessarily have the same cause as a 503 that occurs multiple times every day.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3. Check whether only your website is affected<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A 503 on your domain does not prove that the entire hosting server is unavailable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The cause can lie within your own application or your hosting account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If cPanel is still accessible, you can start troubleshooting there immediately.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Briefly explained:<\/strong> \u201eService Unavailable\u201c describes the response to your specific request. From this alone, it cannot yet be deduced which technical level is causing the issue.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">4. Check cPanel Error Log<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Measured values \u2192 Errors<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compare the entries there with the time of the 503 error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to evaluate the messages under <a href=\"\/en\/help\/web-hosting-cpanel\/read-cpanel-error-log\/\">Read cPanel Error Log and find website errors<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pay special attention to messages that:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>were created at the same time<\/li>\n\n\n\n<li>name the affected domain or file<\/li>\n\n\n\n<li>point to PHP<\/li>\n\n\n\n<li>contain a plugin or theme path<\/li>\n\n\n\n<li>indicate a process or application error<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5. Check CloudLinux resource usage<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In the case of a sporadic 503, you should also check how your hosting account behaved at the time in question.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Metrics \u2192 Resource Usage<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the time period around the error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux can display information about the following resources, among others:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU<\/li>\n\n\n\n<li>Physical Memory<\/li>\n\n\n\n<li>I\/O<\/li>\n\n\n\n<li>IOPS<\/li>\n\n\n\n<li>Entry Processes<\/li>\n\n\n\n<li>Number of Processes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">You can find a detailed explanation at <a href=\"\/en\/help\/web-hosting-cpanel\/cloudlinux-resource-usage\/\">Understanding CloudLinux Resource Usage in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">503 is not automatically a CloudLinux limit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A temporal correlation with high resource usage can be important for the diagnosis. Nevertheless, a 503 must not automatically be equated with a reached CloudLinux limit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, check:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>503 occurred\n        \u2193\nCheck CloudLinux at the same time\n        \u2193\nLimit event present?\n        \u2193\nyes \u2192 investigate cause of resource usage\nno \u2192 continue checking other causes<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">6. Investigate high CPU usage<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the CPU usage is noticeably high at the time of the issue, you should find out which processes or applications are consuming the computing power.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Possible causes include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>many dynamic page views<\/li>\n\n\n\n<li>complex PHP processes<\/li>\n\n\n\n<li>Imports and exports<\/li>\n\n\n\n<li>Cron jobs<\/li>\n\n\n\n<li>WordPress background tasks<\/li>\n\n\n\n<li>WooCommerce processes<\/li>\n\n\n\n<li>inefficient plugins<\/li>\n\n\n\n<li>Bots or automated access<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">High CPU usage is initially just a metric. What matters is which process is causing it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7. Consider entry processes<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Many simultaneously or long-processed dynamic requests can increase the number of entry processes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can occur, for example, when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>many PHP requests are processed simultaneously<\/li>\n\n\n\n<li>individual requests take an unusually long time<\/li>\n\n\n\n<li>database processing is slow<\/li>\n\n\n\n<li>many bots call dynamic URLs<\/li>\n\n\n\n<li>multiple background processes are active in parallel<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">We explain in detail how CloudLinux limits and faults are connected at <a href=\"\/en\/help\/web-hosting-cpanel\/resource-limit-is-reached\/\">Resource Limit Is Reached: Identify and Fix CloudLinux Limits<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">8. Differentiating between Physical Memory and PHP Memory Limit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux Physical Memory and the PHP<code>memory_limit<\/code> are not the same.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PHP memory_limit\n\u2192 Memory limit of a PHP process\n\nCloudLinux Physical Memory\n\u2192 Memory usage of account processes in the LVE<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For example, if in the error log:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Allowed memory size of ... bytes exhausted<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">stands, you should investigate the PHP memory limit and the process causing it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">See on this <a href=\"\/en\/help\/web-hosting-cpanel\/set-php-limits\/\">Set PHP memory limit, upload size, and execution time<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9. Check PHP version<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the 503 started immediately after changing the PHP version, check the compatibility of the application.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At CURIAWEB, the PHP version of a domain is generally configured via:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Software \u2192 MultiPHP Manager<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">managed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find the instructions under <a href=\"\/en\/help\/web-hosting-cpanel\/change-php-version\/\">Change PHP version in cPanel<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not change the PHP version randomly. In particular, check whether the website, plugins, and themes support the version being used.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">10. Control PHP extensions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the error log shows references to missing functions or classes, a required PHP extension may be missing or unavailable in the PHP environment being used.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical notices can be:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Call to undefined function ...\n\nClass ... not found\n\nrequires ext-...<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">We explain the procedure under <a href=\"\/en\/help\/web-hosting-cpanel\/enable-php-extensions\/\">Enabling and Managing PHP Extensions in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">11. Check WordPress maintenance mode<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress can temporarily enter a maintenance state during updates.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the root directory of the WordPress installation, a file named:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>.Maintenance<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">be created.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Normally, WordPress removes this file again after the update has completed successfully.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress is stuck in maintenance mode<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If an update has been interrupted, the website may remain in maintenance mode under certain circumstances.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical notes are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Problem began during a WordPress, plugin, or theme update<\/li>\n\n\n\n<li>Instead of the website, a maintenance message appears<\/li>\n\n\n\n<li>is still located in the WordPress root directory <code>.Maintenance<\/code><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">To do this, open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Files \u2192 File Manager<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">and check the WordPress root directory.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Delete one <code>.Maintenance<\/code>Do not blindly delete files while an update is still actually in progress. First, check whether the update process has truly been canceled or completed.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">A maintenance message is not always a real HTTP 503<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An application can display its own maintenance page. Therefore, you should distinguish between the visible message and the HTTP status actually returned.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For practical troubleshooting, it is nevertheless crucial whether an update or maintenance action was performed immediately before.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">12. Inspect WordPress plugins<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a 503 only occurs on a WordPress website, plugins may be involved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check in particular whether the problem occurred immediately after:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Installation of a plugin<\/li>\n\n\n\n<li>Plugin update<\/li>\n\n\n\n<li>Enabling an extension<\/li>\n\n\n\n<li>Modifying a plugin configuration<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">begun.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the error log for any clues within:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>\/wp-content\/plugins\/<\/code><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Systematically narrowing down plugin conflicts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the cause is not clear, use our guide <a href=\"\/en\/help\/wordpress\/wordpress-plugin-theme-conflicts\/\">Identify and resolve WordPress plugin and theme conflicts<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not indiscriminately deactivate multiple components at the same time if there is already a specific suspicion.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">13. Consider WordPress theme<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A theme or custom theme code can also affect server-side processing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the error started immediately after a theme update or a change to the theme, check the error log for paths under:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>\/wp-content\/themes\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A corresponding path helps narrow the investigation down to the component in question.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">14. Use WordPress debugging<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the standard error log does not provide enough information, controlled WordPress debug logging can provide additional clues.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress can cause errors, for example, in:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-content\/debug.log<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">log.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to set this up securely at <a href=\"\/en\/help\/wordpress\/wordpress-debugging-fehlerprotokolle\/\">Using WordPress debugging and error logs<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Detailed error output should not be permanently displayed publicly on a production website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">15. Check WooCommerce background tasks<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WooCommerce and many WooCommerce extensions run background tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This may include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ordering processes<\/li>\n\n\n\n<li>Product imports<\/li>\n\n\n\n<li>Synchronizations<\/li>\n\n\n\n<li>Webhooks<\/li>\n\n\n\n<li>planned actions<\/li>\n\n\n\n<li>Tasks of payment or shipping plugins<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, if the 503 only occurs with one online shop, you shouldn't look exclusively at the public website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Consider Action Scheduler<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WooCommerce and numerous plugins use the Action Scheduler for scheduled background tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If a large number of pending or repeatedly failing tasks have accumulated there, this can contribute to increased background activity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, in the case of recurring problems, you should check whether the timing of the 503 coincides with such tasks.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">503 only during checkout<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the store works in principle, but only the checkout is affected, focus the diagnosis on this dynamic process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check in particular:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>WooCommerce logs or application errors<\/li>\n\n\n\n<li>Payment plugins<\/li>\n\n\n\n<li>Shipping and tax extensions<\/li>\n\n\n\n<li>external API connections<\/li>\n\n\n\n<li>Error Log<\/li>\n\n\n\n<li>Simultaneous resource utilization<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A checkout should not simply be \u201erepaired\u201c through aggressive full-page caching.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">16. Consider external services<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Web applications frequently communicate with external services.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Payment service provider<\/li>\n\n\n\n<li>Shipping services<\/li>\n\n\n\n<li>ERP systems<\/li>\n\n\n\n<li>CRM systems<\/li>\n\n\n\n<li>external APIs<\/li>\n\n\n\n<li>License or update server<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If an application is waiting for an external response or does not properly handle an error from that service, it can also affect your own website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, in the event of an error that only occurs with a specific function, check which external systems are involved in that function.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check cron jobs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the 503 occurs regularly at the same time, cron jobs are an important checkpoint.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Advanced Options \u2192 Cronjobs<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check which tasks are started at the relevant time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain the diagnosis of faulty tasks under <a href=\"\/en\/help\/web-hosting-cpanel\/cron-job-is-not-working\/\">Cron job not working: Causes and solutions<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Multiple tasks at the same time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An unfavorable schedule can lead to several complex tasks being executed simultaneously.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>03:00 \u2192 Backup\n03:00 \u2192 Product import\n03:00 \u2192 Synchronization\n03:00 \u2192 Data export<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the applications allow for it, staggering the timing can be useful.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, do not change any tasks specified by an application without knowing their function.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">18. Search for recurring time pattern<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A 503 error that appears at roughly the same time every day provides a valuable clue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compare:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Time of the 503\n        \u2193\nCron jobs\n        \u2193\nWordPress Scheduled Tasks\n        \u2193\nWooCommerce Action Scheduler\n        \u2193\nBackups \/ Imports \/ Exports\n        \u2193\nCloudLinux Resources<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If several of these events coincide in time, the cause can be narrowed down much better.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">19. Examine imports and exports<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Large import and export operations can consume significant resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the application, this can:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU<\/li>\n\n\n\n<li>RAM<\/li>\n\n\n\n<li>I\/O<\/li>\n\n\n\n<li>Database<\/li>\n\n\n\n<li>PHP processes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">be heavily strained.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the 503 occurs exclusively during a large import, check whether the application supports processing in smaller batches.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">20. Factor in backups as a time element<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Backup processes can also temporarily consume CPU and file operations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This does not mean that a backup is automatically the cause of a 503.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, if the error occurs regularly and precisely during a backup process, this correlation should be investigated.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check for bots and automated access<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A sudden increase in automated traffic can generate many dynamic requests.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This may include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>search engine crawler<\/li>\n\n\n\n<li>SEO crawler<\/li>\n\n\n\n<li>Monitoring services<\/li>\n\n\n\n<li>automated scanners<\/li>\n\n\n\n<li>Content Crawler<\/li>\n\n\n\n<li>unwanted bots<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If the 503 coincides with unusual traffic, you should check the access logs under <strong>Measurements<\/strong> consider.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">High traffic alone does not prove overload<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Many visitors can increase the resource requirements. However, how efficiently the individual requests are processed is also crucial.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>many fast requests\n\u2192 processes are released quickly\n\nfewer, but very slow requests\n\u2192 processes remain active longer<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, in the case of a 503, both the number of visitors and the application itself should be investigated.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">22. Check AccelerateWP and caching<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In WordPress, suitable caching can reduce the number of dynamically processed requests.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CURIAWEB provides AccelerateWP, a WordPress-oriented optimization solution within the hosting environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find more information at <a href=\"\/en\/help\/web-hosting-cpanel\/acceleratewp-erklaert\/\">AccelerateWP in cPanel explained<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Caching is not a universal 503 solution<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Caching is especially helpful for recurring frontend calls, but it does not automatically solve:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>faulty PHP processes<\/li>\n\n\n\n<li>broken cron jobs<\/li>\n\n\n\n<li>Checkout issues<\/li>\n\n\n\n<li>Import error<\/li>\n\n\n\n<li>external API issues<\/li>\n\n\n\n<li>faulty plugins<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, do not install multiple cache plugins just because a 503 occurs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">23. Check storage space<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When applications need to write files, generate caches, perform updates, or create temporary files, a completely full hosting storage can cause additional problems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, check the available storage space if corresponding symptoms occur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find the instructions under <a href=\"\/en\/help\/web-hosting-cpanel\/check-storage-space-and-bandwidth\/\">Check disk space and bandwidth in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">24. Consider database issues<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If an application performs very long-running or erroneous database operations, server-side processes can remain active for a correspondingly long time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the error log and application-specific logs before making any changes to the database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not delete or modify any tables on suspicion.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">25. 503 after plugin update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the error started immediately after a plugin update, check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Error Log<\/li>\n\n\n\n<li>Plugin compatibility<\/li>\n\n\n\n<li>PHP compatibility<\/li>\n\n\n\n<li>new background tasks<\/li>\n\n\n\n<li>resource behavior<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If the error is reproducibly related to the extension in question, it should be investigated specifically.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">26. 503 after PHP change<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the website throws a 503 error only after a PHP version change, check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Application compatibility<\/li>\n\n\n\n<li>Plugins and Themes<\/li>\n\n\n\n<li>required PHP extensions<\/li>\n\n\n\n<li>Error Log<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A controlled switch back to the previously working and still suitable PHP version can be useful as a diagnostic step.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">27. 503 after website migration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the error occurs immediately after a hosting migration, check in particular:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PHP version<\/li>\n\n\n\n<li>PHP extensions<\/li>\n\n\n\n<li>PHP settings<\/li>\n\n\n\n<li>Cron jobs<\/li>\n\n\n\n<li>WordPress background tasks<\/li>\n\n\n\n<li>Cache configuration<\/li>\n\n\n\n<li>Database connection<\/li>\n\n\n\n<li>external services<\/li>\n\n\n\n<li>Error Log<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A migration can reveal differences between two hosting environments that were not noticed before.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">28. 503 only for certain URLs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the home page works, but only certain URLs generate a 503, focus the diagnosis on the processing of those pages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>which plugin provides the function<\/li>\n\n\n\n<li>whether external APIs are used<\/li>\n\n\n\n<li>whether a complex database query is performed<\/li>\n\n\n\n<li>whether the error is reproducible<\/li>\n\n\n\n<li>which error log entry is generated as a result<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A general domain or DNS problem is then less likely.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">29. 503 only in WordPress backend<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the frontend works, but the admin area or a specific administration function is affected, check in particular:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Plugins<\/li>\n\n\n\n<li>Background tasks<\/li>\n\n\n\n<li>PHP error<\/li>\n\n\n\n<li>Import or export processes<\/li>\n\n\n\n<li>Resource usage<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Many backend actions are dynamic and do not benefit in the same way from frontend caching.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">30. 503 only under load<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the website works during normal operation and the error only occurs during increased usage, you should look at the CloudLinux resources and the application together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>which resource limit is conspicuous<\/li>\n\n\n\n<li>whether faults are present<\/li>\n\n\n\n<li>which URLs are frequently accessed<\/li>\n\n\n\n<li>how long dynamic requests take<\/li>\n\n\n\n<li>whether caching is used sensibly<\/li>\n\n\n\n<li>whether bots are involved<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">31. 503 without conspicuous CloudLinux metrics<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If there are no matching resource events at the time of the error, you should not continue to assume a resource issue just because the message is \u201eService Unavailable\u201c.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check instead:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Error Log<\/li>\n\n\n\n<li>Application error<\/li>\n\n\n\n<li>WordPress or WooCommerce<\/li>\n\n\n\n<li>external services<\/li>\n\n\n\n<li>Maintenance states<\/li>\n\n\n\n<li>recent changes<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> Readings are valuable for diagnosis because they can also refute a hypothesis. If no resource limit was reached at the time of the error, you should expand your troubleshooting accordingly.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">32. 503 occurred only once<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a 503 has occurred once during an exceptional operation and cannot be reproduced, document the event first.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples can be:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>one-time large import<\/li>\n\n\n\n<li>Update<\/li>\n\n\n\n<li>short-term background task<\/li>\n\n\n\n<li>unusual traffic spike<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A single event does not automatically justify extensive changes to an otherwise stable website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">33. 503 occurs regularly<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A recurring 503, on the other hand, should be systematically investigated.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Particularly valuable are:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>exact time\n+\nError Log\n+\nCloudLinux resources\n+\nCron jobs\n+\nWordPress\/WooCommerce background tasks\n+\nTraffic<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The more of this information that can be brought together in time, the more reliably the cause can be determined.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not change all settings at once<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you simultaneously:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>switching PHP\ndeactivating plugins\nchanging cron jobs\nreconfiguring the cache\nincreasing PHP limits<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">and the error subsequently disappears, the cause remains unknown.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, proceed in a controlled manner:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Reproduce error\n        \u2193\nCheck measured values and logs\n        \u2193\nFormulate hypothesis\n        \u2193\nMake a targeted change\n        \u2193\nTest again<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Measure again after a change<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For example, if you have corrected a problematic process, do not just check afterwards whether the website is working again.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compare resource values and logs as well.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Before:\n503 daily at 03:00\nCPU and EP anomalies at the same time\n\nCause:\nmultiple complex tasks start simultaneously\n\nChange:\ntasks distributed in time in a controlled manner\n\nAfter:\nno 503\nno corresponding faults<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This gives you much better evidence that the change was actually relevant.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Systematically diagnose 503 Service Unavailable<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Note domain, URL, date, and exact time.<\/li>\n\n\n\n<li>Check whether the error is permanent or only temporary.<\/li>\n\n\n\n<li>Determine whether the entire website or only one feature is affected.<\/li>\n\n\n\n<li>Check <strong>Measured values \u2192 Errors<\/strong>.<\/li>\n\n\n\n<li>Compare the error log with the time of the 503.<\/li>\n\n\n\n<li>Open <strong>Metrics \u2192 Resource Usage<\/strong>.<\/li>\n\n\n\n<li>Check CloudLinux values and possible faults at the same time.<\/li>\n\n\n\n<li>Check recent changes.<\/li>\n\n\n\n<li>Check PHP version and, if applicable, PHP extensions.<\/li>\n\n\n\n<li>Check WordPress plugins, themes, and maintenance status.<\/li>\n\n\n\n<li>Consider background tasks and scheduled actions in WooCommerce.<\/li>\n\n\n\n<li>Check cron jobs and recurring processes.<\/li>\n\n\n\n<li>Compare the error with imports, exports, and backups.<\/li>\n\n\n\n<li>Take into account unusual traffic and bots.<\/li>\n\n\n\n<li>Check external services if only a specific function is affected.<\/li>\n\n\n\n<li>Change only one possible cause at a time.<\/li>\n\n\n\n<li>Test again and then compare logs and measured values.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Quick diagnosis based on fault pattern<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Error pattern<\/th><th>First checkpoint<\/th><\/tr><\/thead><tbody><tr><td>503 after WordPress update<\/td><td>Check maintenance status, error log, and update<\/td><\/tr><tr><td>503 after plugin update<\/td><td>Check plugin and error log<\/td><\/tr><tr><td>503 after PHP change<\/td><td>Check PHP compatibility and extensions<\/td><\/tr><tr><td>503 daily at the same time<\/td><td>Check cron jobs and background tasks<\/td><\/tr><tr><td>503 only under high load<\/td><td>Check CloudLinux resources and application<\/td><\/tr><tr><td>503 only during import<\/td><td>Check PHP, resources, and import process<\/td><\/tr><tr><td>503 only during WooCommerce checkout<\/td><td>Check WooCommerce, plugins, external services and logs<\/td><\/tr><tr><td>503 without resource anomalies<\/td><td>Check application, logs, and external dependencies<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">What you should not do during a 503<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid in particular:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>automatically assume an overload of the entire server<\/li>\n\n\n\n<li>Significantly increase PHP limits without diagnosis<\/li>\n\n\n\n<li>Switch PHP versions randomly<\/li>\n\n\n\n<li>delete multiple plugins at once<\/li>\n\n\n\n<li>disable all cronjobs<\/li>\n\n\n\n<li>install multiple cache systems<\/li>\n\n\n\n<li>modifying database tables on suspicion<\/li>\n\n\n\n<li>Modify DNS records without corresponding notice<\/li>\n\n\n\n<li>perform multiple technical changes simultaneously<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Basic rule:<\/strong> A 503 initially describes a temporarily unavailable processing. The actual diagnosis only emerges through the combination of the timestamp, error log, resource usage, and the application or task currently being executed.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">When should you contact CURIAWEB support?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the 503 occurs regularly, persists permanently, or the cause cannot be clearly determined, document the problem as precisely as possible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Particularly helpful are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>affected domain<\/li>\n\n\n\n<li>full URL<\/li>\n\n\n\n<li>Date and exact time<\/li>\n\n\n\n<li>visible error message<\/li>\n\n\n\n<li>whether the entire website or only a specific function is affected<\/li>\n\n\n\n<li>whether the error occurs permanently or sporadically<\/li>\n\n\n\n<li>relevant error log entries<\/li>\n\n\n\n<li>CloudLinux metrics or faults at the same time<\/li>\n\n\n\n<li>currently used PHP version<\/li>\n\n\n\n<li>recent changes<\/li>\n\n\n\n<li>running cron jobs, imports, or background tasks<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If the error is reproducible, also describe the exact steps that can be used to trigger it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A <strong>503 Service Unavailable<\/strong> means that a server or service is currently unable to successfully process the request. This message does not automatically mean that the entire hosting server is overloaded.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First note the exact time and then check the cPanel error log and CloudLinux resource usage. This will allow you to determine whether the error coincides with an application, a PHP process, a resource event, or a specific background task.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With WordPress, you should particularly consider updates, maintenance states, plugins, themes, and background tasks. With WooCommerce, dynamic processes such as checkout, scheduled actions, imports, synchronizations, and external services are added.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the error regularly occurs at the same time, cron jobs and other recurring tasks are particularly important diagnostic points. If, on the other hand, it only occurs under load, you should examine CloudLinux resources, traffic, and the application's processing speed together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not change multiple components simultaneously. Reproduce the issue, check logs and metrics, form a concrete hypothesis, and then test a targeted change.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The most important rule is: <strong>\u201e503 Service Unavailable\u201c means that a request cannot be processed at the moment \u2013 timestamps, logs, and metrics show you why.<\/strong><\/p>","protected":false},"excerpt":{"rendered":"<p>Die Fehlermeldung 503 Service Unavailable bedeutet, dass ein Server beziehungsweise Dienst die Anfrage momentan nicht erfolgreich verarbeiten kann. Im Gegensatz zu einem klassischen 500 Internal Server Error deutet ein 503 h\u00e4ufig auf einen vor\u00fcbergehenden Zustand hin. M\u00f6gliche Ursachen sind beispielsweise stark beanspruchte Prozesse, eine Anwendung im Wartungszustand, fehlerhafte Hintergrundaufgaben oder Probleme innerhalb einer Webanwendung. In [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[78],"doc_tag":[],"class_list":["post-22632","docs","type-docs","status-publish","hentry","doc_category-webhosting-cpanel"],"year_month":"2026-09","word_count":3247,"total_views":"7","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"Webhosting &amp; cPanel","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/webhosting-cpanel\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22632","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=22632"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22632\/revisions"}],"predecessor-version":[{"id":22634,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22632\/revisions\/22634"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22632"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22632"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22632"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}