Skip to the products
LCPanelLicence Center Panel

Troubleshooting

Where to look first, and fixes for cron, e-mail, ownership verification, licence states, 403, 404, 500 and 503 errors, maintenance mode, sign-in problems and the error log.

Reference Updated 6 Nov 2026 36 / 36

When something does not work, start with the same three places: the Dashboard (cron, licence, security events), Reports → E-mail Log and Reports → Automation Log, and Settings → System & Maintenance → Log (the file errors.log). Most problems are visible in one of them. This chapter lists the common problems with their cause and cure, grouped by area.

1. The first look

PlaceWhat it tells you
Dashboard, Automation (cron)Running, Late or Never ran.
Dashboard, LicenceThe state of the licence.
Dashboard, Security eventsBans, new devices, ownership changes.
Settings → System & MaintenanceThe cron state, the failed jobs, the server checks (red marks), the database state and the log.
Reports → Automation LogWhat each job did and the errors of the failed ones.
Reports → E-mail LogEvery mail, with the error when it failed.
data/logs/errors.logPage errors. It should be empty.

A page that fails shows Something went wrong on this page. The error was written to the log. and a plain layout. The details are in errors.log, with the page, the message, the file and the line. To see the message on the page while you debug, switch on Show error details to staff under Settings → General Settings → Security, and switch it off again.

2. The cron does not run

SignCauseFix
Dashboard says Never ranThe cron job was never added, or the command is wrong.Add it (see Installing). Copy the exact line from the Cron card.
Dashboard says Late or StoppedThe job stopped, or runs less often than every 5 minutes.Check the hosting panel's cron list and set */5 * * * *.
Cron mail from the host says php: command not foundThe path to PHP is wrong.Use the full path that the Cron card shows (for example /usr/local/bin/php or /opt/cpanel/ea-php82/root/usr/bin/php).
The web cron answers Invalid cron key (403)The address has the wrong key, or a new key was made.Copy the address again from the Cron card.
The web cron answers a login page or 404The address is not https://your-domain/cron.php?key=.... For a sub-folder include the folder.Fix the address.
Run now says the server does not let PHP start programsexec is disabled.Open the web address of the cron in a browser, or use a web cron service.
The command works by hand but not from croncron uses another PHP version, or a memory limit.Use the same PHP binary by full path. Put >/dev/null 2>&1 at the end so mails from cron stop.
Some jobs Failed in the Automation LogThe message column tells why (for example the exchange rate service was not reachable).Fix the cause; run the job again from Run now.

To test: Run now, choose Every job, tick Even if not due, and read the output. A healthy run lists each job with ok.

3. E-mails are not sent or not received

SignCauseFix
Nothing in the E-mail LogSend e-mail is off, or the template is switched off.Settings → General Settings → E-mail: switch Send e-mail on. Settings → E-mail Templates: check the template.
Log says Failed with an errorThe server refused.Read the error in the log. For SMTP check host, port (587 TLS, 465 SSL), user and password; Check the server certificate off while you test. For PHP mail() try the -f switch, or move to SMTP.
Log says Sent but the mail never arrivesThe receiving side put it in spam or dropped it.Check the spam folder. Send from an address on your own domain, set up SPF and DKIM for it, and ask the host about the sending reputation.
A test mail works but member mails are lateThe mail queue waits for the cron.Fix the cron (section 2) or press Work the queue now.
Members do not get the verification linkWrong address, spam folder, or a blocked provider.Check the address under Users, press Send verification e-mail or Mark e-mail as verified, and check Banned IPs & E-mail Domains for the provider.
Mails show a broken logo or wrong linksSite address is empty or wrong.Set it under General (like https://www.example.com).
Sellers do not get inquiry mailsThey switched the e-mail off in Notifications.The bell still shows them. Ask them to check Account Settings → Notifications.

Always test with Send test and read the result line under the button.

4. Verification is not found

Sellers see The record was not found yet. Work through the list:

CheckWhat to look for
The full host nameTyped _aiodomain-verify.example.com.example.com? The panel added the domain a second time. Use the short host.
The right DNS providerThe record must be where the domain's name servers point (the registrar, Cloudflare, or a hosting company).
The valueExactly as shown, no quotes, no spaces at either end, no line break.
The typeTXT for the TXT method, CNAME for the CNAME method.
CloudflareCNAME records must be DNS only (grey cloud).
TimeChanges can take an hour, rarely longer. The marketplace keeps checking. Press Check now after a while.
The tokenA newer Start verification replaces the old token. Use the record on the page now. An old one gives not found. After the token's days, The token expired.
CNAME target emptyThe owner has not set CNAME target under the Verification settings. Use TXT or set the target.
DNS lookups blockedThe host disabled dns_get_record, so no record can be read. The installer would have warned. Ask the host.
An outside checkLook the record up with a public DNS tool. If it is not there, it is not on the internet yet.

Staff can see what the marketplace read: open the listing, Verification tab → history; the Result column says seen: ... with the values found. If the seller truly owns the domain and cannot add a record, use Manual review or the Admin override with a note. See Verifying ownership.

5. Licence problems

State on the Licence pageMeaning and cure
Not registeredNo key. Enter it.
Invalid keyThe key is wrong or unknown. Copy it again from lcpanel.com.
Registered to another domainThe key is bound elsewhere. Release it there, or ask support to change the domain.
Active (could not reach the License Center lately)The server cannot reach lcpanel.com. Allow outgoing HTTPS. The marketplace works until the grace window ends.
ExpiredRenew, then Check now.
Suspended, RevokedRead the message on the page and contact support.
You are sent to the Licence page from every admin pageThe state is not Active. Fix it, or at least reach the Licence page to activate.
The listing limit of N is reachedYour package's active-listing limit. Remove listings or upgrade, then Check now.

Details are in The licence key.

6. Errors 403, 404, 500 and 503

You seeCauseFix
404 on every page except the home page.htaccess is missing, or mod_rewrite / AllowOverride is off.Upload .htaccess again (it is a hidden file). On nginx add the rewrite rule.
404 on a sub-folder installRewriteBase still says /.Set RewriteBase /your-folder/.
403 Forbidden on /uploads/kyc/... or /data/...That is intended; those folders are private.Staff open identity documents through the admin KYC page.
403 Forbidden on /admin/pages/...Page files are private.Use /admin/<page> addresses.
Access denied: Your role does not allow this pageThe signed-in role lacks the right.Add the right under Users → Roles & Permissions, or Permissions on the user.
Your role does not allow this action (users.suspend)The same, for a button.The message names the right.
403 Invalid cron keySee section 2.
Page not found inside the site layoutThe address is not a page. A hidden CMS page is also a 404 for visitors.Check the address, or publish the page.
500 white pageA fatal error before the layout.data/logs/errors.log and the host's error log. Often an old PHP version, a missing extension, or a half-uploaded file.
503 We are doing some maintenanceMaintenance mode is on.See section 7.
Not signed in (API, 401)An AJAX call without a session.Sign in again.
419 the form is staleThe page was open too long, or cookies are blocked, so the form's security token no longer matches.Go back, reload the page and send the form again; check that cookies are on.

7. Maintenance mode

With Maintenance mode on (Settings → General Settings → System), visitors and members see the notice with a 503 answer; signed-in staff see the site normally, and a yellow bar in the admin area warns that it is on.

To switch it off: sign in as staff at /admin (sign-in always works in maintenance mode), open Settings → General Settings → System, switch Maintenance mode off, and save. If you cannot sign in, set the value in the database:

UPDATE ad_settings SET value = '0' WHERE `key` = 'maintenance_mode';

(use your table prefix if it is not ad_), then press Clear the cache or delete the files in data/cache.

8. Signing in

ProblemCure
The e-mail address or password is not rightCheck the address and the case of the password. Forgot password? sends a reset link (one hour).
Too many failed sign-ins from your address. Please wait a few minutesThe address is banned (5 failures in an hour, for 15 minutes by default). Wait, or another staff member removes the ban under Users → Banned IPs & E-mail Domains, or add your address to the Sign-in whitelist.
This account has been banned / is suspended / is closedRead the reason; staff can lift a suspension or ban from the user's record.
This account has no access to the admin areaThe account has no role. A staff manager sets one under Users.
Pending e-mail verificationClick the link in the mail, or ask staff to Mark e-mail as verified.
Lost phone with two-factor onUse a recovery code. Otherwise a staff manager opens Users → [user] → Security → Switch 2FA off. If the only administrator lost it, run in the database: UPDATE ad_users SET twofa_on = 0, twofa_secret = '', twofa_recovery = '' WHERE username = 'admin';
Lost the only administrator password and the reset mail does not arriveFix the mail first (section 3), then use Forgotten your password? on the admin sign-in page again. If mail cannot work yet, ask support for help.
Signed out all the timeThe session cookie is blocked, the clock is wrong, or the site switches between www and the bare domain. Use one address; set Site address correctly.
ProblemCause and cure
A seller cannot add a domainE-mail not confirmed, the extension is blocked, the name is already listed (by them, or by another seller), the licence limit is reached, or the name is invalid. The page says which.
Verify first in the approval queueThe listing is not verified and Ownership must be verified is on. Open the Verification tab.
A listing is not found by searchIt must be Active. A paused, pending, expired or sold listing is not searched.
Counts of listings per category or extension look wrongDomains → Categories → Refresh counts, or Extensions → Refresh counts. The nightly job does it too.
Registrar, age or name servers are emptyThe first registry lookup is queued when the listing is added and needs the cron. Press Refresh registry data on the Verification tab. RDAP needs outgoing HTTPS to the service address; WHOIS needs outgoing port 43.
A CSV import adds nothingOpen the result: each bad row names the reason. Check the header row, the separator (a comma), the file encoding (UTF-8), and that the seller's e-mail is confirmed.
An upload is refusedThe file is larger than the cap (Largest upload (MB) and PHP's upload_max_filesize) or has a type the field does not accept.
Prices look wrong in another currencySettings → Currencies & Rates: update the rates, or fix a rate typed by hand.
The sitemap is empty or oldSettings → General Settings → SEO → Rebuild the sitemap now.

10. Speed and disk

  • Use the Clear the cache button after big changes; it is safe.
  • The disk fills slowly with uploads, logs and SQL backups. Delete old backups and clear logs from the System page.
  • A slow admin list usually means a very large table; use the filters. The daily housekeeping job already deletes old log rows (see Reports and logs).
  • For a busy marketplace, use a VPS with more memory and Redis for the cache (see Requirements).

11. Asking for help

Write to support from your account at lcpanel.com. Send:

  1. Your AIODomain version (the footer, or What's New) and your PHP version (the Server card).
  2. What you did, what you expected, and what happened (a screenshot helps).
  3. The last lines of errors.log and, for mail or cron problems, the line from the E-mail Log or Automation Log.
  4. Never send passwords, API keys, the cron key, config.php or a database backup in a message.
Was this helpful?
Share this chapter