starred/kvm

Fork 0

mirror of https://github.com/jetkvm/kvm.git synced 2026-03-02 22:58:00 -05:00

app.jetkvm.com not working with Windows or Mac Firefox #243

New issue

Closed

opened 2026-02-20 08:21:26 -05:00 by deekerman · 9 comments

deekerman commented

2026-02-20 08:21:26 -05:00

Owner

Originally created by @gitguys on GitHub (May 4, 2025).

in Firefox the app.jetkvm.com page shows the KVM online but when I click on 'Connect to KVM' it lingers at "Establishing a Secure Connection' then results with 'Connection Issue Detected'.

Firefox works locally with the IP address, but not with app.jetkvm.com. Chrome browser on the same machines work with app.jetkvm.com just fine, so it's only Firefox (Win or Mac) and app.jetkvm.com.

I tested this with latest App: 0.3.9 System: 0.2.4 as well as 0.2.3

Originally created by @gitguys on GitHub (May 4, 2025). in Firefox the app.jetkvm.com page shows the KVM online but when I click on 'Connect to KVM' it lingers at "Establishing a Secure Connection' then results with 'Connection Issue Detected'. Firefox works locally with the IP address, but not with app.jetkvm.com. Chrome browser on the same machines work with app.jetkvm.com just fine, so it's only Firefox (Win or Mac) and app.jetkvm.com. I tested this with latest App: 0.3.9 System: 0.2.4 as well as 0.2.3

deekerman closed this issue

2026-02-20 08:21:27 -05:00

deekerman commented

2026-02-20 08:21:27 -05:00

Author

Owner

@InariTheFox commented on GitHub (May 4, 2025):

As a user of Firefox, I can confirm that it does work perfectly fine on Windows, Mac and Linux with the latest version (138.0). I would recommend that you check for running plugins and other configuration changes which could be interfering.

@InariTheFox commented on GitHub (May 4, 2025): As a user of Firefox, I can confirm that it does work perfectly fine on Windows, Mac and Linux with the latest version (138.0). I would recommend that you check for running plugins and other configuration changes which could be interfering.

deekerman commented

2026-02-20 08:21:27 -05:00

Author

Owner

@gitguys commented on GitHub (May 5, 2025):

@InariTheFox

I've narrowed it down to some incompatibility with app.jetkvm.com, Firefox and using a Virtual Private Network. I've test with both the PIA VPN app and Tunnelblick VPN client that connects to PIA VPN servers. Firefox has no other issues with any other sites using the VPN, only app.jetkvm.com is the problem. I've tried different VPN servers and it has the same effect.

Chrome works while on the same VPN with app.jetkvm.com so if it was a VPN IP blocking problem I wouldn't expect Chrome to be able to connect through the same VPN IP address.

tl;dr — As long as the VPN is disconnected Firefox work with app.jetkvm.com. Chrome works either way. Finding this the same on both Windows and Mac computers running latest Firefox.

@gitguys commented on GitHub (May 5, 2025): @InariTheFox I've narrowed it down to some incompatibility with app.jetkvm.com, Firefox and using a Virtual Private Network. I've test with both the PIA VPN app and Tunnelblick VPN client that connects to PIA VPN servers. Firefox has no other issues with any other sites using the VPN, only app.jetkvm.com is the problem. I've tried different VPN servers and it has the same effect. Chrome works while on the same VPN with app.jetkvm.com so if it was a VPN IP blocking problem I wouldn't expect Chrome to be able to connect through the same VPN IP address. **tl;dr** — As long as the VPN is disconnected Firefox work with app.jetkvm.com. Chrome works either way. Finding this the same on both Windows and Mac computers running latest Firefox.

deekerman commented

2026-02-20 08:21:27 -05:00

Author

Owner

@InariTheFox commented on GitHub (May 5, 2025):

I have been able to confirm that using the combination of ExpressVPN & Firefox does duplicate the issue as reported. Using inspection via developer tools there are no issues with HTTP traffic, so this comes down to WebRTC and Firefox while on a VPN.

Upon inspection using debugging tools within Firefox, the following logs were captured:
https://gist.github.com/InariTheFox/6f0c90843528fc6e1a0ccb05b0fc20ea

The IP address which has been blanked out is my network's public IP. Firefox, when negotiating with the STUN server is using invalid route information, leaking with your network's IP address and not the VPN's. It appears that WebRTC is leaky on a variety of browsers, including Mozilla and Chromium based ones, which would result in this issue happening.

Because of the leaked IP addresses being used versus the VPN's, Firefox is not able to negotiate with the STUN server, causing the failure. This is most likely out of the hands of JetKVM, and actually falls on Mozilla's lap.

@InariTheFox commented on GitHub (May 5, 2025): I have been able to confirm that using the combination of ExpressVPN & Firefox does duplicate the issue as reported. Using inspection via developer tools there are no issues with HTTP traffic, so this comes down to WebRTC and Firefox while on a VPN. Upon inspection using debugging tools within Firefox, the following logs were captured: https://gist.github.com/InariTheFox/6f0c90843528fc6e1a0ccb05b0fc20ea The IP address which has been blanked out is my network's public IP. Firefox, when negotiating with the STUN server is using invalid route information, leaking with your network's IP address and not the VPN's. It appears that WebRTC is leaky on a variety of browsers, including Mozilla and Chromium based ones, which would result in this issue happening. Because of the leaked IP addresses being used versus the VPN's, Firefox is not able to negotiate with the STUN server, causing the failure. This is most likely out of the hands of JetKVM, and actually falls on Mozilla's lap.

deekerman commented

2026-02-20 08:21:27 -05:00

Author

Owner

@gitguys commented on GitHub (May 6, 2025):

@InariTheFox Thank you for the insights. Would it be possible to contact Mozilla about this bug?

@gitguys commented on GitHub (May 6, 2025): @InariTheFox Thank you for the insights. Would it be possible to contact Mozilla about this bug?

deekerman commented

2026-02-20 08:21:27 -05:00

Author

Owner

@docfaraday commented on GitHub (May 15, 2025):

Just to make sure I'm understanding, what IP address is the "leaked" one here? The one that is blanked out, or 100.64.100.6?

@docfaraday commented on GitHub (May 15, 2025): Just to make sure I'm understanding, what IP address is the "leaked" one here? The one that is blanked out, or 100.64.100.6?

deekerman commented

2026-02-20 08:21:27 -05:00

Author

Owner

@InariTheFox commented on GitHub (May 15, 2025):

The blanked out one is the "leaked" public IP address of the non-VPN connection to the internet.

@InariTheFox commented on GitHub (May 15, 2025): The blanked out one is the "leaked" public IP address of the non-VPN connection to the internet.

deekerman commented

2026-02-20 08:21:28 -05:00

Author

Owner

@docfaraday commented on GitHub (May 19, 2025):

That blanked out address is not coming from Firefox. That's all remote candidate stuff from the other end. Are you trying to connect to a device on your local network? The other device is likely telling jetkvm about this address, which is then being handed off to Firefox.

@docfaraday commented on GitHub (May 19, 2025): That blanked out address is not coming from Firefox. That's all remote candidate stuff from the other end. Are you trying to connect to a device on your local network? The other device is likely telling jetkvm about this address, which is then being handed off to Firefox.

deekerman commented

2026-02-20 08:21:28 -05:00

Author

Owner

@docfaraday commented on GitHub (May 30, 2025):

Have you had a chance to double-check your scenario? While I think I know what is happening, I don't want to miss something important here.

@docfaraday commented on GitHub (May 30, 2025): Have you had a chance to double-check your scenario? While I _think_ I know what is happening, I don't want to miss something important here.

deekerman commented

2026-02-20 08:21:28 -05:00

Author

Owner

@paulverbeke commented on GitHub (Sep 16, 2025):

hi,

I have the same problem:

Proton VPN enabled
connection to my JetKVM using IP on local network is OK on all browsers (Firefox, Edge & Chrome)
connection to my JetKVM using KVM cloud is OK on both Edge & Chrome but KO on Firefox being stuck at "Establishing secure connection ..."
I now close Proton VPN
now all connections works everywhere including Firefox

Where should I go to find a fix for this ?
I didn't find a solution in #84 because this doesn't look like the same underlying issue

Thanks in advance

@paulverbeke commented on GitHub (Sep 16, 2025): hi, I have the same problem: - Proton VPN enabled - connection to my JetKVM using IP on local network is OK on all browsers (Firefox, Edge & Chrome) - connection to my JetKVM using KVM cloud is OK on both Edge & Chrome but KO on Firefox being stuck at "Establishing secure connection ..." - I now close Proton VPN - now all connections works everywhere including Firefox Where should I go to find a fix for this ? I didn't find a solution in #84 because this doesn't look like the same underlying issue Thanks in advance