Troubleshooting
Common issues and solutions when using local Wikibase with FOVEA.
Connection Issues
"Failed to fetch Wikidata config from backend"
Cause: Frontend can't reach the backend /api/config endpoint.
Solutions:
- Ensure the backend is running:
docker compose ps - Check backend logs:
docker compose logs backend - Verify
VITE_API_URLpoints to the correct backend URL
"Error searching Wikidata" in browser console
Cause: Frontend can't reach the Wikibase API.
Solutions:
- Verify Wikibase is running:
docker compose -f docker-compose.wikibase.yml ps - Check Wikibase health:
curl http://localhost:8181/api.php?action=query&meta=siteinfo&format=json - Verify CORS is enabled (check browser Network tab for CORS errors)
- Ensure
WIKIDATA_URLis accessible from the browser
Wikibase not starting
Cause: Service dependencies not ready.
Solutions:
- Check MySQL is healthy:
docker compose -f docker-compose.wikibase.yml logs wikibase-mysql - Check Elasticsearch:
docker compose -f docker-compose.wikibase.yml logs wikibase-elasticsearch - Wait for health checks: Services need 60+ seconds to initialize
Search Issues
Search returns no results
Causes:
- Elasticsearch not indexed
- No data loaded into Wikibase
Solutions:
- Check if data exists via API:
curl "http://localhost:8181/api.php?action=wbsearchentities&search=human&language=en&format=json" - Trigger Elasticsearch reindex:
docker compose -f docker-compose.wikibase.yml exec wikibase php maintenance/run.php CirrusSearch/ForceSearchIndex.php - Run the data loader to populate Wikibase
Search is slow
Cause: Elasticsearch needs more resources.
Solutions:
- Increase Elasticsearch memory in
docker-compose.wikibase.yml:environment:
- "ES_JAVA_OPTS=-Xms1g -Xmx1g" - Ensure Elasticsearch data is on fast storage
Data Loading Issues
"Entity creation failed" errors
Causes:
- Authentication failed
- Entity already exists
- Invalid entity data
Solutions:
- Check loader credentials match Wikibase admin:
echo $WIKIBASE_ADMIN_USER $WIKIBASE_ADMIN_PASS - View detailed error logs:
LOG_LEVEL=DEBUG docker compose -f docker-compose.wikibase.yml --profile loader run --rm wikibase-loader
SPARQL query fails
Cause: Wikidata query service rate limiting or timeout.
Solutions:
- Add
LIMITclause to your query - Run during off-peak hours
- Use smaller batches with the config file method
"Dump file not found"
Cause: File path not accessible in container.
Solution: Mount the data directory:
docker compose -f docker-compose.wikibase.yml --profile loader run \
-v /path/to/data:/data:ro \
--rm wikibase-loader
CORS Issues
"Access-Control-Allow-Origin" error
Cause: CORS not properly configured.
Solutions:
- Verify
LocalSettings.d/cors.phpis mounted - Add your frontend origin to allowed origins
- Check browser developer tools for specific CORS error
Preflight request fails
Cause: OPTIONS request not handled.
Solution: Ensure Wikibase handles OPTIONS requests:
// In LocalSettings.d/cors.php
$wgCrossSiteAJAXdomains = ['*'];
Memory Issues
Elasticsearch out of memory
Symptoms: Container restarts, "circuit_breaking_exception" errors.
Solution: Increase memory limits:
environment:
- "ES_JAVA_OPTS=-Xms1g -Xmx1g"
ulimits:
memlock:
soft: -1
hard: -1
Wikibase PHP memory errors
Solution: Increase PHP memory limit:
environment:
- PHP_MEMORY_LIMIT=512M
Data Persistence
Data lost after restart
Cause: Volumes not configured.
Solution: Verify volumes in docker-compose.wikibase.yml:
volumes:
wikibase-mysql-data:
wikibase-elasticsearch-data:
Cannot delete data
Solution: Remove volumes explicitly:
docker compose -f docker-compose.wikibase.yml down -v
Getting Help
- Check container logs:
docker compose logs <service-name> - Verify service health:
docker compose ps - Test API directly with curl
- Check browser developer tools for network errors
If issues persist, please open an issue on GitHub with:
- Docker Compose version
- Container logs
- Browser console errors
- Steps to reproduce