Skip to main content

Repeated connection errors, missing audio, or a shorter-than-expected encounter

Troubleshoot repeated “Unable to establish connection” or “Unable to contact the server” messages, incomplete transcripts, and unusually short encounter durations.

Written by Attend Health Team

If Attend repeatedly shows a connection error and your transcript is incomplete or the encounter duration is much shorter than the visit, some audio may not be reaching Attend. The steps below can help you find a working connection without needing technical expertise.

What you might notice

  • A message such as “Unable to establish connection” or “Unable to contact the server. Please check your internet connection” keeps returning after you dismiss it.

  • A long visit appears as a much shorter encounter, sometimes only one or two minutes.

  • The transcript contains only parts of the conversation, or no transcript is available.

  • A note has missing information, or is blank.

  • A short test works, but a longer session has problems.

Why this can happen

Attend sends audio to its servers in segments while you record. Something on your computer or network can interrupt or delay those connections. Possible causes include security software, a VPN or proxy, browser extensions, a network adapter, or the connection through your router.

Your microphone may still be working and the recording timer may continue even when uploads are failing. Browsing websites, having a good speed-test result, or staying connected to Zoom does not guarantee that every connection to Attend will succeed.

When audio segments do not reach processing, the saved duration can be shorter and the transcript can have gaps. A generated note does not confirm that the entire visit was captured. Review the transcript and note for completeness. A short duration by itself can also have other causes, so contact support if you are unsure.

Before you test

If this happens during a visit, avoid refreshing or closing an active recording as a troubleshooting step. Finish the encounter before restarting the browser or changing your connection, and keep the affected encounter available for support.

Use an ordinary conversation or read-aloud passage for testing, without patient information. Change one thing at a time and note whether the error returns. A 2 minute test is a useful starting point. If you normally use Zoom or another telehealth app, include it in the test.

1. Try a different connection

If you use an Ethernet cable

Connect to your home Wi-Fi, then unplug the Ethernet cable so the computer actually uses Wi-Fi. Start a new test recording with the same browser and microphone.

If Wi-Fi works reliably, you can continue using it. There is no need to repair Ethernet before using Attend over a working Wi-Fi connection. Leave the cable unplugged while using that connection.

If Wi-Fi also has problems

If available, try your phone’s hotspot for a test. Disconnect Ethernet and make sure the computer has joined the hotspot rather than your home Wi-Fi. This tests a different network path.

  • Wi-Fi works but Ethernet does not: the wired connection, adapter, or settings specific to it are likely involved.

  • The hotspot works but your home connection does not: the home network or the route it uses may be involved.

  • Every connection fails on the same computer: try the browser and computer checks below. This does not, by itself, prove that the computer is the cause.

These comparisons help narrow the problem; they do not identify a particular faulty component on their own.

2. Try another browser or computer

After ending the test recording, close and reopen your browser. Install any available browser update. If you use Chrome, try a fresh test in Edge, or vice versa, and allow microphone access when prompted.

If one browser works and another does not, an extension or browser setting may be involved. If both fail, a setting or component shared by the computer or network may be involved. If another computer is available, testing it on the same connection can help narrow this down further.

If the microphone indicator does not respond when you speak, also check microphone permissions and our audio setup guidance.

3. Check software that manages your connection

Antivirus web protection, firewalls, VPNs, proxies, and privacy or security extensions can affect connections to Attend. They may behave differently on Ethernet and Wi-Fi. Their presence does not mean they are causing the problem, and an empty blocked-connections history does not rule out delays.

Note which of these tools you use and whether any were recently updated. Automatic updates can change behavior even if you have not intentionally changed your setup. If you use an optional personal VPN, you can compare a nonclinical test with it disconnected. For security software or a required VPN, ask Attend support or the software provider to help check the settings rather than turning off protection broadly.

4. Optional: investigate Ethernet

If Wi-Fi is working, these steps are optional:

  • Try a different Ethernet cable.

  • Try a different Ethernet port on the router.

  • Restart the computer and router when you are not in a visit.

  • If the cable connects through a USB adapter or docking station, try another adapter or connect directly to the computer if it has an Ethernet port.

If the issue continues, your computer manufacturer’s support team can help check the Ethernet adapter and driver. Your router or security-software provider can help with settings specific to the wired connection. You do not need an IT department to contact these support teams.

When to contact Attend support

Contact us through the support chat in Attend or email [email protected] if errors continue, you cannot find a reliable connection, or a transcript remains incomplete.

Please include:

  • The date, approximate start time, and time zone of an affected encounter, plus its link if available.

  • The exact error message and how long the recording ran before it appeared.

  • Your browser and whether you were using Ethernet, Wi-Fi, or a hotspot.

  • Whether Zoom or another telehealth app was running.

  • Which connection or browser tests worked and which did not, and any security software or VPN you use.

Keep screenshots free of patient information. You do not need to collect technical logs yourself: support can guide you through a browser Network check during a nonclinical test to see where the connection gets stuck.

Changing to a working connection can help future uploads, but it does not automatically restore audio missing from an earlier encounter. Support can review what reached Attend and advise on what is available.

Did this answer your question?