[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"doc-en-website-error-logs-plesk":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":21,"docGroup":28,"docGroupIcon":28,"link_fr":29,"bodyHtml":30},"\u002Fdocs\u002Fen\u002Fcloud\u002Fhebergement-web\u002Fwebsite-error-logs-plesk","website-error-logs-plesk","How to Read the Error Logs of Your Website on Plesk","Find the cause of a 500 error or a blank page in your website logs on Winheberg Plesk web hosting, filters, real-time tracking and common PHP messages.","cloud","hebergement-web","tabler:file-text","2026-11-02","Winheberg",147,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fwebsite-error-logs-plesk.webp",[16,17,18,19,20],"Logs","500 Error","PHP","Plesk","Web Hosting",[22,23,24,25,26,27],"500 error","blank page","error logs","plesk error_log","php logs","website debugging","","\u002Fdocs\u002Fhebergement-web\u002Fjournaux-erreurs-site-plesk","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>A 500 error, a blank page or a form that no longer sends almost always has a cause written in plain text in the server logs. Reading them is the first reflex before changing anything.\u003C\u002Fp>\n\u003Cp>On your \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fcloud\u002Fweb-hosting\">Winheberg web hosting\u003C\u002Fa>, Plesk gathers the logs of each domain on a single page, with filters by type, date and keyword, and real-time tracking.\u003C\u002Fp>\n\u003Cp>This guide shows you how to open these logs, find the right line and interpret the most frequent messages.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The Winheberg Plesk panel is displayed in French. Menu, field and button names are quoted below exactly as they appear on screen, followed by their English meaning.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A Winheberg web hosting plan with access to the Plesk panel\u003C\u002Fli>\n\u003Cli>The approximate time the error occurred\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>1. Open the domain logs\u003C\u002Fh2>\n\u003Cp>In \u003Cstrong>Sites Web &amp; Domaines\u003C\u002Fstrong> (\u003Cem>Websites &amp; Domains\u003C\u002Fem>), open your domain. In the \u003Cstrong>Tableau de bord\u003C\u002Fstrong> (\u003Cem>Dashboard\u003C\u002Fem>), \u003Cstrong>Outils Dévelop.\u003C\u002Fstrong> (\u003Cem>Dev Tools\u003C\u002Fem>) section, click \u003Cstrong>Journaux\u003C\u002Fstrong> (\u003Cem>Logs\u003C\u002Fem>).\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fwebsite-error-logs-plesk-1793616260335-cd68d02050a79cf4ae23e939.webp\" alt=\"Logs page of a domain in Plesk with its filters\" width=\"800\" \u002F>\n\n\u003Cp>Each line shows the \u003Cstrong>Date\u003C\u002Fstrong>, the \u003Cstrong>Type\u003C\u002Fstrong>, the visitor \u003Cstrong>IP\u003C\u002Fstrong>, the response \u003Cstrong>Code\u003C\u002Fstrong>, the \u003Cstrong>Message\u003C\u002Fstrong> and the \u003Cstrong>Source\u003C\u002Fstrong>, meaning the original log.\u003C\u002Fp>\n\u003Ch2>2. Choose the logs to display\u003C\u002Fh2>\n\u003Cp>At the top right, the \u003Cstrong>Tous les journaux\u003C\u002Fstrong> (\u003Cem>All logs\u003C\u002Fem>) list lets you tick the logs to display.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fwebsite-error-logs-plesk-1793616260640-f319eec7aa9e787cab7d3378.webp\" alt=\"Apache error, Apache access and Nginx log list in Plesk\" width=\"360\" \u002F>\n\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Available logs\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Log\u003C\u002Fth>\n\u003Cth>What it contains\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Erreur Apache (\u003Cem>Apache error\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>Web server and PHP errors, the most useful for a 500 error\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Accès Apache (\u003Cem>Apache access\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>Every page requested over HTTP, with its response code\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Accès SSL\u002FTLS Apache (\u003Cem>Apache SSL\u002FTLS access\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>Every page requested over HTTPS\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Erreur Nginx (\u003Cem>Nginx error\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>Errors of the front-end server, useful when \u003Cstrong>Erreur Apache\u003C\u002Fstrong> shows nothing\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Accès Nginx and Accès SSL\u002FTLS Nginx (\u003Cem>Nginx access\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>Requested pages, as seen by the front-end server\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>3. Find the right line\u003C\u002Fh2>\n\u003Cp>For a 500 error, keep only the error logs ticked, then choose the \u003Cstrong>error\u003C\u002Fstrong> type in the list under the toolbar and the period when the error occurred.\u003C\u002Fp>\n\u003Cp>The \u003Cstrong>IP\u003C\u002Fstrong>, \u003Cstrong>Code\u003C\u002Fstrong> and \u003Cstrong>Message\u003C\u002Fstrong> fields filter on a keyword. Enter \u003Ccode>500\u003C\u002Fcode> in \u003Cstrong>Code\u003C\u002Fstrong>, for instance, or a file name in \u003Cstrong>Message\u003C\u002Fstrong>, then click \u003Cstrong>Appliquer\u003C\u002Fstrong> (\u003Cem>Apply\u003C\u002Fem>).\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 16v-4\"\u002F>\u003Cpath d=\"M12 8h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>Click \u003Cstrong>Lancer les mises à jour en temps réel\u003C\u002Fstrong> (\u003Cem>Start real-time updates\u003C\u002Fem>), then reproduce the error in another tab. The matching line shows up right away, with no searching.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>4. Interpret frequent messages\u003C\u002Fh2>\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Common messages and leads\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Message\u003C\u002Fth>\n\u003Cth>Likely cause\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Ccode>PHP Fatal error: Allowed memory size of [N] bytes exhausted\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The script exceeded the allowed memory, raise \u003Ccode>memory_limit\u003C\u002Fcode> in \u003Cstrong>Paramètres PHP\u003C\u002Fstrong> (\u003Cem>PHP Settings\u003C\u002Fem>)\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PHP Fatal error: Maximum execution time of [N] seconds exceeded\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The script ran too long, raise \u003Ccode>max_execution_time\u003C\u002Fcode> in \u003Cstrong>Paramètres PHP\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PHP Fatal error: Uncaught Error: Call to undefined function\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A function does not exist in the PHP version in use, check the version your application requires\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PHP Parse error: syntax error\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A syntax error in a PHP file, the path and line are given in the message\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>AH01630: client denied by server configuration\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A rule of an \u003Ccode>.htaccess\u003C\u002Fcode> file blocks access\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003Cdiv class=\"md-table__footer\">Values in brackets depend on your website.\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>The file path quoted in the message points you to the culprit, for instance a WordPress plugin in \u003Ccode>wp-content\u002Fplugins\u002F\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch2>5. Read your application logs\u003C\u002Fh2>\n\u003Cp>Some applications write their errors to their own files, on top of the server logs.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress writes to \u003Ccode>wp-content\u002Fdebug.log\u003C\u002Fcode> when the logging of its debug mode is on, set from the settings icon next to \u003Cstrong>Débogage\u003C\u002Fstrong> (\u003Cem>Debugging\u003C\u002Fem>) on the website card, see our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fhost-wordpress-plesk\">How to Host a WordPress Website on Plesk\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Laravel writes to \u003Ccode>storage\u002Flogs\u002Flaravel.log\u003C\u002Fcode>, see our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fhost-laravel-plesk\">How to Host a Laravel Website on Plesk\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The raw server log files sit in the \u003Ccode>logs\u003C\u002Fcode> folder of your webspace, reachable from \u003Cstrong>Gérer les fichiers journaux\u003C\u002Fstrong> (\u003Cem>Manage log files\u003C\u002Fem>).\u003C\u002Fp>\n\u003Ch2>Troubleshooting\u003C\u002Fh2>\n\u003Ch3>❌ The error log stays empty\u003C\u002Fh3>\n\u003Cp>The error is not recorded where you are looking.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Tick all the logs again, \u003Cstrong>Erreur Nginx\u003C\u002Fstrong> in particular, and remove the type filter\u003C\u002Fli>\n\u003Cli>Check that the chosen period includes the time of the error\u003C\u002Fli>\n\u003Cli>If the application shows its own errors, read its file as described in step 5\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ Too many lines to find your way\u003C\u002Fh3>\n\u003Cp>Normal visits drown out the useful lines.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Filter on the \u003Cstrong>error\u003C\u002Fstrong> type and on the date\u003C\u002Fli>\n\u003Cli>Use real-time tracking while reproducing the error\u003C\u002Fli>\n\u003Cli>Enter your own IP address in the \u003Cstrong>IP\u003C\u002Fstrong> field to only see your tests\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Note the exact time of an error before investigating, the search will be much faster\u003C\u002Fli>\n\u003Cli>Read the logs again after each significant update of your website\u003C\u002Fli>\n\u003Cli>Turn off your application debug mode once the problem is solved\u003C\u002Fli>\n\u003Cli>A burst of access lines to the same unknown page may point to an attack, see our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fhacked-website-plesk\">What to Do If Your Website Is Hacked on Plesk\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If the message remains unclear, open a ticket with our support from your \u003Ca href=\"https:\u002F\u002Fbilling.winheberg.com\">client area\u003C\u002Fa>, \u003Cstrong>Technical\u003C\u002Fstrong> department, filling in the \u003Cstrong>Related Product\u003C\u002Fstrong> field with the web hosting concerned. Copy the full log line and the time of the error, our team will know where to look.\u003C\u002Fp>\n\u003Cp>Your website finally tells you what is wrong 🔍\u003C\u002Fp>\n",1794526351203]