Troubleshooting¶
| Symptom | Likely cause | What to do |
|---|---|---|
Deploy fails at start, TypeError: 'coroutine' object is not iterable |
The app run as WSGI | [run].start must be myxo serve layout.toml, which serves the app as ASGI (it is in hop3.toml) |
| 502 from nginx | The app isn't listening on $PORT |
hop3 logs: a startup error, often SECRET_KEY or the database |
| "The database schema is out of date" from a command | Migrations not applied | Deploy again (they run before start), or alembic upgrade head |
| Visits without country or network | GeoIP databases missing | hop3 logs for jobs.geoip; abilian-analytics geoip update to download now |
| Every visit from the same network | Proxy address taken for the visitor's | X-Forwarded-For (see step 4) |
| A site's hits don't show | Hostname unclaimed, CSP, or ad blocker | Unclaimed hostnames page; browser developer tools |
| Too many visits counted from one odd network | A hosting provider the lists miss | Excluded traffic page → leave it out |
| A slow page | A heavy query, or a long period | The bar in the bottom right corner, shown to administrators: the page's time and SQL queries; click it for each query's text and time |
For a deploy that fails on Hop3's side, hop3 logs --app abilian-analytics and hop3 help come first.