Fix a problem
Start with what you see, then collect logs if you need help.
Start with what you see. Each problem below lists the checks in the order most likely to fix it. If none of them work, the last section shows how to collect logs so the problem can be found.
Can’t join
- Server offline on Android, or no connection on Windows: check the device’s internet connection. If you use your own server, the Switch and the viewer must both point at it.
- Wrong codes: open the Switch’s host screen and compare the Session ID and Password letter by letter. Codes change if someone chose Refresh ID and Password, and after 60 days.
- Hosting is off: the host screen must say Turn Off Hosting, which means hosting is on.
- Versions don’t match: the Switch and the viewer should come from the same package.
- Bridge Mode is full: when a Windows PC shares a USB-connected Switch, up to three people can join. Wait for someone to leave.
USB doesn’t connect
- Use a cable that carries data. Many cables only charge.
- Accept the USB driver offer the Windows app shows the first time, and approve the Windows prompt.
- If you disconnected the session yourself, click Connect By USB again, or unplug and replug the cable.
Connected, but no picture
- Note whether the screen is black, frozen, or still waiting for the first picture, and whether it happened when switching between HOME and a game. That helps when reporting it.
- On USB, check that USB streaming mode is Both or Video.
- On Windows, if the whole window is black or flickers, try Force software rendering and restart the app. If you turned on picture upscaling, set it back to Off.
- Some games block streaming unless the system patches are installed. The Switch app’s Settings → System patches shows whether they are.
Picture, but no sound
- Web player: sound starts off. Open ☰ Menu → Sound.
- Check the volume on the device and in the player.
- On USB, check that USB streaming mode is Both or Audio.
- Windows: if sound crackles, has gaps or is missing, set Audio player mode to Compatible and reconnect.
- Android: if sound crackles, raise Audio delay in Settings → Testing.
Buttons do nothing
- On the Switch, open Controllers → Change Grip/Order and press L and R together on the viewer, so the Switch notices the controller.
- Windows: check that the side panel says Controller: On. If a notice says the controller is moving the app, press the Guide button to send it back to the Switch.
- Web player: check that Controller is on in the menu, and press a button so the page finds your controller.
- Switch viewing a Switch: passthrough must be on. Hold L + R + ZL + ZR to switch it.
Stutters or falls behind
- Wi-Fi is the most common cause. Move closer to the router, or use a cable for the Switch or PC where you can.
- USB to a PC is usually the smoothest connection.
- Try one change at a time, so you can tell what helped.
- When reporting it, say what was on screen (a game, HOME or a menu) and how you were connected.
Browser says the page isn’t secure
The Windows app makes its own certificate for the web player, so browsers warn about it the first time. It’s safe to continue to your own link. To remove the warning for Public links, turn on Automatic public-IP HTTPS certificate in the Windows app’s Web Sharing settings and accept the agreement.
Public link doesn’t work outside home
- The router must let the web port (8443) and video port (8444, UDP) through to the PC. Request router ports for browser sharing asks it to. If your router ignores that, forward both ports yourself in its settings.
- Sharing settings apply on the next connection. Unplug the USB cable and plug it back in after changing them.
- Some internet providers share one public address between many homes. On those connections, outside links can’t reach your PC.
Collect logs and report a problem
Reproduce the problem once, note the time and your time zone, then export the logs as soon as you can. Say what you were doing when it happened. Avoid clearing app data or running several unrelated tests before exporting, so the files still cover the problem.
Collect logs from the Switch being played and the device you played on. Each export contains that device’s own logs, not the whole setup:
- Windows or Android app: the host Switch’s text file and the viewer’s ZIP.
- Switch-to-Switch: a text file from each console. Rename the copies to identify the host and the viewer.
- Browser play through a Windows PC: the host Switch’s text file, the Windows ZIP and the browser’s text file.
Switch
- After reproducing the problem, open NX Remote Play from the homebrew launcher. Close any other running homebrew app before opening hbmenu through Album.
- Open Settings → Actions → Export logs, then choose Create log file.
- Wait for Saved to the SD card root. The file is
/NX-Remote-Play-logs.txt. - Copy that file to the device you will use to submit the issue. You can use an FTP connection you already have set up, or fully shut down the Switch before removing the SD card and reading it on a computer. Do not remove the card while the Switch is running or asleep.
Each export replaces NX-Remote-Play-logs.txt. Keep a separate copy if you need logs from more than one test or console. Export from the host Switch even when the problem appears on the viewer.
Windows
- Reproduce the problem, then disconnect or stop the stream. Keep NX Remote Play open so you can export; traces still being written can be left out of the ZIP.
- Open Settings → Diagnostics & Logging → Export logs.
- Wait for the export notice. The Diagnostics folder opens automatically.
- Find
NX-Remote-Play-desktop-logs-YYYYMMDD-HHMMSS.zip, using the time in its name to choose the export for this report. The folder is%LOCALAPPDATA%\NX-Remote-Play\Diagnostics; you can paste that path into File Explorer’s address bar if it did not open.
Attach the ZIP, rather than only a screenshot of the export notice. It contains the support report, app logs and recent connection traces.
Android, Android TV and Google TV
- Reproduce the problem, then end the streaming session and return to the NX Remote Play start screen.
- Open Settings → About → Export logs.
- Wait for Logs saved to Downloads/NX-Remote-Play.
- Open your device’s file manager and go to Downloads → NX-Remote-Play. The manual export is named
NX-Remote-Play-logs-export-<timestamp>.zip. Choose the file created for this report. - On a TV, copy the ZIP using your usual file-transfer method to a phone or computer where you can attach it to GitHub.
The same folder can also contain automatic exports. Use the file from the problem session:
- Manual export:
NX-Remote-Play-logs-export-<timestamp>.zip. - After a streaming session:
NX-Remote-Play-logs-<session-timestamp>.zip. - After a failed join:
NX-Remote-Play-logs-join-failed-<timestamp>.zip.
The timestamp placeholders above are numbers in the actual filenames; they are not the Switch’s Session ID or Password. The Android ZIP does not include the Switch’s logs.
This beta’s built-in log export needs Android 10 or later. On Android 7–9, the app keeps private logs but cannot export them through this button. Report the Android version and the export message, and attach the host Switch’s logs and any Windows or browser logs involved. Do not clear app data to try to make the export work.
Web player, including iPhone and iPad
- Reproduce the problem and keep the player page open. Export before refreshing or closing the page: its log is kept only while that page is open.
- Open ☰ Menu → Export logs. If joining failed, use Export logs on the join screen instead.
- Save
NX-Remote-Play-web-log-YYYYMMDD-HHMMSS.txt(the filename uses UTC). Your browser either downloads it or opens a share sheet. On iPhone or iPad, choose Save to Files if offered, then choose a folder you can find again. - Collect the Windows app’s ZIP and the host Switch’s text file too. They help show what happened before the picture reached the browser.
Review the files before uploading
GitHub issues and their attachments are public. Open the exported text files and the files inside each ZIP before attaching them. Logs can include network addresses, device details or identifiers. Keep your originals privately; if anything needs removing, make a copy, remove those details and ZIP the reviewed files again.
Do not upload your whole SD card or configuration folders, passwords, Session ID, owner keys, or private browser-sharing links. Use the exported logs and describe any information you removed.
Attach the logs to a GitHub issue
- Sign in to GitHub and open NX Remote Play’s Issues page. Search for the same problem first. If an issue already covers it, add your details and logs in a comment there.
- Otherwise choose New issue and give it a short title describing the problem, such as “Android audio stops after returning from HOME”.
- Describe the steps to reproduce it, what you expected and what actually happened. Include the app version on each device, Switch model and firmware, viewer device and operating-system version, and whether you used USB, the local network, the internet or browser/Bridge Mode. Give the time of the problem and your time zone, and identify which log came from each device.
- Drag the reviewed ZIP or TXT files into the issue’s description, or use the attachment control below the text box to select them. On a phone, select the files from Downloads or Files.
- Wait for each upload to finish and for its attachment link to appear in the description. Then submit the issue. For an existing issue, wait for the links before posting your comment.
Do not paste a long log into the description instead of attaching the file. A screenshot or short recording can help show the problem, but include the logs as well when you can. If an export fails, report the exact message and attach the logs you could collect from the other devices.