Troubleshooting Common TourneyKing Setup and Sync Issues

Running a tournament with TourneyKing should be reliable, but like any web-based event platform there are a number of recurring setup and synchronization issues tournament organizers encounter. This guide covers the most common problems and gives practical, step-by-step solutions so you can troubleshoot quickly and get back to running matches.

Common categories of problems

- Authentication and account access

- Bracket and match result synchronization

- Overlay/stream integration (OBS, Streamlabs, browser sources)

- Import/export and CSV problems

- Network, firewall, and local device permissions

- Browser and caching issues

- Data consistency (duplicates, missing players)

Quick troubleshooting checklist (start here)

1. Confirm you are logged into the correct TourneyKing account and have the right event selected.

2. Use an up-to-date browser (Chrome, Edge, Firefox). Disable extensions or test in an incognito/private window.

3. Refresh the page and verify other admins see the same state.

4. Check TourneyKing status (official status page or Twitter) for outages.

5. Collect error screenshots, browser console logs (F12 → Console/Network), timestamps, and event ID before contacting support.

Authentication and account access

- Wrong account or permissions: Confirm the account you’re using is listed as an admin or organizer on the event. If multiple people manage the event, one admin can re-add or elevate permissions for others.

- Session expiry: Log out and log back in. If you use single sign-on (Google, Discord, Steam), ensure that provider is currently accessible.

- Two-factor or email verification: If you rely on email links, check spam folders and ensure the email domain isn’t blocked by your mail provider.

Bracket and match sync issues

- Results not appearing for viewers: Ensure the match result was submitted and saved. Some interfaces require confirmation or an explicit “Publish” button.

- Delayed updates: TourneyKing uses server-side processing; allow a short delay. If delays are longer than a minute, check server status and your local network.

- Conflicting edits: If two admins edit bracket state simultaneously, conflicts can occur. Coordinate edits or have one admin handle match reporting.

- Offline reporting: If you input results while offline, make sure the device reconnects to the internet so changes can sync to the server.

- Pairing errors: Verify tournament settings (bracket type, number of rounds, seeding method). Incorrect initial seeding or round count will produce unexpected pairings.

Overlay and streaming integration

- Browser source not updating in OBS/Streamlabs: Use the overlay URL TourneyKing provides and set it as a browser source. If the overlay shows old data, click the browser source’s “Refresh” or enable the “Reload CSS/JS” option.

- HTTPS and mixed-content issues: Ensure the overlay URL is HTTPS. If your stream software or page blocks insecure content, overlays won’t load.

- CORS/blocked requests: If console logs show blocked network requests, check if a browser extension, firewall, or corporate network is blocking. Test locally from the same machine in a standard browser tab.

- Localhost/Local Network overlays: On macOS, browser-based apps sometimes block local network access—grant the browser permission for Local Network in System Preferences. On Windows, confirm the app can accept local connections.

- Transparency and rendering: In OBS, enable “Allow Transparency” and use a proper base resolution. If elements aren’t visible, disable hardware acceleration in the browser used for the browser source.

CSV import and data formats

- Encoding issues: Save CSVs as UTF-8 without BOM. Non-UTF encodings can corrupt special characters.

- Incorrect headers: Follow the exact header names and column order the TourneyKing importer expects. Check the import preview for mapping errors.

- Delimiters: Ensure your system’s regional settings don’t convert commas to semicolons. Use the explicit delimiter the importer expects.

- Duplicate entries: Remove extra whitespace and duplicates before importing. If IDs or emails must be unique, ensure no duplicates exist.

Network, firewall, and antivirus

- Ports and WebSockets: Some platforms use WebSockets. Corporate firewalls or restrictive NATs may block persistent connections. Test on a home network or mobile hotspot to isolate.

- Windows Firewall and AV tools: If the client or local helper app is blocked, allow it through Windows Firewall and your antivirus. Add exceptions for your browser and any local TourneyKing helper applications.

- Proxy/VPN: Proxies and certain VPNs can interfere with real-time syncing. Disable them during the event if possible.

Browser and cache problems

- Cache and stale resources: Clear cache or use an incognito window. A hard refresh (Ctrl+F5) can resolve stale scripts or styles.

- Extensions interfering: Ad blockers, privacy extensions, or script blockers often break overlays and API calls. Temporarily disable them.

- Developer console: Use F12 → Network to see failing requests and F12 → Console for JavaScript errors. These logs are very helpful for support.

Device-specific tips (Windows and macOS)

- Windows: Run browsers as administrator only if required by a local helper app. Check Task Manager for conflicting apps that take audio/video devices.

- macOS: For overlays and local web apps, grant camera/microphone access and “Local Network” access in System Preferences → Security & Privacy. If a browser source shows just a white box in OBS, give the browser permission to record the screen (Screen Recording permission).

When to update or reinstall

- If you encounter persistent, unusual behavior after checking other items, update your browser and any local helper apps to the latest version.

- Clear the app’s cache and, if necessary, reinstall. Always back up or export any local data you need before reinstall.

What logs and information to collect before contacting support

- Event ID and public URL

- Exact timestamp(s) (with timezone) when the issue happened

- A concise description of the steps to reproduce the issue

- Screenshots or short screen recordings showing the problem

- Browser console logs (F12 → Console and Network export)

- CSV file (if import issues) and a sample of rows causing errors

- Network environment (home, school, LAN, VPN) and whether other admins are affected

Providing this will speed resolution.

Preventative practices

- Test your complete workflow (registration → seeding → matches → overlay) before tournament day with a small mock event.

- Maintain a backup admin account or co-organizer who can take over if one account has issues.

- Keep documentation and templates for CSV imports and participant instructions.

- Schedule a “tech check” 15–30 minutes before the event for overlays and streaming.

Conclusion

Most TourneyKing issues come down to permissions, cached resources, network restrictions, or simple input mistakes (wrong event ID, improper CSV format). Systematically check the quick checklist, reproduce the problem in an isolated environment (another browser or network), capture logs and screenshots, and only then escalate to support with detailed information. With the right diagnostics, many issues can be resolved quickly and with minimal disruption to your event.

Troubleshooting Common TourneyKing Setup and Sync Issues Running a tournament with TourneyKing should be reliable, but like any web-based event platform there are a number of recurring setup and synchronization issues tournament organizers encounter. This guide covers the most common problems and gives practical, step-by-step solutions so you can troubleshoot quickly and get back to running matches. Common categories of problems - Authentication and account access - Bracket and match result synchronization - Overlay/stream integration (OBS, Streamlabs, browser sources) - Import/export and CSV problems - Network, firewall, and local device permissions - Browser and caching issues - Data consistency (duplicates, missing players) Quick troubleshooting checklist (start here) 1. Confirm you are logged into the correct TourneyKing account and have the right event selected. 2. Use an up-to-date browser (Chrome, Edge, Firefox). Disable extensions or test in an incognito/private window. 3. Refresh the page and verify other admins see the same state. 4. Check TourneyKing status (official status page or Twitter) for outages. 5. Collect error screenshots, browser console logs (F12 → Console/Network), timestamps, and event ID before contacting support. Authentication and account access - Wrong account or permissions: Confirm the account you’re using is listed as an admin or organizer on the event. If multiple people manage the event, one admin can re-add or elevate permissions for others. - Session expiry: Log out and log back in. If you use single sign-on (Google, Discord, Steam), ensure that provider is currently accessible. - Two-factor or email verification: If you rely on email links, check spam folders and ensure the email domain isn’t blocked by your mail provider. Bracket and match sync issues - Results not appearing for viewers: Ensure the match result was submitted and saved. Some interfaces require confirmation or an explicit “Publish” button. - Delayed updates: TourneyKing uses server-side processing; allow a short delay. If delays are longer than a minute, check server status and your local network. - Conflicting edits: If two admins edit bracket state simultaneously, conflicts can occur. Coordinate edits or have one admin handle match reporting. - Offline reporting: If you input results while offline, make sure the device reconnects to the internet so changes can sync to the server. - Pairing errors: Verify tournament settings (bracket type, number of rounds, seeding method). Incorrect initial seeding or round count will produce unexpected pairings. Overlay and streaming integration - Browser source not updating in OBS/Streamlabs: Use the overlay URL TourneyKing provides and set it as a browser source. If the overlay shows old data, click the browser source’s “Refresh” or enable the “Reload CSS/JS” option. - HTTPS and mixed-content issues: Ensure the overlay URL is HTTPS. If your stream software or page blocks insecure content, overlays won’t load. - CORS/blocked requests: If console logs show blocked network requests, check if a browser extension, firewall, or corporate network is blocking. Test locally from the same machine in a standard browser tab. - Localhost/Local Network overlays: On macOS, browser-based apps sometimes block local network access—grant the browser permission for Local Network in System Preferences. On Windows, confirm the app can accept local connections. - Transparency and rendering: In OBS, enable “Allow Transparency” and use a proper base resolution. If elements aren’t visible, disable hardware acceleration in the browser used for the browser source. CSV import and data formats - Encoding issues: Save CSVs as UTF-8 without BOM. Non-UTF encodings can corrupt special characters. - Incorrect headers: Follow the exact header names and column order the TourneyKing importer expects. Check the import preview for mapping errors. - Delimiters: Ensure your system’s regional settings don’t convert commas to semicolons. Use the explicit delimiter the importer expects. - Duplicate entries: Remove extra whitespace and duplicates before importing. If IDs or emails must be unique, ensure no duplicates exist. Network, firewall, and antivirus - Ports and WebSockets: Some platforms use WebSockets. Corporate firewalls or restrictive NATs may block persistent connections. Test on a home network or mobile hotspot to isolate. - Windows Firewall and AV tools: If the client or local helper app is blocked, allow it through Windows Firewall and your antivirus. Add exceptions for your browser and any local TourneyKing helper applications. - Proxy/VPN: Proxies and certain VPNs can interfere with real-time syncing. Disable them during the event if possible. Browser and cache problems - Cache and stale resources: Clear cache or use an incognito window. A hard refresh (Ctrl+F5) can resolve stale scripts or styles. - Extensions interfering: Ad blockers, privacy extensions, or script blockers often break overlays and API calls. Temporarily disable them. - Developer console: Use F12 → Network to see failing requests and F12 → Console for JavaScript errors. These logs are very helpful for support. Device-specific tips (Windows and macOS) - Windows: Run browsers as administrator only if required by a local helper app. Check Task Manager for conflicting apps that take audio/video devices. - macOS: For overlays and local web apps, grant camera/microphone access and “Local Network” access in System Preferences → Security & Privacy. If a browser source shows just a white box in OBS, give the browser permission to record the screen (Screen Recording permission). When to update or reinstall - If you encounter persistent, unusual behavior after checking other items, update your browser and any local helper apps to the latest version. - Clear the app’s cache and, if necessary, reinstall. Always back up or export any local data you need before reinstall. What logs and information to collect before contacting support - Event ID and public URL - Exact timestamp(s) (with timezone) when the issue happened - A concise description of the steps to reproduce the issue - Screenshots or short screen recordings showing the problem - Browser console logs (F12 → Console and Network export) - CSV file (if import issues) and a sample of rows causing errors - Network environment (home, school, LAN, VPN) and whether other admins are affected Providing this will speed resolution. Preventative practices - Test your complete workflow (registration → seeding → matches → overlay) before tournament day with a small mock event. - Maintain a backup admin account or co-organizer who can take over if one account has issues. - Keep documentation and templates for CSV imports and participant instructions. - Schedule a “tech check” 15–30 minutes before the event for overlays and streaming. Conclusion Most TourneyKing issues come down to permissions, cached resources, network restrictions, or simple input mistakes (wrong event ID, improper CSV format). Systematically check the quick checklist, reproduce the problem in an isolated environment (another browser or network), capture logs and screenshots, and only then escalate to support with detailed information. With the right diagnostics, many issues can be resolved quickly and with minimal disruption to your event.

You May Also Like