Diagnosis:

SELECT videoid, posterpath, previewpath

FROM tblVideoFiles WHERE videoid = <ID>;

Common causes:

• ImageMagick not installed (convert command needed for contact sheets)
• FFmpeg failed during thumbnail extraction
• CDN upload for thumbnails failed (check storage server logs)

Solution:

# Verify ImageMagick

which convert

convert --version

Reprocess thumbnails only

php ct/admin/cron/videoprocessor.php --video-id=<ID> --thumbnails-only

Diagnosis:

1. Check storage server configuration:

SELECT  FROM tblStorageServers WHERE enabled = 1;

   SELECT  FROM tblStorageServerGroups;

1. Check file location records:

SELECT  FROM tblStorageFileLocations WHERE videoid = <ID>;

1. Verify CDN credentials and connectivity from the admin panel.

File sharding formula: floor(videoid / 1000) 1000
Example: Video ID 4321 goes to shard 4000:

https://cdn.example.com/videos/4000/4321/webmp4/web.mp4

Solution: Check CDN credentials, test connectivity, verify storage server group assignment.

Diagnosis:

1. Check server status:

SELECT serverid, title, statusid, currentjobs, maxconcurrentjobs,

          lastheartbeat, loadaverage

   FROM tblConversionServers WHERE statusid = 1;

1. Check conversion logs:

SELECT  FROM tblConversionServerLogs
   WHERE loglevel IN ('WARNING', 'ERROR')
   ORDER BY createdat DESC LIMIT 20;

1. Verify settings:

SELECT  FROM tblSettings WHERE settinggroup = 'videoprocessing';

Solution:

• Ensure conversionuseremoteservers is set to 1
• Verify remote server SSH/FTP connectivity
• Check that FFmpeg is installed on remote servers
• Verify conversionfallbacktolocal is 1 for automatic fallback

Common causes:

1. Wrong user ID column - tblCMSUsers uses id, NOT userid:

-- CORRECT
   SELECT id, username, accountstatus FROM tblCMSUsers WHERE id = 123;

-- WRONG (column doesn't exist)
SELECT userid FROM tblCMSUsers;

1. Wrong status column - tblCMSUsers uses accountstatus, NOT status:

-- CORRECT
   WHERE accountstatus = 'active'

-- WRONG
WHERE status = 'active'

1. JWT token expired - Tokens have an expiration time. Re-authenticate:

POST /ct/api/v1/auth/login

1. JWT secret mismatch - Verify in config:

$jwtsecret = md5($domain . $licensekey);

Diagnosis:

1. Check ApiClient base URL:

// Browser console

   const api = new ApiClient();

   console.log(api.baseUrl);

1. Check Network tab (F12) for the failing request - note the URL, status code, and response body.

1. Verify the endpoint exists in the router:

• File: ct/api/v1/index.php
• 90+ endpoints defined

1. Check JWT token:

console.log(localStorage.getItem('authtoken'));

Solution: Verify base URL detection, check endpoint exists in router, verify authentication token if endpoint requires auth.

Diagnosis:

1. Check if data exists in the database:

SELECT COUNT() FROM tblVideos WHERE status = 'active';

   SELECT COUNT() FROM tblCamsPerformers WHERE status = 1 AND enabled = 1;

1. Check feature toggles - some API endpoints return empty when features are disabled.

1. Check query parameters - pagination offset may be beyond available data.

Solution: Verify data exists in the database and feature toggles are enabled.

Cause: API and frontend on different domains or ports.

Solution: Ensure the API sets proper CORS headers:

header('Access-Control-Allow-Origin: https://yourdomain.com');

header('Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS');

header('Access-Control-Allow-Headers: Content-Type, Authorization');

Or in .htaccess:

Header set Access-Control-Allow-Origin "https://yourdomain.com"

Diagnosis:

1. Test the features API endpoint:

curl https://yourdomain.com/ct/api/v1/features

1. Check feature cache - APCu may have stale data:

// Clear APCu cache
   apcuclearcache();

1. Check featurehelper.php - all features default to enabled if not found in database.

1. Verify feature settings in admin panel: Admin Panel -> Feature Toggles

Solution: Clear APCu cache, verify feature settings in admin panel, check that the API is reachable.

Diagnosis:

1. Verify lang/en.json exists and is valid JSON:

php -r "jsondecode(filegetcontents('lang/en.json')); echo jsonlasterrormsg();"

1. Check file permissions (must be readable by web server).

1. Verify the translation key exists in the JSON:

# Search for a specific key
   grep -o '"videos"' lang/en.json

1. Check for typos in nested keys - videos.sortby.videoid requires all parent keys to exist.

Solution: Validate JSON syntax, check file permissions, verify key path exists in the translation file.

Rules:

1. Only use assets/css/style.css - no external CSS frameworks (Bootstrap, Tailwind, etc.)
2. Check for specificity conflicts with Style Manager overrides (Phase 12)
3. Verify the stylesheet is loaded in includes/header.php
4. Check browser cache - append ?v=timestamp to stylesheet URL

Solution:

// Force cache bust

<link rel="stylesheet" href="assets/css/style.css?v=<?= time() ?>">

Diagnosis:

1. Check featuredarkmode is enabled in feature toggles
2. Verify localStorage is available:

console.log(localStorage.getItem('comusdarkmode'));

1. Confirm body.dark-mode CSS rules exist in assets/css/style.css
2. Check that both body and html elements get the class:

document.body.classList.contains('dark-mode');

   document.documentElement.classList.contains('dark-mode');

Solution: Enable the feature toggle, clear localStorage, verify CSS dark mode rules exist.

Diagnosis:

1. Check securemedia.php token generation:

GET /securemedia.php?token=...&type=video&id=...

Solution: Check API response, verify access control, ensure HLS.js or native HLS support is available, verify media token is valid.

Critical rule: ALL external links MUST route through click.php. Direct links incur a 100% skim penalty.

Correct format:

// PHP

$url = sprintf('click.php?url=%s&type=video&id=%d',

    urlencode($externalurl), $videoid);

// JavaScript
const url = click.php?url=${encodeURIComponent(externalUrl)}&type=${type}&id=${id};

Diagnosis:

1. Check that click.php exists at the project root
2. Verify tblClickTracking is receiving records:

SELECT  FROM tblClickTracking ORDER BY clickid DESC LIMIT 10;

1. Check tblContentClicks for aggregated counts

Solution: Audit all external links to ensure they use click.php. Use browser DevTools to verify link href attributes.

Cause: SEO data must be loaded BEFORE header.php is included.

Correct order:

// 1. Load config and API helper FIRST

requireonce DIR . '/ct/dat/config.inc.php';

requireonce DIR . '/includes/InternalApiHelper.php';

// 2. Fetch data for SEO
$api = InternalApiHelper::getInstance();
$videoData = $api->getVideoForSeo($videoId);

// 3. NOW include header (generates meta tags from loaded data)
requireonce DIR . '/includes/header.php';

Diagnosis:

• Check ct/dat/seosettings.json for template configuration

Solution: Ensure SEO data is loaded before header, verify SeoHelper.php and InternalApiHelper.php are working.

Diagnosis (in order):

1. Check cron jobs are running:

php ct/admin/cronupdatecams.php

1. Verify API credentials in Admin -> Cam Settings
2. Check tblCamsSites for enabled sites:

SELECT recordnum, name, enabled FROM tblCamsSites WHERE enabled = 1;

1. Verify featurelivecams is enabled in feature toggles
2. Check logs:

tail -50 ct/logs/cron-update.log

1. Test the internal API directly:

GET /ct/api/v1/cams/online?perpage=1&fast=1

Solution: Enable cron jobs, verify API credentials, enable the feature toggle.

Diagnosis:

1. Run the cron update manually:

php ct/admin/cronupdatecams.php

1. Check if external API is responding:

curl --location 'https://performersext-api.pcvdaa.com/performers-ext/?token=<TOKEN>&gender=f&live=true&size=1&page=1' \

   --header 'x-api-key: <APIKEY>' \

   --header 'User-Agent: ComusThumbz/1.0'

1. Verify API token hasn't expired
2. Check database for online performers:

SELECT COUNT() FROM tblCamsPerformers WHERE status = 1;

Solution: Run cron manually, verify external API credentials are valid.

Causes:

1. Missing or invalid x-api-key header
2. Missing User-Agent header (returns HTML error page)
3. API key revoked by CrakRevenue

Diagnosis:

-- Check stored API credentials

SELECT recordnum, name, apiData, parameters FROM tblCamsSites WHERE enabled = 1;

Solution: Verify x-api-key (stored in tblCamsSites.apiData) and ensure requests include a User-Agent header. Contact CrakRevenue if key was revoked.

Causes:

1. Invalid or missing token parameter
2. Requesting brands not authorized for your token
3. Token is domain-bound and being used from wrong domain

Diagnosis:

-- Check token values

SELECT recordnum, name, parameters, brand FROM tblCamsSites WHERE enabled = 1;

Solution: Verify token (stored in tblCamsSites.parameters), ensure you only request authorized brands, verify token is for your domain.

Diagnosis:

1. Use the debug panel: add ?debug=1 to the URL to see timing breakdown
2. Use the full debug tool:

https://yourdomain.com/tools/camperformersdebug.php?key=comus2025

Optimization checklist:

1. Enable fast mode - ensure frontend uses ?fast=1 parameter
2. Check APCu is installed and enabled:

php -m | grep apcu

1. Verify stats cache cron is running:

/2     php /path/to/ct/admin/cron/updatecamperformerstats.php

1. Reduce perpage to 24 or less
2. Check for blocking database queries (see Table Locks)

Three-layer caching strategy:

• Layer 1: APCu in-memory cache (30s TTL)
• Layer 2: Database stats cache (tblCamsPerformersStatsCache)
• Layer 3: Fast mode (skip COUNT queries entirely)

Solution: Enable all three caching layers and verify cron jobs are running.

Cause: External performer links not routed through click.php.

Required format:

$clickurl = sprintf('click.php?url=%s&type=camperformer&id=%d',

    urlencode($performer['chatroomurl']), $performer['performerid']);

Also verify:

• Affiliate ID is present in the roomUrl from the external API
• tblClickTracking is recording cam performer clicks
• Performer chatroomurl contains valid affiliate tracking parameters

Solution: Audit all performer links to ensure click.php routing. Verify affiliate ID in room URLs.

Diagnosis:

# Check container status

docker ps -a | grep livekit

Check logs

docker logs livekit

Verify Docker is running

systemctl status docker

Common causes:

1. Port conflicts (7880, 7881, 40000-40100 already in use)
2. Invalid livekit-config.yaml syntax
3. Docker not installed or not running
4. Insufficient permissions

Solution:

# Check port availability

ss -tlnp | grep 7880

Restart container

docker restart livekit

Or recreate

docker rm -f livekit
docker run -d --name livekit --network host \
  -v $(pwd)/livekit-config.yaml:/livekit.yaml:ro \
  livekit/livekit-server:latest --config /livekit.yaml

Diagnosis:

1. Check LiveKit config in ct/dat/config.inc.php:

define('LIVEKITHOST', 'wss://yourdomain.com/livekit/');

   define('LIVEKITAPIKEY', 'yourkey');

   define('LIVEKITAPISECRET', 'yoursecret');

1. Verify WebSocket connection from browser:

• Open browser console (F12)
• Look for WebSocket connection errors
• Check if wss:// URL is accessible

1. Verify firewall rules:

sudo ufw status | grep -E "7880|7881|40000"

Required ports:

• 7880 - WebSocket signaling
• 7881 - TCP media
• 40000-40100 - UDP media (WebRTC)

Solution: Verify LiveKit credentials match between config and server, check firewall ports, ensure SSL is configured for wss://.

Causes:

1. UDP ports blocked - WebRTC falls back to TCP (higher latency)
2. Server overloaded
3. Client bandwidth insufficient

Solution:

1. Ensure UDP ports 40000-40100 are open
2. Check server load:

top -bn1 | head -5

1. Verify nodeip in livekit-config.yaml matches your public IP

Diagnosis:

1. Check tblLiveStreamChat for recent messages:

SELECT  FROM tblLiveStreamChat ORDER BY id DESC LIMIT 10;

1. Verify WebSocket connection in browser console
2. Check that the stream ID is valid in tblLiveStreams

Solution: Verify stream exists, WebSocket is connected, and chat API endpoint is responding.

Diagnosis:

-- Check recent token transactions

SELECT  FROM tblTokenTransactions ORDER BY createdat DESC LIMIT 10;

-- Check creator tips
SELECT FROM tblCreatorTips ORDER BY createdat DESC LIMIT 10;

-- Check user token balance
SELECT id, username, tokenbalance FROM tblCMSUsers WHERE id = <USERID>;

Common causes:

• Insufficient token balance
• Creator profile not verified
• API endpoint error (check response)

Solution: Verify sender has sufficient tokens, creator profile is active, and POST /tips/send returns success.

Cause: Earnings aggregation cron job not running.

Required cron:

     php /path/to/ct/admin/cron/aggregatecreatorearnings.php

Diagnosis:

-- Check daily earnings records

SELECT  FROM tblCreatorEarningsDaily

WHERE creatorid = <ID>

ORDER BY earningdate DESC LIMIT 10;

-- Check if raw transactions exist
SELECT SUM(amount) as total
FROM tblTokenTransactions
WHERE recipientid = <ID> AND createdat >= CURDATE();

Solution: Ensure the aggregatecreatorearnings.php cron job is running every minute.

Diagnosis:

1. Check featurecreatorposts is enabled
2. Verify posts exist:

SELECT  FROM tblCreatorPosts WHERE creatorid = <ID> ORDER BY createdat DESC LIMIT 10;

1. Check post visibility settings (public vs subscriber-only vs PPV)
2. Verify media uploads if post contains images/video:

SELECT  FROM tblCreatorPostMedia WHERE postid = <POSTID>;

Solution: Enable the feature toggle, verify posts exist in the database, check access control for post visibility.

Diagnosis:

-- Check active subscriptions

SELECT  FROM tblCreatorSubscriptions

WHERE subscriberid = <USERID> AND status = 'active';

-- Check subscription packages
SELECT FROM tblCreatorSubscriptionPackages WHERE creatorid = <CREATORID>;

Solution: Verify featuresubscriptions is enabled, check payment processing, verify subscription record status.

Diagnosis:

1. Test the auth API directly:

POST /ct/api/v1/auth/login

   {"username": "test", "password": "test"}

1. Check user account status:

SELECT id, username, accountstatus, emailverified
   FROM tblCMSUsers WHERE username = 'testuser';

Remember: column is accountstatus, NOT status.

1. Check if account is locked, suspended, or unverified.

Solution: Verify account exists, is active (accountstatus = 'active'), and email is verified if required.

Diagnosis:

1. Check auth/setsession.php is being called after login
2. Verify session cookie is being set:

document.cookie  // Check for PHP session cookie

1. Check PHP session configuration:

vardump(sessionstatus());  // Should be PHPSESSIONACTIVE

   vardump($SESSION);         // Should contain user data

Solution: Ensure setsession.php is called after API login returns JWT token. Verify session cookie domain matches.

Diagnosis:

1. Check feature2fa is enabled
2. Verify server time is accurate (TOTP codes are time-based):

date

   timedatectl status

1. Time drift of >30 seconds will cause code rejection.

Solution: Sync server time with NTP, verify 2FA secret is stored correctly.