<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>general-errors on</title><link>https://docs.whmcs.com/9-1/tags/general-errors/</link><description>Recent content in general-errors on</description><generator>Hugo -- gohugo.io</generator><atom:link href="https://docs.whmcs.com/9-1/tags/general-errors/index.xml" rel="self" type="application/rss+xml"/><item><title>404 Page Not Found Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/404-page-not-found-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/404-page-not-found-errors/</guid><description>Fixes the 404 Not Found error caused by a Friendly URLs misconfiguration or an outdated .htaccess file, by reverting Friendly URLs to Basic URLs in General Settings (or via the RouteUriPathMode database setting), or by refreshing the .htaccess rewrite rules using Auto-Managed Rewrite and Synchronize.</description></item><item><title>Admin Directory Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/admin-directory-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/admin-directory-errors/</guid><description>Resolves admin directory conflict errors such as &amp;ldquo;accessing the admin area via a directory that is not configured&amp;rdquo; by verifying the correct URL, setting the $customadminpath value in configuration.php, uploading updated files to a custom admin directory and deleting the default admin folder, or reverting the admin directory name to admin.</description></item><item><title>Dataset Must Be Array Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/dataset-must-be-array-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/dataset-must-be-array-errors/</guid><description>Resolves the &amp;ldquo;InvalidArgumentException: Dataset must be an array&amp;rdquo; TableQuery.php error caused by an incorrect $mysql_charset value in configuration.php, with the fix of setting $mysql_charset = &amp;lsquo;utf8&amp;rsquo; and removing any latin1 entry.</description></item><item><title>Down for Maintenance Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/down-for-maintenance-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/down-for-maintenance-errors/</guid><description>Troubleshoots the Down for Maintenance (Err2) error caused by a mismatch between database, WHMCS file, and PHP versions, with separate resolution steps for when the error appears during an in-progress update (browser install.php upgrade process) versus after an update that did not complete or apply correctly.</description></item><item><title>Filename Not Allowed Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/filename-not-allowed-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/filename-not-allowed-errors/</guid><description>Fixes the &amp;ldquo;This filename is not allowed&amp;rdquo; error when uploading a file at Support &amp;gt; Downloads, caused by the file&amp;rsquo;s extension being missing from the allowed list, by adding the extension to Allowed File Attachment Types in General Settings &amp;gt; Support and saving changes.</description></item><item><title>Missing Country Customizations</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/missing-country-customizations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/missing-country-customizations/</guid><description>Explains why custom changes to /resources/country/countries.json don&amp;rsquo;t take effect, caused by invalid JSON syntax in the file, and directs running the file&amp;rsquo;s contents through an online JSON syntax validator to locate the error.</description></item><item><title>Module Command Unknown Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/module-command-unknown-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/module-command-unknown-errors/</guid><description>Addresses the &amp;ldquo;An unknown error occurred&amp;rdquo; module command error caused by a third-party system or module returning a response WHMCS cannot interpret, and directs checking the Module Log under System Logs to identify the exact cause.</description></item><item><title>Query String URI Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/query-string-uri-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/query-string-uri-errors/</guid><description>Explains the &amp;ldquo;InvalidArgumentException: Query string must not include a URI fragment&amp;rdquo; activity log error, caused by bots crawling invalid URLs, notes no corrective action is required, and gives the option to disable Log Errors in General Settings &amp;gt; Other to stop logging it.</description></item><item><title>Redirect Loops</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/redirect-loops/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/redirect-loops/</guid><description>Resolves redirect loops caused by server or website misconfiguration, with checks of the WHMCS System URL setting in General Settings, resetting the .htaccess file and removing other .htaccess files in the directory tree, and changing Cloudflare&amp;rsquo;s SSL mode to Full or Full (Strict).</description></item><item><title>Server Communication Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/server-communication-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/server-communication-errors/</guid><description>Diagnoses &amp;ldquo;An error occurred while communicating with the server. Please try again&amp;rdquo; by checking for a System URL mismatch between the browser URL and the WHMCS System URL setting in General Settings, enabling Log Errors to catch PHP errors in System Logs, and using browser Network/Inspect tools to read the response, with the fix of aligning the access URL to the configured System URL.</description></item><item><title>Server IP Address in Logs</title><link>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/server-ip-address-in-logs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/server-ip-address-in-logs/</guid><description>Fixes the server&amp;rsquo;s own IP address appearing instead of the client&amp;rsquo;s or admin&amp;rsquo;s IP in the Activity, Admin, or Whois logs, caused by a proxy such as Cloudflare supplying an incorrect PHP variable among HTTP_CLIENT_IP, HTTP_X_FORWARDED_FOR, and related headers, by configuring the Proxy IP Header and Trusted Proxies fields under General Settings &amp;gt; Security.</description></item></channel></rss>