23 questions in this topic
Expand a question to see the answer. The content is visible in HTML and can be indexed by search engines.
301. What to do in case of error 400?
We diagnose error 400 based on the URL, time of occurrence, scope of the problem and recent changes to the application. Some errors result from permissions, some from PHP/CMS, LVE limits, DNS, ModSecurity or external services.
In your report, please include the URL, screenshot or error content, your IP address, time, and whether the problem occurs for all users or only some users.
302. What to do in case of error 401?
We diagnose a 401 error based on the URL, time of occurrence, scope of the problem and recent changes to the application. Some errors result from permissions, some from PHP/CMS, LVE limits, DNS, ModSecurity or external services.
In your report, please include the URL, screenshot or error content, your IP address, time, and whether the problem occurs for all users or only some users.
303. What to do in case of error 403?
Error 403 means the resource cannot be accessed. Reasons: wrong file/directory permissions, missing index file, .htaccess block, Directory Privacy, ModSecurity/WAF/Imunify360, IP block or attempt to list a directory. By default, directories are 755, files are 644, and public_html must be available to the web server. Details are usually in cPanel → Errors or error_log.
304. What to do if ModSecurity is blocked?
A ModSecurity block means that the application firewall has considered the request to be similar to an attack, such as SQL injection, XSS, or a suspicious form. If a legitimate operation is blocked, do not disable protection globally without analysis.
Provide support with the URL, time, IP address, message content and description of the activity. Support will check the rule and assess whether it is a false positive, an application error or a real threat.
305. What to do in case of error 404?
Error 404 means that the server did not find the specified URL. You should check whether the file exists in the correct document root, whether the domain points to the correct directory, whether there are no incorrect redirections and whether the application has the correct rewrite rules. In WordPress, it often helps to save Settings → Permalinks or recreate .htaccess. In cPanel, it is worth checking Domains, File Manager and Errors.
306. What to do in case of error 405?
We diagnose error 405 based on the URL, time of occurrence, scope of the problem and recent changes to the application. Some errors result from permissions, some from PHP/CMS, LVE limits, DNS, ModSecurity or external services.
In your report, please include the URL, screenshot or error content, your IP address, time, and whether the problem occurs for all users or only some users.
307. What to do in case of error 500?
We diagnose error 500 based on the URL, time of occurrence, scope of the problem and recent changes to the application. Some errors result from permissions, some from PHP/CMS, LVE limits, DNS, ModSecurity or external services.
In your report, please include the URL, screenshot or error content, your IP address, time, and whether the problem occurs for all users or only some users.
308. What to do in case of error 502?
We diagnose error 502 based on the URL, time of occurrence, scope of the problem and recent changes to the application. Some errors result from permissions, some from PHP/CMS, LVE limits, DNS, ModSecurity or external services.
In your report, please include the URL, screenshot or error content, your IP address, time, and whether the problem occurs for all users or only some users.
309. What to do in case of error 503?
Error 503 means that the application or process that hosts the page is temporarily unavailable. The most common reasons are exceeding resource limits, too many PHP processes, a problem with PHP-FPM/Passenger, application maintenance work or a dependency failure. The customer should check cPanel → Errors/error_log and Resource Usage and then disable suspicious plugins, cache or cron jobs. With repeating 503s, it is worth optimizing the website or changing the package.
310. What to do in case of error 504?
We diagnose error 504 based on the URL, time of occurrence, scope of the problem and recent changes to the application. Some errors result from permissions, some from PHP/CMS, LVE limits, DNS, ModSecurity or external services.
In your report, please include the URL, screenshot or error content, your IP address, time, and whether the problem occurs for all users or only some users.
311. What to do if the website only works for some users?
For the topic "what to do when the website works for only some users", first check the settings in the website logs, DNS, SSL and recent changes in the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
312. What to do if you see the old website after migration?
For the topic "what to do if you see an old website after migration", first check the setting in the website logs, DNS, SSL and recent changes in the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
313. What to do if the DNS or browser cache shows an old version?
For the topic "what to do when the DNS or browser cache shows an old version" first check the setting in the site logs, DNS, SSL and recent changes in the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
314. What to do if the website slows down periodically?
For the topic "what to do when a website periodically slows down", first check the setting in the website logs, DNS, SSL and recent changes in the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
315. What to do when the CMS panel works but the frontend doesn't?
For the topic "what to do when the CMS panel works but the frontend doesn't", first check the settings in the website logs, DNS, SSL and recent changes in the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
316. What to do when the frontend works but the CMS panel doesn't?
For the topic "what to do when the frontend works but the CMS panel doesn't", first check the settings in the website logs, DNS, SSL and recent changes in the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
317. What to do if the contact form doesn't work?
For the topic "what to do when the contact form doesn't work", first check the setting in the website logs, DNS, SSL and recent changes in the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
318. What to do if file upload doesn't work?
For the topic "what to do when file upload doesn't work", first check the settings in the website logs, DNS, SSL and recent changes to the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
319. What to do when in-app sessions/logins are not working?
For the topic "what to do when app sessions/logins are not working" first check the setting in the site logs, DNS, SSL and recent changes to the app.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
320. What to do if the store does not finalize orders?
For the topic "what to do when the store does not finalize orders", first check the settings in the website logs, DNS, SSL and recent changes in the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
321. What to do when an external API stops responding?
For the topic "what to do when an external API has stopped responding", first check the setting in the site logs, DNS, SSL and recent changes to the application.
If the problem occurs only among some users or only in a selected website function, you need to separate DNS, browser cache, application cache, CDN/proxy, sessions, forms, database and external integrations.
In the request, provide the recovery steps, a test account if needed, URL, time, browser, IP address and recent changes to the CMS or store.
322. What data should the customer always provide when reporting a failure?
When reporting a failure, always include: website address, exact URL, time of the problem, error message, your IP address, recent changes, browser used and whether the problem affects all users.
For mail, add the sender, recipient, subject, SMTP stanza, and headers. For CMS/store, add recent updates, plugins and logs if available.
10281. How to configure your own error pages?
You can configure your own error pages in cPanel → Advanced → Error Pages or manually in .htaccess via the ErrorDocument directive, e.g. ErrorDocument 404 /404.html. The error page file must exist in the page directory and should not generate errors itself. In CMS applications, it is often better to configure a 404 page in a theme or plugin to maintain the appearance of the site.