Troubleshooting

Solutions to common Aikeedo installation, configuration, and runtime issues including database errors, asset loading problems, and model configuration.

Overview

This guide provides solutions to common issues users encounter when installing, configuring, and running Aikeedo. Issues are organized by category for easy navigation.

Before You Begin

Before troubleshooting, verify that:

1. Your server meets all server requirements
2. You have the latest version of Aikeedo files
3. You’ve followed the installation guide carefully
4. You’ve completed initial setup steps

Quick Navigation

Find your issue and click to jump to the solution:

Installation Issues

• Assets Not Loading (CSS, JS, Images)
• 404 or 403 Errors During Installation
• Database Connection Issues
• 500 Internal Server Error During Installation
• Installation Wizard Not Loading

Configuration Issues

• “Does Not Allow the Value” Error
• Cannot Select Models or Send Prompts
• 500 Error on Image Generator or Video Generator
• Save Button Does Nothing

Database Issues

• MySQL Server Has Gone Away

Feature-Specific Issues

• Auto-Generated Titles Don’t Match Content Language
• Uploaded Files Return 404 Not Found Errors
• Generated Images/Videos Not Loading

---

Installation Issues

Assets Not Loading

Symptoms:

• Installation page appears without styling
• Images, CSS, and JavaScript files fail to load
• Browser shows 404 errors for asset files

Cause: The domain is not correctly pointing to the public directory.

Solution:

1. Verify Document Root

   Ensure your domain points to the public directory within your Aikeedo installation:

   /path/to/aikeedo/public
   

   Not to the root Aikeedo directory.

2. Test Redirection

   Visit your domain (e.g., https://yourdomain.com). You should be automatically redirected to https://yourdomain.com/install.

   If the redirect works, your domain is configured correctly.

3. cPanel Users

   If you’re using cPanel and cannot change the document root for your main domain, follow the dedicated cPanel Installation Guide.

   The cPanel installation process differs from the standard installation due to control panel limitations.

Related Documentation:

• Installation Guide
• cPanel Installation

---

404 or 403 Errors During Installation

Symptoms:

• 404 error when accessing /install
• 403 Forbidden error on home page
• Installation wizard not accessible

Cause: Domain document root not pointing to the public directory, missing files, incorrect permissions, or web server configuration issues preventing proper request routing.

Solution:

1. Verify Document Root Configuration

   Ensure your domain’s document root points to the public folder:

   For cPanel:

   • Main domain: Points to public_html by default (this is correct)
   • Ensure Aikeedo’s public folder contents are copied to public_html
   • Add-on domains/subdomains: Update document root in cPanel to point to the public folder

   For VPS/Dedicated:

   • Set document root to /path/to/aikeedo/public

   Accessing your domain should automatically redirect you to /install if the document root is correctly configured.

2. Configure Web Server

   Configure your web server to serve PHP applications and rewrite all requests to /public/index.php:

   Nginx

   Ensure your server block is configured correctly:

   /etc/nginx/sites-available/aikeedo

   server {
       listen 80;
       listen [::]:80;
       server_name yourdomain.com www.yourdomain.com;
       root /path/to/aikeedo/public;
       
       # Add index.php to the list
       index index.php index.html index.htm index.nginx-debian.html;
       
       # Increase the maximum upload size
       client_max_body_size 256M;
       
       location / {
           # First attempt to serve request as file, then
           # as directory, then fall back to index.php
           try_files $uri $uri/ /index.php$is_args$query_string;
       }
       
       # Pass PHP scripts to FastCGI server
       location ~ \.php$ {
           include snippets/fastcgi-php.conf;
           
           # Fix for PHP files downloading instead of execute
           fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
           fastcgi_param DOCUMENT_ROOT $realpath_root;
           
           # With php-fpm (or other unix sockets):
           fastcgi_pass unix:/run/php/php-fpm.sock;
           # With php-cgi (or other tcp sockets):
           # fastcgi_pass 127.0.0.1:9000;
           
           fastcgi_connect_timeout 300s;
           fastcgi_send_timeout 300s;
           fastcgi_read_timeout 300s;
       }
       
       # Deny access to .htaccess files, if Apache's document root
       # concurs with nginx's one
       location ~ /\.ht {
           deny all;
       }
   }
   

   After configuring, test your Nginx configuration: sudo nginx -t and reload: sudo systemctl reload nginx

   Adjust the fastcgi_pass socket path to match your PHP-FPM configuration. Common locations:

   • /run/php/php-fpm.sock (generic)
   • /run/php/php8.2-fpm.sock (version-specific)
   • /var/run/php/php8.2-fpm.sock (alternative path)

   The server configurations provided above are minimal samples. Consult with your server administrator for the correct configuration for your specific server environment, especially if you’re using load balancers, reverse proxies, or have specific security requirements.

3. Verify .htaccess File (Apache)

   If you’re using Apache, ensure the .htaccess file is present in the public directory. Aikeedo includes this file by default with the correct rewrite rules.

   Hidden files may not be visible by default. Enable “Show hidden files” in your FTP client or file manager if you need to verify the file exists.

4. Check File Extraction

   Verify all Aikeedo files are extracted correctly and the public directory exists with all necessary files.

5. Set File Permissions

   Ensure the web server has appropriate permissions:

   # Set directory permissions
   find /path/to/aikeedo -type d -exec chmod 755 {} \;
   
   # Set file permissions
   find /path/to/aikeedo -type f -exec chmod 644 {} \;
   

6. Verify Virtual Host Settings

   Double-check that all virtual host settings are correctly configured:

   • Document Root: Must point to /path/to/aikeedo/public (not the root directory)
   • Server Name/Alias: Must match your domain exactly
   • PHP Handler: Configured correctly (PHP-FPM for Nginx, mod_php or PHP-FPM for Apache)
   • Rewrite Rules: Enabled and properly configured to route all requests to index.php
7. Test Configuration

   After making changes:

   1. Test web server configuration:

      • Nginx: sudo nginx -t
      • Apache: sudo apache2ctl configtest

   2. Reload your web server:

      # Nginx
      sudo systemctl reload nginx
      
      # Apache
      sudo systemctl reload apache2
      

   3. Visit your domain - you should be automatically redirected to /install

   If you’re redirected to /install, your server configuration is correct.

All requests must be rewritten to /public/index.php for the application to function correctly. Without proper rewrite rules, you’ll encounter 404 errors on all routes except the home page.

---

Database Connection Issues

Symptoms:

• Cannot connect to database during installation
• Database error messages in installation wizard
• Installation fails at database configuration step

Cause: Incorrect database credentials, missing database, or insufficient permissions.

Solution:

1. Verify Database Credentials

   • Database name: Must be exact (case-sensitive)
   • Username: Database user with proper permissions
   • Password: Correct password for the database user
   • Host: Usually localhost, but may be different on some hosts

2. Check Database Server

   • Ensure the database server (MySQL/MariaDB) is running
   • Verify the database is accessible from your web server
   • Confirm the database exists and is empty

3. Verify User Permissions

   The database user must have these permissions:

   • SELECT, INSERT, UPDATE, DELETE
   • CREATE, DROP, INDEX, ALTER
   If unsure, grant ALL PRIVILEGES to the database user for the specific database.

4. Check PHP Extensions

   Verify that required PHP database extensions are installed:

   • mysqli for MySQL
   • pdo_mysql for PDO support

   Check with:

   php -m | grep -i mysql
   

If problems persist, try creating a new database and user with full permissions.

---

500 Internal Server Error During Installation

Symptoms:

• HTTP 500 error before or during installation
• Blank page with 500 status code
• Generic server error message

Cause: PHP configuration issues, incorrect file permissions, or insufficient server resources.

Solution:

1. Check Error Logs

   Review server error logs for specific error messages:

   Apache:

   tail -f /var/log/apache2/error.log
   # or
   tail -f /var/log/httpd/error_log
   

   Nginx:

   tail -f /var/log/nginx/error.log
   

   Error logs will reveal the exact issue.

2. Verify PHP Version

   Ensure you’re running PHP 8.2 or later:

   php -v
   

   Verify all required extensions are installed:

   php -m
   

3. Set Correct Ownership and Permissions

   # Set ownership (replace www-data with your web server user)
   chown -R www-data:www-data /path/to/aikeedo
   
   # Set directory permissions
   find /path/to/aikeedo -type d -exec chmod 755 {} \;
   
   # Set file permissions
   find /path/to/aikeedo -type f -exec chmod 644 {} \;
   

   Common web server users: www-data (Ubuntu/Debian), apache (CentOS/RHEL), nginx (Nginx)

4. Restart PHP-FPM (if applicable)

   If using PHP-FPM:

   sudo systemctl restart php8.2-fpm
   

   Replace 8.2 with your PHP version.

5. Increase PHP Memory Limit

   Edit your php.ini file:

   memory_limit = 256M
   

   Restart your web server after making changes.

---

Installation Wizard Not Loading

Symptoms:

• Blank white page when accessing installation
• Installation wizard doesn’t appear
• JavaScript errors in browser console

Cause: PHP errors, insufficient server resources, or missing files.

Solution:

1. Check PHP Error Logs: Review PHP error logs for fatal errors or warnings
2. Clear Browser Cache: Hard refresh (Ctrl+Shift+R or Cmd+Shift+R) or try a different browser
3. Verify SSL Certificate: If using HTTPS, ensure your SSL certificate is valid
4. Check File Permissions: Verify web server can read all files in the public directory
5. Confirm PHP Extensions: Ensure all required extensions are installed (see Server Requirements)
6. Check Server Resources: Verify sufficient CPU and RAM are available

Try accessing the site from an incognito/private browsing window to rule out browser cache issues.

---

Configuration Issues

”Does Not Allow the Value” Error

Symptoms:

• Error message: “Does not allow the value”
• Occurs after installation when trying to use features

Cause: The Site Domain value is missing in General Settings.

Solution:

1. Log in to the admin panel
2. Navigate to Settings > General
3. Locate the “Site Domain” field
4. Enter your domain without protocol or paths (e.g., yourdomain.com)
5. Enable SSL if you have an SSL certificate
6. Click “Save changes”

Related Documentation:

• Initial Setup - Configuring Site Domain

---

Cannot Select Models or Send Prompts

Symptoms:

• Browser console shows JavaScript errors
• Unable to select AI models in dropdown
• Cannot send prompts or generate content
• Tools missing from sidebar

Cause: Features and models are not enabled globally, or plan configuration is incomplete.

Solution:

1. Enable Features Globally

   1. Navigate to Settings > Features in the admin panel
   2. Enable the features you want to offer (Chat, Writer, Coder, etc.)
   3. Click “Save changes”

   Enabling features globally makes them available but they still need to be configured in plans.

2. Enable Models Globally

   1. Go to Settings > Models
   2. Enable the AI models you want to make available
   3. Click “Save changes”
3. Configure Plan Settings

   1. Navigate to the Plans page in the admin panel
   2. Find the plan your users are subscribed to
   3. Edit the plan configuration:
      • Enable desired features
      • Enable desired models
      • Set credit allocations
   4. Important: Check the “Update snapshots” box before saving
   5. Click “Save changes”

   If you don’t check “Update snapshots,” changes will only apply to new subscriptions, not existing ones.

4. Verify Configuration

   1. Log in as a test user
   2. Verify tools appear in the sidebar
   3. Test selecting a model and generating content

   Users should now be able to access features and generate content.

Related Documentation:

• Plans, Snapshots & Subscriptions
• Application Configuration

---

500 Error on Image Generator or Video Generator

Symptoms:

• Imagine (image generator) page returns HTTP 500 error
• Video generator page returns HTTP 500 error
• Server error logs show credit ratio issues

Cause: Credit ratios are not configured for all enabled models.

Solution:

1. Navigate to Settings > Credit Ratios in the admin panel
2. Review all enabled AI models
3. Ensure every enabled model has a credit ratio configured
4. Set appropriate credit values for each model
5. Click “Save changes”

If you’re unsure about credit ratios, start with the default suggestions and adjust based on your pricing strategy.

Related Documentation:

• Unified Credit System
• Application Configuration

---

Save Button Does Nothing

Symptoms:

• Clicking “Save changes” or other save buttons in the admin panel has no effect
• No error message appears
• Page appears to be unresponsive after clicking save
• Changes are not saved

Cause: Most commonly a backend PHP error that’s preventing the request from completing. Can also be a frontend JavaScript issue.

Solution:

1. Check Browser Console for Frontend Errors

   Before clicking the save button, check for frontend errors:

   1. Open your browser’s developer console:
      • Chrome/Edge: Press F12 or Ctrl+Shift+I (Windows/Linux) / Cmd+Option+I (Mac)
      • Firefox: Press F12 or Ctrl+Shift+K (Windows/Linux) / Cmd+Option+K (Mac)
      • Safari: Enable Developer menu first, then press Cmd+Option+I
   2. Look for any red error messages in the console
   3. Review error details - they often indicate the specific issue

   If you see errors in the console before clicking save, the issue is likely frontend-related. Note the error messages for troubleshooting.

2. Check Server Error Logs (Apache/Nginx)

   If no frontend errors are visible, first check server-level error logs, as the issue might occur before the request reaches PHP:

   1. Locate your web server error log:

      # Apache
      /var/log/apache2/error.log
      # or
      /var/log/httpd/error_log
      
      # Nginx
      /var/log/nginx/error.log
      

   2. View recent errors:

      tail -f /path/to/error.log
      

   3. Click the save button while monitoring the log

   4. Review any error messages that appear

   Server-level errors can include issues like request timeouts, connection problems, or web server configuration errors that prevent requests from reaching PHP.

3. Check PHP Error Logs (Backend Issue)

   If no server-level errors are found, check PHP error logs:

   1. Locate your PHP error log (common locations):

      # PHP-FPM
      /var/log/php8.2-fpm.log
      # or check php.ini for error_log location
      # You can find it with: php -i | grep error_log
      

   2. View recent errors:

      tail -f /path/to/php-error.log
      

   3. Click the save button while monitoring the log

   4. Review the error message that appears in the log

   The error log will show the exact PHP error preventing the save operation from completing. Common issues include database errors, permission problems, or missing dependencies.

4. Enable DEBUG Mode and Check API Response

   Alternatively, enable DEBUG mode to get more detailed error information:

   1. Enable DEBUG mode from the admin panel:

      • Navigate to Status page in the admin panel
      • Enable DEBUG mode using the toggle or button provided

   2. Open your browser’s developer console (see step 1 above)

   3. Navigate to the Network tab in the developer console

   4. Click the save button again

   5. Look for the API request that was made when you clicked save (usually shows as a POST request)

   6. Click on the request to view details:

      • Check the Status Code (should be between 200 and 299 for success, 4xx/5xx for errors)
      • Check the Response tab to see the response body
      • Review any error messages in the response

   Remember to disable DEBUG mode from the Status page after troubleshooting, as it can expose sensitive information in production environments.

5. Address the Specific Error

   Based on the error information you’ve gathered:

   • Database errors: Check database connection and permissions
   • Permission errors: Verify file/directory permissions (see 500 Internal Server Error)
   • Missing dependencies: Ensure all required PHP extensions are installed
   • Frontend JavaScript errors: Check for conflicting scripts or browser compatibility issues

   The specific error message will guide you to the exact solution. Common fixes include updating file permissions, fixing database credentials, or installing missing PHP extensions.

Related Documentation:

• 500 Internal Server Error During Installation - Permission and PHP configuration issues
• Database Connection Issues - Database-related errors

---

Database Issues

MySQL Server Has Gone Away

Symptoms:

• Error message: “MySQL server has gone away”
• Database connection drops during requests
• Long-running operations fail

Cause: MySQL server timeout or packet size limitations.

Solution:

Server Timeout Fix

Problem: MySQL server times out and closes the connection.

Solution: Update your my.cnf configuration file:

[mysqld]
wait_timeout = 28800

This sets the timeout to 8 hours. Adjust as needed for your use case.

After modifying my.cnf, you must restart your MySQL server for changes to take effect:

sudo systemctl restart mysql

or

sudo service mysql restart

Finding my.cnf:

Common locations for the MySQL configuration file:

• Linux: /etc/my.cnf or /etc/mysql/my.cnf
• macOS: /etc/my.cnf
• Windows: C:\ProgramData\MySQL\MySQL Server X.X\my.ini

If you’re on shared hosting and don’t have access to my.cnf, contact your hosting provider to request these changes.

---

Feature-Specific Issues

Auto-Generated Titles Don’t Match Content Language

Symptoms:

• AI generates titles in Spanish when content is in another language
• Title language doesn’t match the generated content language

Cause: AI models sometimes generate titles in their default language despite instructions.

Solution:

Option 1: Modify Prompts

Customize the title generation prompts in these files:

/src/Ai/Infrastructure/Services/OpenAi/TitleGeneratorService.php
/src/Ai/Infrastructure/Services/Anthropic/TitleGeneratorService.php
/src/Ai/Infrastructure/Services/Cohere/TitleGeneratorService.php

Strengthen the language instruction in the prompt to emphasize matching the content language.

Custom code modifications will need to be reapplied after app updates.

---

Uploaded Files Return 404 Not Found Errors

Symptoms:

• Uploaded files show “not found” or 404 errors
• Generated files (images, videos, audio, documents etc.) are inaccessible
• Files exist in storage but cannot be accessed via URL
• Browser shows 404 when clicking file links

Cause: File grouping enabled on local storage, secure URLs enabled, incorrect document root configuration, or file permission issues.

Solution:

1. Disable File Grouping (if using local storage)

   If you’re experiencing file access issues with local storage, try disabling file grouping:

   1. Log in to the admin panel
   2. Navigate to Settings > Storage
   3. Locate the “File Grouping” option
   4. Change the value to “None”
   5. Click “Save changes”

   File grouping and secure URLs are optimized for cloud storage (S3, DigitalOcean Spaces, etc.) and may cause compatibility issues on some local storage configurations, particularly on cPanel-based hosting. If files are inaccessible, disabling these options often resolves the issue.

2. Disable Secure URLs

   If you’re using local storage without special security requirements:

   1. In Settings > Storage
   2. Locate the “Secure URLs” option
   3. Turn off the “Secure URLs” option
   4. Click “Save changes”

   If files were uploaded with Secure URLs enabled, you may need to re-upload them after disabling this option.

3. Verify Document Root Configuration

   If your domain’s document root is set to public_html instead of public:

   1. Open your .env file in the root directory
   2. Find the line with PUBLIC_DIR (it may be commented out with #)
   3. Ensure it’s set correctly:
      PUBLIC_DIR=public_html
      

   4. Remove the # symbol if present at the beginning
   5. Save the file

   This is particularly important for cPanel users where the default document root is public_html.

4. Check File Permissions

   Ensure the web server has read access to uploaded files:

   # Navigate to your Aikeedo directory
   cd /path/to/aikeedo
   
   # Set correct permissions for storage directory
   chmod -R 755 storage/
   
   # Set correct ownership (replace www-data with your web server user)
   chown -R www-data:www-data storage/
   

   Common web server users:

   • Ubuntu/Debian: www-data
   • CentOS/RHEL: apache
   • Nginx: nginx
5. Check Cloud Storage CORS Configuration

   If you’re using cloud storage (AWS S3, DigitalOcean Spaces, etc.), CORS issues may prevent file access:

   1. Check your cloud storage CORS configuration:

      • Ensure your bucket allows requests from your domain
      • Verify that the GET method is allowed (generally sufficient for file access)
      • Check that the correct headers are permitted

   2. Example CORS configuration for AWS S3:

      [
        {
          "AllowedHeaders": ["*"],
          "AllowedMethods": ["GET"],
          "AllowedOrigins": ["https://yourdomain.com", "https://www.yourdomain.com"]
        }
      ]
      

   3. Verify your storage configuration:

      • Check Settings > Storage in your admin panel
      • Ensure cloud storage credentials are correct
      • Verify the bucket/container name and region are accurate

   CORS misconfiguration can cause files to appear uploaded but return 404 errors when accessed. Always test file access after making CORS changes.

6. Verify Storage Path

   Check that your storage path is correctly configured:

   1. Go to Settings > Storage in the admin panel
   2. Verify the storage driver is set correctly (Local, S3, etc.)
   3. If using local storage, ensure the path is correct
   4. Test by uploading a new file

   If the new file is accessible, the configuration is correct. You may need to re-upload older files.

7. Clear Application Cache

   After making configuration changes:

   1. Navigate to Status page in the admin panel
   2. Click “Clear cache” to clear the application cache
   3. Test file access again

For production environments requiring secure file access or workspace-based file organization, cloud storage (S3, DigitalOcean Spaces) is recommended. File grouping and secure URL features are optimized for cloud storage and work most reliably in that environment, though they may also work on some local storage configurations.

Related Documentation:

• Secure URLs - Configure secure file access
• cPanel Installation - Document root configuration for cPanel

---

Generated Images/Videos Not Loading

Symptoms:

• Generated images or videos fail to display after creation
• Broken image/video placeholders appear instead of content
• 404 or 403 errors when accessing generated media files
• Files appear to generate successfully but cannot be viewed

Cause: Incomplete initial setup, cloud storage CORS misconfiguration, incorrect .env file configuration (especially for cPanel installations), or Secure URLs/Group files settings enabled when using local storage.

Solution:

1. Verify Initial Setup Completion

   Ensure you’ve completed all steps in the Initial Setup Guide:

   1. Verify your site domain is configured correctly in Settings > General
   2. Check that storage settings are properly configured in Settings > Storage settings
   3. Ensure all required integrations are set up if using cloud storage

   Skipping or incorrectly completing initial setup steps can prevent generated files from being accessible.

2. Check Cloud Storage CORS Configuration

   If you’re using cloud storage (AWS S3, DigitalOcean Spaces, Cloudflare R2, etc.), CORS misconfiguration is a common cause:

   1. Access your cloud storage provider’s console (AWS S3, DigitalOcean, etc.)
   2. Navigate to your bucket/container settings
   3. Review CORS configuration - it must allow requests from your domain
   4. Update CORS rules if needed:
   5. Save the CORS configuration
   6. Test by generating a new image or video

   CORS rules must include your exact domain (with protocol: https:// or http://). Wildcards may not work for all storage providers.

   See the Cloud Storage Overview and provider-specific guides for detailed CORS configuration instructions.

3. Check Secure URLs and Group Files Settings

   The Secure URLs and Group files options should only be enabled when using cloud storage (AWS S3, DigitalOcean Spaces, etc.):

   1. Navigate to Settings > Storage settings in the admin panel
   2. Review the Secure URLs and Group files settings
   3. If using local storage, ensure both options are disabled:
      • Secure URLs: Should be turned Off
      • Group files: Should be set to None
   4. If using cloud storage, these options can be enabled as needed
   5. Click “Save changes”

   Secure URLs and Group files are designed for cloud storage only. Enabling these options with local storage can cause generated files to be inaccessible.

   Changing these settings only affects newly generated files. Files that were already generated with the previous settings will remain unchanged. If the issue stems from Secure URLs, previously generated files can be made accessible by fixing file permissions (see the “Verify Storage Path and Permissions” step below). Otherwise, you may need to regenerate images or videos after adjusting these settings.

4. Verify .env File Configuration (cPanel Users)

   If you’re using cPanel, the .env file configuration is critical:

   1. Locate your .env file in the Aikeedo root directory (not in public_html)
   2. Find the PUBLIC_DIR setting - it may be commented out with #
   3. For main domain installations, ensure it’s set correctly:
      PUBLIC_DIR=public_html
      

   4. Remove the # symbol if the line is commented out
   5. Save the file

   If you’re using cPanel and the PUBLIC_DIR setting is missing or incorrect, generated files will not be accessible. This is a critical step that must be completed during installation.

   For add-on domains or subdomains in cPanel where the document root points directly to the public folder, you may not need to set PUBLIC_DIR or it should be set to public. Refer to the cPanel Installation Guide for your specific setup.

5. Verify Storage Path and Permissions

   Check that your storage configuration is correct:

   1. Navigate to Settings > Storage settings in the admin panel
   2. Verify the storage driver is set correctly (Local, S3, etc.)
   3. If using local storage, ensure the storage path is writable:
      # Check storage directory permissions
      ls -la /path/to/aikeedo/public/uploads/
      
      # Set correct permissions if needed
      chmod -R 755 /path/to/aikeedo/public/uploads/
      chown -R www-data:www-data /path/to/aikeedo/public/uploads/
      

   4. If using cloud storage, verify:
      • Bucket/container name is correct
      • Region is correctly configured
      • Access keys are valid and have proper permissions
      • Bucket/container exists and is accessible

   Test by generating a new image or video. If it loads correctly, the configuration is working.

For cPanel users: If you skipped or incorrectly completed the .env file configuration step during installation (specifically the PUBLIC_DIR=public_html setting), generated files will not load correctly. This is one of the most common causes of this issue on cPanel hosting. Refer to the cPanel Installation Guide and ensure you’ve completed the “Update the Environment File” step correctly.

Related Documentation:

• Initial Setup Guide - Complete setup configuration
• cPanel Installation - Critical .env file configuration
• Cloud Storage Overview - Cloud storage setup and CORS configuration
• Secure URLs - Secure file access configuration

---

Additional Troubleshooting Steps

If you’re still experiencing issues after trying the solutions above:

1. Fresh Installation: Consider a clean reinstall with fresh Aikeedo files
2. Server Configuration: Review web server configuration (Apache/Nginx) for PHP applications
3. PHP Configuration: Check php.ini for settings like:
   • max_execution_time
   • upload_max_filesize
   • post_max_size
   • memory_limit
4. Hosting Environment: Contact your hosting provider to ensure no server-side restrictions

Getting Additional Help

If you’ve tried the solutions above and still need assistance:

Before Contacting Support

1. Check Error Logs:

   • Browser console (F12 in most browsers)
   • Server error logs (/var/log/apache2/error.log or /var/log/nginx/error.log)
   • Application logs
   • PHP error logs

2. Verify Configuration:

   • Review Initial Setup
   • Check Application Configuration
   • Verify Server Requirements

3. Clear Caches:

   • Clear browser cache (Ctrl+Shift+R or Cmd+Shift+R)
   • Clear application cache from admin panel Status page

Need Additional Help?

Professional Support

Get expert help from our team with a paid support subscription

For support plan options and pricing, visit https://aikeedo.com/support/.

Before contacting support:

• Ensure you have an active support plan subscription
• Have your Aikeedo license key ready for validation

When contacting support, include:

• Your Aikeedo license key (for purchase validation)
• Detailed description of the issue
• Complete error messages (screenshots if possible)
• Steps to reproduce the problem
• PHP version and server environment details
• Aikeedo version number
• Relevant error log entries
• What troubleshooting steps you’ve already tried

Support is only available to users with active support plan subscriptions. Requests without valid license keys or active support plans will not be processed.

The more detailed information you provide, the faster our support team can help resolve your issue.

---

Related Guides

• Installation Guide
• Initial Setup
• Application Configuration
• Server Requirements
• Plans, Snapshots & Subscriptions