Troubleshoot common hosting faults with an AI assistant
When something stops working, an AI assistant can walk you through the checks in plain language, at your pace, while you look at your own screen. This page gives you a prompt for each of the most common faults on Noiz hosting: a website that is down or blank, email that will not send or arrive, and certificate warnings. Each prompt carries the facts the assistant needs about Noiz hosting, keeps it to safe checks one at a time, and tells it when to send you to us instead.
Last reviewed: 19 October 2026, against Plesk Obsidian on Noiz shared hosting.
Official Documentation Reference
- Plesk Customer Guide: Log files: where the error and access logs are.
- Plesk: Securing connections with SSL It!: how certificates are issued and renewed.
Before you start
- An AI assistant you use with a business account. Nothing here connects it to your hosting; you describe what you see.
- Access to Plesk for the domain, or at least to the website and your mail app.
- The exact error message, copied as text or as a screenshot with any passwords and other people's details covered.
How to use these prompts
- Paste the prompt for your fault and fill in the brackets.
- Do one check at a time and tell the assistant what you saw.
- Stop when the assistant says the next step needs Noiz, and open a ticket with what you found. The checks you have done save time.
The prompts never ask for a password and never ask the assistant to change anything for you. If an assistant asks for a password or suggests deleting files, turning off security or changing DNS "to see if it helps", do not do it.
The website is down, blank or shows an error
Manual checks are in PHP error: allowed memory size of X bytes exhausted and the WordPress section.
My website [yourdomain.com] is hosted by Noiz on Plesk Obsidian shared
hosting, plan [sLegacy or sPremium]. Problem: [blank white page / "critical
error" / 500 error / site not found / very slow]. It started [when], after
[any change: a plugin update, a new theme, a DNS change, nothing].
Help me find the cause one check at a time, starting with the simplest, and
wait for my answer after each check. Likely checks: whether the site loads
from another network or phone, whether the domain still points to Noiz
(nameservers ns1.noiz.co.za and ns2.noiz.co.za), and the most recent lines
of the domain's error_log in Plesk under Logs, which I will paste to you.
Rules: never ask for any password. Do not tell me to delete files,
databases or plugins. If a plugin is the cause, tell me how to switch it
off by renaming its folder, and how to undo that. Tell me to take a backup
before any change. If the error points at the server itself, tell me to
contact Noiz support and what to include.
Email will not send or arrive
Manual checks are in Why is my email not working? An email troubleshooting guide.
My email on [yourdomain.com] is hosted by Noiz on Plesk Obsidian. Problem:
[cannot send / not receiving / password rejected / messages going to spam].
The exact error is: [paste]. It started [when]. My mail app is [app and
device].
The correct Noiz settings are: server mail.yourdomain.com (or the server
name in my welcome email), username my full email address, IMAP on port 993
with SSL/TLS, SMTP on port 465 with SSL/TLS and authentication on.
Help me find the cause one check at a time, starting with the simplest, and
wait for me after each one: signing in to webmail with the same details,
comparing my app's settings with the ones above, and checking whether the
problem is on one device or network only. Never ask for my password. Do not
suggest changing DNS records, MX records or server settings yourself; if
the cause looks like DNS or the server, tell me what to send Noiz support.
If the problem is that your mail goes to other people's spam folders, ask the assistant to explain your domain's SPF, DKIM and DMARC records from what you paste, then see How to protect your domain from spoofing and improve email deliverability.
The browser warns that the site is not secure
Plesk issues and renews free Let's Encrypt certificates for you. Warnings usually mean the certificate does not cover the address being visited, or a page loads something over plain HTTP. Manual steps are in How to install a free Let's Encrypt SSL certificate in Plesk.
My website [yourdomain.com] is hosted by Noiz on Plesk Obsidian, which
issues free Let's Encrypt certificates. The browser shows: [paste the exact
warning]. It happens on [https://yourdomain.com / https://www.yourdomain.com
/ a subdomain / webmail].
Help me find the cause one check at a time and wait for me after each one:
whether the certificate covers both the address with and without www, its
expiry date, whether the domain points to Noiz, and whether the page loads
images or scripts over http:// (mixed content). Then tell me which option
to tick in Plesk under SSL/TLS Certificates, if any. Never ask for a
password or a private key. If the certificate cannot be issued, tell me
what error to send Noiz support.
Uploads fail with "413 Request Entity Too Large"
On my Noiz-hosted site [yourdomain.com] (Plesk Obsidian), uploading a file
of [size] fails with HTTP 413 Request Entity Too Large in [WordPress media /
a form / the file manager]. Explain what limits apply, which of them I can
change myself in Plesk's PHP Settings, and which need Noiz support. One step
at a time; no passwords; tell me to keep a note of each setting I change so
that I can change it back.
The manual steps are in How to fix HTTP 413 request entity too large upload errors in Plesk.
When the assistant is not helping
- It keeps suggesting the same check. Tell it the result again in different words, or paste the exact error.
- It names menus you cannot find. Tell it you are a customer on Noiz shared hosting with Plesk Obsidian and which plan you have.
- It wants a password, a private key or a code. Do not give it. Go to the linked guide, or to us.
- The fault is on the server. No prompt fixes that. Open a ticket and paste what the assistant helped you find.
When a prompt is not enough
If you would rather someone else watched your WordPress site and fixed it when it breaks, WordPress Care keeps it updated with a restore point first and recovers it when something goes wrong.
