CrankWheel technical diagnostics
This page checks whether CrankWheel will work for you. It tests your connection to our servers, then lets you check your screen sharing, camera and microphone. Nothing leaves your computer. Your recording and camera preview stay in this browser tab. At the end you can download the results or copy them, and send them to us or to your IT team.
Use the buttons in the bar at the bottom of the screen. Each needs your permission, so each one is separate, and you can skip any of them. We show you a live preview, play your recording back, then ask you to confirm it looked and sounded right.
Send these results to whoever is helping you.
Email CrankWheel supportWhat this page checks
- Your connection to CrankWheel. This is the only part that has to work. If it passes, CrankWheel will work for you.
- High quality screen sharing. Optional. If it fails, CrankWheel still works, at lower quality.
- Computer audio. Optional. If it fails, you can use phone audio.
- Your screen, camera and microphone. These test this device, not your network. You see a live preview of your screen and camera, and you can play back a short recording of your microphone, so you can confirm for yourself that everything looks and sounds right.
What this page cannot check
- How fast screen sharing will actually be, or how much data is lost along the way.
- Computer audio as a live test. We can only tell you whether the kind of connection it needs is available.
For IT and network teams
CrankWheel viewers need outbound HTTPS on TCP 443 to *.crankwheel.com and meeting.is, including WebSocket upgrades on the /engine.io/ path. Idle connections should be allowed to live for at least 60 seconds; CrankWheel sends a keepalive every 4 seconds.
For better screen sharing quality, presenters can also reach turn-<region>.crankwheel.com on UDP 3478, TCP 3478 and TCP 443. This is optional; CrankWheel works without it.
Computer audio additionally needs outbound UDP to the regional CrankWheel server. Without it, use phone audio.