Guides
Troubleshooting failed connections and restrictive networks
Find the failing stage first. Mándamele separates site access, signalling and WebRTC, and it does not turn a failure into a server upload.
Symptom → probable cause → action
Symptom
The site does not load on one device
Probable cause
Access, DNS, network filtering or service trouble; the flow has not reached the Pase yet.
Action
Open mandamele.com directly, check connectivity and try the same browser outside an embedded view.
Symptom
The code is invalid, missing or expired
Probable cause
A character is wrong, an old screenshot was used, or the ten-minute join window passed.
Action
Create a fresh Pase and enter all six characters. I, L, O, 0 and 1 are not in the alphabet.
Symptom
The second browser joins, but both remain on connecting
Probable cause
Signalling has started, but ICE cannot find a valid WebRTC route.
Action
Keep both tabs open. If policy allows, test a less restrictive trusted network or disconnect a VPN only as a controlled check.
Symptom
It works at home but not at work, in a hotel or over VPN
Probable cause
Firewall, NAT or policy blocks P2P connections. No TURN server is configured to relay them.
Action
Use the network or transfer tool approved by the organisation. This result alone does not prove browser incompatibility.
Symptom
The connection drops after locking the phone or switching apps
Probable cause
The operating system suspended or constrained the background tab.
Action
Keep the browser visible and device awake; make a new Pase if the previous session has ended.
Symptom
The file is rejected before it starts
Probable cause
It exceeds 50 MB, another send is active, or the DataChannel is not ready.
Action
Wait for the ready state, send one file at a time and stay within the limit.
Symptom
Progress starts but never finishes
Probable cause
An unstable channel, suspension, low memory or one endpoint closing.
Action
Keep the original, check storage and memory, try a small file first, then resend through a new Pase.
Symptom
The file appears in the conversation but not in Downloads
Probable cause
The browser created a local copy and preview, but it has not yet been saved to the system.
Action
Select download, choose a location if prompted, then open the saved file.
Useful details for a fault report
Hide the code and do not attach transferred content.
Environment
- Date and time zone.
- Browser, version and system at both endpoints.
- Network type and VPN use.
Exact stage
- Whether the site loaded and a code was created.
- Whether the second browser reached connected state.
- Whether short text worked and the test file’s size.
Controlled comparison
- Repeat once with a new code.
- When authorised, compare a home or test network to isolate the restriction.