Troubleshooting

Start with the smallest reliable check.

Most installation and operation problems become easier once you separate database access, URL configuration, filesystem permissions, scheduled tasks, authentication, and sending infrastructure.

Database connection fails

Re-check all four connection values

Hostname, database name, database username, and database password must match the target server.

Confirm network access

The MySQL server must accept connections from the web server or trusted network where Clistor runs.

Confirm database privileges

The dedicated database user needs the permissions required for installation and normal application operation.

Links point to the wrong host or path

Review the Application URL. It must match the real public scheme, hostname, and base path.

Common mistake: leaving localhost, an IP address, or an old migration subdirectory in a production configuration.

Runtime files cannot be written

Verify that the web-server/PHP account can write to the directories intended for runtime storage, temporary files, and sessions. Do not solve a permissions problem by making the entire application world-writable.

Administrator login fails

Confirm you are using the Clistor administrator credentials, not the database credentials.
Confirm the installation completed and the site is using the intended database.
Clear only normal browser/session state if you suspect a stale session; do not delete application configuration blindly.
If the password was changed by another administrator, use the supported account-management/recovery process for your installation.

License activation is rejected

Use the intended production hostname for activation. Production licenses can be domain-bound and may reject localhost or direct-IP environments.

Do not work around license checks by modifying application code. If the deployment hostname is correct and activation still fails, contact Clistor support with the domain and the non-sensitive error message.

Scheduled work does not run

Application checks

Confirm the required scheduled task is configured.
Confirm the relevant campaign/autoresponder is enabled and configured.
Review the internal Help Center article for scheduled tasks.

Server checks

Confirm cron/scheduler is enabled.
Confirm the task executes under the correct account.
Review the hosting/system logs for scheduler errors.

Email sending does not work

Troubleshoot the application configuration and the mail infrastructure separately.

Verify the configured sending method and server details.
Verify authentication details with the mail provider.
Verify the required outbound network ports are permitted by your hosting provider/firewall.
Test with a controlled recipient before a real list.
Use Clistor statistics and server/provider logs to narrow down where the failure occurs.

Deliverability is not the same as sending success. A message can leave your server and still be filtered or rejected later. Provider policy, domain authentication, IP/domain reputation, content, list quality, and recipient systems all matter.

A page looks incomplete or an asset is missing

Confirm the full release package was uploaded with the directory structure intact.
Hard-refresh the browser after changing static files.
Confirm your web server serves the included CSS, JavaScript, images, and resource paths normally.
Do not add custom rewrite rules until you have proven they are necessary.

When to contact support

Contact support when the environment matches the documented requirements but Clistor still fails at a repeatable step.

Useful support information: Clistor version, PHP/MySQL versions, the page/action that fails, the visible error message, and a screenshot with passwords, tokens, database credentials, license keys, and private server paths removed.