Troubleshooting
Fix common Blog Lite 2 problems: blank page, cannot save posts, upload and AI writer errors, pretty URLs, missing comments and a forgotten password.
Most problems have a simple cause. Find your symptom below.
First, turn on error messages
Open config.php and set 'debug' => true. Reload the page and you will see the real message. Set it back to false when you are done. See config.php options.
Installation and saving
| Symptom | Cause and fix |
|---|---|
| Blank white page | A PHP error. Turn on debug (above). Check that your PHP version is 7.4 or newer and that all files were uploaded. |
| "Can not write to ... check the folder permissions" | The data folder is not writable. Set its permission to 755 or 775 and check the owner in your hosting panel. |
| The dashboard says a folder is not writable | Same fix for data or uploads. |
| I am logged out all the time | PHP cannot save sessions or cookies are blocked. Ask your host to make the session folder writable, and use the same address (with or without www) every time. |
| Dates or times are wrong | Set your timezone in config.php. |
Images
| Symptom | Cause and fix |
|---|---|
| "Only JPG, PNG, GIF and WebP images are allowed" | The file is another type or is damaged. Re-export it as JPG or PNG. |
| "The image is bigger than 5 MB" or upload error | Compress the image, or raise max_upload_mb in config.php and upload_max_filesize and post_max_size in php.ini. |
| "Could not save the image" | The uploads folder is not writable. |
The AI writer
| Message | Cause and fix |
|---|---|
| "AI is not set up yet" | No API key saved. See AI API keys (Groq, DeepSeek, OpenAI). |
| "AI service error: Invalid API Key" | The key is wrong or was deleted. Paste it again without spaces, and check that the selected provider matches the key. |
| "AI service error" about the model | The model name does not exist at that provider. Clear the Model field to use the default. |
| "AI service error" about quota or rate limit | You used up your free limit or credits. Wait a while or check your provider account. |
| "Could not reach the AI service: SSL certificate problem" | Typical on a local XAMPP server. Set 'ai_verify_ssl' => false in config.php (local only). |
| "Could not reach the AI service" or a timeout | Your hosting blocks outgoing connections, or the provider is busy. Try a shorter length, or ask your host. |
| "The PHP cURL extension is not enabled" | Enable curl in your hosting panel or php.ini. |
| The Write with AI panel is missing | The AI writer is switched off in Settings → AI writer. |
The public site
| Symptom | Cause and fix |
|---|---|
| "Page not found" after turning on Pretty URLs | Your server lacks the rewrite rules. See Pretty URLs. Turn the option off to recover. |
| A comment does not appear | It is waiting for approval in Comments → Pending. See Comment moderation. |
| A visitor cannot comment | Comments may be off for the blog or this post, or the visitor submitted twice within 30 seconds. |
| Contact messages are not emailed | Check the email address in Settings. Your server may not support mail(). The messages are still saved in the inbox. |
| A category is missing from the menu | Categories only show when they have a published post. |
| A post is missing from the homepage | It may still be a draft. Check its status. |
| The editor is a plain box | The visual editor could not be downloaded (offline or blocked). Reload while online. You can still write HTML and use the AI writer. |
Forgot your admin password
You can safely reset the account without losing any content:
- Download
data/settings.xmlwith FTP and make a copy. - Open it in a text editor and delete the lines
<admin_user>...</admin_user>and<admin_password>...</admin_password>. - Upload the file again.
- Open
yoursite.com/admin/. The setup screen appears, where you create a new username and password. Your posts, comments and settings are kept.
Locked out after wrong passwords
After 5 wrong attempts the login is blocked for 15 minutes. Wait and try again, or delete data/attempts.xml.
Still stuck?
Read the FAQ or contact support with the exact error message and your PHP version.
Last updated