From f96d5fff19885a122e882c0eccd23778503e42df Mon Sep 17 00:00:00 2001 From: Adam Shiervani Date: Mon, 24 Mar 2025 16:54:34 +0100 Subject: [PATCH 1/7] Revise troubleshooting documentation to focus on resolving "Loading Video Stream" issues and enhance WebRTC connection guidance. Update steps for firmware updates, browser settings, and troubleshooting mode for improved user support. --- .../docs/getting-started/troubleshooting.mdx | 78 ++++++++----------- 1 file changed, 33 insertions(+), 45 deletions(-) diff --git a/content/docs/getting-started/troubleshooting.mdx b/content/docs/getting-started/troubleshooting.mdx index 28af893..5c9a081 100644 --- a/content/docs/getting-started/troubleshooting.mdx +++ b/content/docs/getting-started/troubleshooting.mdx @@ -1,67 +1,55 @@ --- title: "Troubleshooting" -description: "Troubleshoot common JetKVM issues. Learn how to check connection status, verify USB connections, use the Troubleshooting Mode, and submit bug reports when needed for smooth remote computer management." +description: "Troubleshoot common JetKVM issues with a focus on resolving the Loading Video Stream problem and ensuring proper WebRTC connections." order: 1 --- -When issues arise with JetKVM, there are a few key steps you can take to identify and resolve the problem. Below, we'll guide you through the general approach to troubleshooting, highlighting the areas to check first and what each status or state means. +## Loading Video Stream Issue -## Check Connection Status +The most common issue with JetKVM is getting stuck at "Loading video stream..." when trying to connect to your device. This problem is typically caused by WebRTC connection issues between your browser and the JetKVM device. -The first step in troubleshooting is verifying the connection status between your device and the server. JetKVM provides a quick visual check in the **top-right corner of the dashboard**, where you'll see icons that represent the current connection status for both: +### 1. Update JetKVM Firmware -- **WebRTC Connection**: This represents the connection to the server. If this is disrupted, you'll see a message explaining the issue and suggested actions. -- **USB Connection**: This shows the status of the USB connection between your JetKVM device and the target host. +- Navigate to the IP address displayed on your JetKVM device +- Go to Settings → Check for Updates +- If an update is available, apply it and check if the issue is resolved -If both connections are **green** and stable but you're still encountering issues, proceed to the next steps. +### 2. Verify WebRTC Functionality -## Verify USB Connection +- Temporarily disable all browser extensions that might block or alter WebRTC connections +- If using a VPN or corporate network, try temporarily disconnecting as these can block WebRTC traffic -If the USB connection icon is **grayed out**, there's likely an issue with the USB cable connection. Common reasons include: +### 3. Browser-Specific Settings -- **USB not attached**: Check the physical connection and make sure the cable is properly inserted. -- **USB suspended**: This state usually indicates a low power mode or a suspension due to inactivity. +**For Microsoft Edge:** -For a more detailed state of the USB connection, move to the next step and enable Troubleshooting Mode. +- In your address bar, enter `edge://settings/content/mediaAutoplay` +- Ensure your JetKVM URL is in the Allow list, as Edge may block autoplay by default -## Enable Troubleshooting Mode (Debug Info) +**For Vivaldi:** -If the icons aren't giving enough context or you're still unable to identify the issue, the **Troubleshooting Mode** in the **Settings** provides deeper insight into what's happening. Here's how to access and use it: +- Navigate to `vivaldi://flags/#ignore-gpu-blocklist` +- Enable "Override software rendering list" (ignore the GPU blocklist) +- Go to Vivaldi Settings → Webpages and ensure "Use hardware acceleration when available" is enabled +- Make sure "Broadcast IP for best WebRTC Performance" is enabled +- Restart the browser after making these changes -- **Go to Settings** in the WebUI. -- Switch on **Troubleshooting Mode** at the bottom of the menu. +### 4. Check Browser Autoplay Settings -Once enabled, you'll see additional diagnostic details along the bottom of the interface, such as: +- As noted by some users, browsers may block video autoplay by default +- Ensure autoplay settings for video/audio are enabled for the JetKVM site -- **Resolution & Video Size**: +### Still Having Issues? - - _Resolution_: This shows the actual resolution being streamed from the KVM device. - - _Video Size_: This reflects the size of the video element on the browser window, adjusting dynamically based on browser dimensions. +If none of the above steps resolve your issue: -- **Mouse Pointer Position**: This shows the X and Y coordinates of the mouse pointer in real-time, which helps debug input issues. +1. Visit our [GitHub issue #84](https://github.com/jetkvm/kvm/issues/84) where we're actively monitoring this problem -- **USB State**: You'll see the raw state of the USB connection: +2. When reporting your issue, please include: + - The data shown at the bottom of the video feed when Troubleshooting Mode is enabled (Settings > Advanced > Enable Troubleshooting Mode) + - Your network configuration (router type, network setup) + - The devices/computers you've tried connecting to + - Any browsers you've tested with and their results + - The JetKVM app version and system version - - **Configured**: The USB connection is functioning as expected. - - **Attached**: The device is physically connected but may still be initializing. - - **Not Attached**: The USB device is not detected. - - **Suspended**: The connection is idle or in a low-power state. - - **Addressed**: The USB device is recognized and assigned an address but not yet fully functional. - -- **HDMI State**: This shows the status of the HDMI signal from the target host: - - **Ready**: Everything is functioning properly. - - **No Signal**: The target device isn't sending a video signal. Check cables or ensure the device is powered on. - - **No Lock/Out of Range**: The signal is either unsupported or outside the allowed range (e.g., resolution or refresh rate too high). - - **Connecting**: The HDMI connection is initializing and should be ready soon. - -## When All Else Fails - -If none of the above steps resolve your issue and everything seems to be connected, but JetKVM is still not functioning, we recommend submitting a bug report. Here's how to do that: - -1. **Go to GitHub** and navigate to our issues page. (To be added at launch, when source code is available.) -2. **Fill out the bug report template**. Include important information such as: - - The **JetKVM app version**. - - The **system version** of your KVM device. - - A brief description of the problem and context (e.g., when it happens, how often, any notable actions that caused the issue). - -This will help us quickly identify and resolve the problem for you. +Our team is actively working to resolve these connection issues with each firmware update. From a5aea50b8d552b6410dd7ac7d5e5f312dc9179e3 Mon Sep 17 00:00:00 2001 From: Adam Shiervani Date: Tue, 25 Mar 2025 11:49:03 +0100 Subject: [PATCH 2/7] Add Firefox-specific troubleshooting steps for WebRTC issues in documentation --- content/docs/getting-started/troubleshooting.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/docs/getting-started/troubleshooting.mdx b/content/docs/getting-started/troubleshooting.mdx index 5c9a081..0129b98 100644 --- a/content/docs/getting-started/troubleshooting.mdx +++ b/content/docs/getting-started/troubleshooting.mdx @@ -34,6 +34,13 @@ The most common issue with JetKVM is getting stuck at "Loading video stream..." - Make sure "Broadcast IP for best WebRTC Performance" is enabled - Restart the browser after making these changes +**For Firefox:** + +- Navigate to `about:config` +- Search for `media.peerconnection.enabled` +- Set it to `true` +- Restart the browser after making these changes + ### 4. Check Browser Autoplay Settings - As noted by some users, browsers may block video autoplay by default From 4dc9bb41b9475521fe18446186e6550bbffb2d80 Mon Sep 17 00:00:00 2001 From: Adam Shiervani Date: Tue, 25 Mar 2025 19:25:49 +0100 Subject: [PATCH 3/7] Add Chromium-specific troubleshooting steps for WebRTC issues in documentation --- content/docs/getting-started/troubleshooting.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/docs/getting-started/troubleshooting.mdx b/content/docs/getting-started/troubleshooting.mdx index 0129b98..3a80490 100644 --- a/content/docs/getting-started/troubleshooting.mdx +++ b/content/docs/getting-started/troubleshooting.mdx @@ -21,6 +21,12 @@ The most common issue with JetKVM is getting stuck at "Loading video stream..." ### 3. Browser-Specific Settings +**For Chromium:** +- Navigate to `chrome://flags/#webrtc-ip-handling-policy` in your address bar +- Look for "WebRTC IP Policy" +- If it's set to "Disable non proxied UDP", change it to "Default" +- Restart your browser for the changes to take effect + **For Microsoft Edge:** - In your address bar, enter `edge://settings/content/mediaAutoplay` From 0aac2a1189adec8aa272499c232c2d3701470555 Mon Sep 17 00:00:00 2001 From: Adam Shiervani Date: Wed, 26 Mar 2025 18:37:30 +0100 Subject: [PATCH 4/7] Update shipping batch ranges in Kickstarter FAQ for March and April --- content/docs/getting-started/ks-faq.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/docs/getting-started/ks-faq.mdx b/content/docs/getting-started/ks-faq.mdx index 09d66c3..23839d1 100644 --- a/content/docs/getting-started/ks-faq.mdx +++ b/content/docs/getting-started/ks-faq.mdx @@ -35,7 +35,8 @@ The batch you're in depends on the backer number. - **December**: Less than 12208 - **January**: 12208 - 15303 - **February**: 15304 - 19415 -- **March**: Larger than 19415 +- **March**: 19416 - 30447 +- **April**: Larger than 30447 ### How do I know when my package will be dispatched? From 863205589a2716c5e9b4f0dc1cf00db20dd7467c Mon Sep 17 00:00:00 2001 From: Adam Shiervani Date: Wed, 26 Mar 2025 18:40:57 +0100 Subject: [PATCH 5/7] Update shipping batch details in Kickstarter FAQ, clarifying status for December, January, March, and April batches, and emphasize the use of the Pledge Tracker for updates. --- content/docs/getting-started/ks-faq.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/getting-started/ks-faq.mdx b/content/docs/getting-started/ks-faq.mdx index 23839d1..c7ba53e 100644 --- a/content/docs/getting-started/ks-faq.mdx +++ b/content/docs/getting-started/ks-faq.mdx @@ -12,13 +12,13 @@ For more context: As the delivery of your JetKVM pledge depends on so many factors, **mostly out of our control**, we can only provide you with a rough estimate of the dispatch of your device. -**December Batch:** Less than 0.47% of this batch is still pending. These are mostly orders requiring manual handling due to unusual delivery requirements. If you haven't received a shipping email, please [contact us](mailto:shipping@jetkvm.com). +**December, January, February:** Less than 0.25% of this batch is still pending. These are mostly orders requiring manual handling due to unusual delivery requirements. If you haven't received a shipping email, please [contact us](mailto:shipping@jetkvm.com). -**January Batch:** Fewer than 0.58% of these pledges are left. Like the December batch, these are mainly orders with special manual handling needs or unique shipping destinations. If you haven't received a shipping email, please [contact us](mailto:shipping@jetkvm.com). +**March Batch:** We began processing the March batch on March 18th. About 10% of this group has already been dispatched, and more are going out each day. Things are moving consistently now. -**February Batch:** We are actively shipping these orders right now. If you haven’t received a shipping confirmation yet, hang tight - it’s on the way. **Please don't reach out to us with simple shipping status inquiries.** +**April Batch:** We expect the April batch to start shipping in April. No delays expected. -**March Batch:** We expect this batch to be dispatched in March, with no delays. **Please don't reach out to us with simple shipping status inquiries.** +**If you're in the March or April batch, please don’t email us just to ask for a status update.** You can check your reward’s progress any time via the [Pledge Tracker](https://shiphelp.jetkvm.com). Just enter your email, and you’ll see where your reward is in the shipping pipeline. **Important Reminders:** From 7b77a8a143c9cdcba4b0da8cf0e4fa5fea0cd746 Mon Sep 17 00:00:00 2001 From: Adam Shiervani Date: Wed, 26 Mar 2025 21:55:01 +0100 Subject: [PATCH 6/7] Clarify batch assignment criteria in Kickstarter FAQ, specifying that it is based on backer number rather than the backing date. --- content/docs/getting-started/ks-faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/getting-started/ks-faq.mdx b/content/docs/getting-started/ks-faq.mdx index c7ba53e..03b8c5c 100644 --- a/content/docs/getting-started/ks-faq.mdx +++ b/content/docs/getting-started/ks-faq.mdx @@ -30,7 +30,7 @@ As the delivery of your JetKVM pledge depends on so many factors, **mostly out o ### Which batch am I in? -The batch you're in depends on the backer number. +The batch you're in depends on the backer number, and not when you backed the project. - **December**: Less than 12208 - **January**: 12208 - 15303 From 2ebcbdd111c9cab27486a4a9daacc5b842c471a7 Mon Sep 17 00:00:00 2001 From: Adam Shiervani Date: Thu, 27 Mar 2025 00:57:09 +0100 Subject: [PATCH 7/7] Enhance Kickstarter FAQ by adding a note on batch identification and updating shipping status for December, January, and March batches. Include reminders about shipment processes and clarify that extensions may ship separately. --- content/docs/getting-started/ks-faq.mdx | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/content/docs/getting-started/ks-faq.mdx b/content/docs/getting-started/ks-faq.mdx index 03b8c5c..933a925 100644 --- a/content/docs/getting-started/ks-faq.mdx +++ b/content/docs/getting-started/ks-faq.mdx @@ -12,7 +12,14 @@ For more context: As the delivery of your JetKVM pledge depends on so many factors, **mostly out of our control**, we can only provide you with a rough estimate of the dispatch of your device. -**December, January, February:** Less than 0.25% of this batch is still pending. These are mostly orders requiring manual handling due to unusual delivery requirements. If you haven't received a shipping email, please [contact us](mailto:shipping@jetkvm.com). +
+ +Before proceding, make sure you know [which batch you are +in](/docs/getting-started/ks-faq#which-batch-am-i-in)! + +
+ +**December, January, February Batch:** Less than 0.25% of these batches are still pending. These are mostly orders requiring manual handling due to unusual delivery requirements. If you haven't received a shipping email, please [contact us](mailto:shipping@jetkvm.com). **March Batch:** We began processing the March batch on March 18th. About 10% of this group has already been dispatched, and more are going out each day. Things are moving consistently now. @@ -22,15 +29,12 @@ As the delivery of your JetKVM pledge depends on so many factors, **mostly out o **Important Reminders:** -- If you haven't received an email yet, it just means your reward hasn't been packaged & processed yet. Hang tight, we'll get to you as soon as possible! - -- We don’t ship all rewards at once. Instead, **shipments go out continuously starting in the target month**. If your order is in a pending batch, rest assured we’ll get to you soon! - -- If you ordered any extensions, **we will very likely ship them separately from your main JetKVM device**. You'll receive another notification when your extensions are ready to ship. +- Shipments go out **continuously starting in the target month**, not all at once. +- Extensions will **likely ship separately** from your main device. ### Which batch am I in? -The batch you're in depends on the backer number, and not when you backed the project. +The batch you're in depends on the backer number, **and not when you backed the project.** - **December**: Less than 12208 - **January**: 12208 - 15303