mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4962] [bug]: Error running hoppscotch-desktop on Ubuntu 24.04 Cannot find unused port #1879
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1879
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kernusr on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4962
Originally assigned to: @CuriousCorrelation on GitHub.
Is there an existing issue for this?
Current behavior
When i run hoppscotch-desktop installing from *.deb package on Ubuntu 24.04 i have error
Steps to reproduce
Logs and Screenshots
Environment
Release
Hoppscotch Version
Local
Interceptor
Native - Desktop App
Browsers Affected
No response
Operating System
Linux
Additional Information
@kernusr commented on GitHub (Apr 7, 2025):
I am download and run AppImage package from https://hoppscotch.com/download and get the same error
@CuriousCorrelation commented on GitHub (Apr 7, 2025):
Hey @kernusr, thanks for reporting this issue with such details.
I wasn’t able to reproduce this in some of our testing environments so I did some digging, and I believe this might be related to the local environment preventing port binding rather than a general compatibility bug. The error happens when the app tries to find an available network port using
portpicker::pick_unused_port()right here. You can also see how the underlying library handles this here.It’s rather rare for this function to fail, the likely scenario being the port allocation algorithm simply failing to find available ports. It tries random ports in the 15000-25000 range first (which are likely to be free), then asks the OS for available ports as a reliable fallback, but in your environment, the error suggests that it can't find any ports that satisfy the requirements which in turn suggests there might be network configuration, security software, or system policies in your environment that are preventing the standard port allocation strategy from working properly.
@kernusr commented on GitHub (Apr 7, 2025):
It seems I found a solution!
For my VPN to work properly, I need to disable work with IP V6
Configuration via the graphical interface constantly stops working after rebooting the computer
On the Internet, I found a solution that to disable IP V6, you need to edit the parameters of the grub:
in
/etc/default/grubmake change fromto
After I deleted these parameters from the grub, the hoppscotch-desktop worked fine
@CuriousCorrelation thanks for the link to the code section that helped me figure out where to look
@wapmorgan commented on GitHub (Jun 3, 2025):
Don't forget to update grub after change to
/etc/default/grubviacommand
@wapmorgan commented on GitHub (Jun 18, 2025):
this does not work for me:
@wapmorgan commented on GitHub (Jun 18, 2025):
so, your propose is to delete arguments that disables ipv6?
https://github.com/Dentosal/portpicker-rs/blob/master/src/lib.rs#L23
In the library it looks like it checks ipv6 port too (used
&&and instead of||or)@kernusr commented on GitHub (Jun 24, 2025):
I encountered the fact that Outline VPN desctop client on my Ubuntu (https://github.com/Jigsaw-Code/outline-apps) does not pass traffic to resources accessible via IP6
The first thing that came to mind was to disable IP6
By google, I found a solution in the form of a recommendation to "change the grub config"
The problem with Outline VPN was solved and I forgot about this setting for some time
Then I got a problem with hoppscotch. After looking at the source code, I realized that the problem lies in checking IP6 and remembered my manipulations. Simply by deleting the key that I myself wrote there, I restored the functionality of hoppscotch
@kernusr commented on GitHub (Jun 24, 2025):
Pay attention to the output of
sudo netstat -tulnp | grep LISTENIt shows that no one is trying to listen to IP6. This should lead you to think that this is the problem. Something is preventing applications from listening to IP6. And for normal operation of hoppscotch, access to listening to IP6 is absolutely necessary
@wapmorgan commented on GitHub (Jun 27, 2025):
The question is "why is this required"? Hoppscotch won't work with ipv4-only?
@andersonpem commented on GitHub (Jun 30, 2025):
Kernel config:
BOOT_IMAGE=/boot/vmlinuz-6.14.11-zabbly+ root=UUID=40ed96e8-b73d-42fa-a533-695991e19b65 ro quiet splash ipv6.disable=1 loglevel=3 udev.log_level=3 vt.handoff=7Tried the deb:
`2025-06-30T10:38:48.682102Z DEBUG main ThreadId(01) tauri_plugin_appload: Initializing desktop-specific components.
2025-06-30T10:38:48.682113Z INFO main ThreadId(01) tauri_plugin_appload: appload plugin setup complete.
2025-06-30T10:38:48.682131Z INFO main ThreadId(01) tauri_plugin_relay: Setting up relay plugin
2025-06-30T10:38:48.682133Z DEBUG main ThreadId(01) tauri_plugin_relay: Initializing desktop-specific components
2025-06-30T10:38:48.682136Z DEBUG main ThreadId(01) tauri_plugin_relay::desktop: Initializing Relay for desktop platform
2025-06-30T10:38:48.682138Z DEBUG main ThreadId(01) tauri_plugin_relay: Desktop components initialized successfully
2025-06-30T10:38:48.682153Z INFO main ThreadId(01) tauri_plugin_relay: relay plugin setup complete
thread 'main' panicked at src/lib.rs:24:62:
Cannot find unused port
note: run with
RUST_BACKTRACE=1environment variable to display a backtraceandy@lrgi-pt-pf-4j9srf ~/Downloads> `
Tried the AppImage:
`2025-06-30T10:39:40.953330Z DEBUG ThreadId(19) tauri_plugin_appload::cache::store: File fits in memory; adding to hot cache. key="hoppscotch:assets/join-team-L3q4xvQk.js.map" size=9806
2025-06-30T10:39:40.953412Z INFO main ThreadId(01) tauri_plugin_appload::cache::manager: Bundle caching completed successfully name=hoppscotch
2025-06-30T10:39:40.953417Z INFO main ThreadId(01) tauri_plugin_appload::vendor::config: Vendored bundle initialized successfully name=hoppscotch
2025-06-30T10:39:40.956549Z DEBUG main ThreadId(01) tauri_plugin_appload: Initializing desktop-specific components.
2025-06-30T10:39:40.956560Z INFO main ThreadId(01) tauri_plugin_appload: appload plugin setup complete.
2025-06-30T10:39:40.956570Z INFO main ThreadId(01) tauri_plugin_relay: Setting up relay plugin
2025-06-30T10:39:40.956572Z DEBUG main ThreadId(01) tauri_plugin_relay: Initializing desktop-specific components
2025-06-30T10:39:40.956576Z DEBUG main ThreadId(01) tauri_plugin_relay::desktop: Initializing Relay for desktop platform
2025-06-30T10:39:40.956579Z DEBUG main ThreadId(01) tauri_plugin_relay: Desktop components initialized successfully
2025-06-30T10:39:40.956581Z INFO main ThreadId(01) tauri_plugin_relay: relay plugin setup complete
thread 'main' panicked at src/lib.rs:24:62:
Cannot find unused port
note: run with
RUST_BACKTRACE=1environment variable to display a backtrace`
Issue should be reopen.
@kernusr commented on GitHub (Jul 2, 2025):
As I understand it, the portpicker (
github.com/Dentosal/portpicker-rs@912f913ac3/src/lib.rs (L23)) is to blame for not checking "is it possible to use IP6" before starting this check. If IP6 is disabled in the system, the portpicker will fall into an error, and Hoppscotch will interpret it incorrectly.@jamesgeorge007 commented on GitHub (Aug 8, 2025):
Hi, this is addressed in the latest release. Please let us know if the issue persists.
@wapmorgan commented on GitHub (Aug 11, 2025):
firstly, thanks!
secondly, it looks like does not work as proposed.
@CuriousCorrelation commented on GitHub (Aug 11, 2025):
Hey @wapmorgan, thanks for testing v25.7.1!
Yes unfortunately it looks like the PR didn't solve this universally. This was an exploratory fix that worked on some systems but apparently not all. Although it does give us a lot more flexibility, so for an even more robust fix, I'll look into forcing IPv4-only binding, or perhaps falling back to letting the OS pick a port directly, or even better - completely sidestep the whole dual-stack issue. I am also looking into dropping the port requirement altogether and perhaps using deep-linking instead.
I am reopening this issue to track a follow-up solution.
@dmitryuk commented on GitHub (Aug 21, 2025):
Same issue, thanks
@wapmorgan commented on GitHub (Sep 29, 2025):
2025.9.0 still affecting:
@wapmorgan commented on GitHub (Nov 11, 2025):
Is it too complicated issue?
25.10.0 still affecting