Jellycuts Bridge is not working

[gulias]

Describe the bug

I can't get a connection to the VSCode extension using the bridge feature. The app is stuck on the "connecting..." state.

I confirm that the server side on the VSCode is running as I executed the command "Open Jellycuts Bridge". I also confirm that my phone is able to reach the computer, as when I introduce the server address and port (http://computerip:8080/) on safari I get a response from the server with the HTTP Status 426 and the text "Upgrade required".

To Reproduce

Steps to reproduce the behavior:

1. Run the "Open Jellycuts Bridge" command on VSCode
2. Go to Jellycuts app and open the "Jellycuts Bridge" Tool
3. Create a new connection with using the computer ip as "Server Address" (ex: 192.168.1.24)
4. Try to connect to the fresh created connection.

Expected behavior

Connection successful between VSCode extension and Jellycuts app

Information

• Device: iPhone 13
• OS: iOS 17.5.1
• Jellycuts Version 2.2(2)
• Jailbroken? No

Additional context

I search the web for any kind of documentation or guide to get this to work, but found nothing.
I'm using the plain IP address of my computer as "Server Address". Also tried to add the socket (x.x.x.x:8080), but got "invalid url" message.

[gulias]

This is quite disappointing. The only reason I paid the "plus" subscription was the possibility to edit the shortcuts directly from VSCode.
Two weeks since I reported the issue and I got no feedback or guidance (in case I'm doing something wrong).

Also, no official documentation on how make it to work in the first place...

[mooreorless555]

@gulias Agreed, I'm in your same boat.

[chrysaora-achlyos]

I share your disappointment.

This is a workaround, not a solution. If you are comfortable with changing the networking on the machine running vscode, there are workarounds on both windows and mac.https://discord.com/channels/503976650439131183/1249101795045671094 contains the link to reddit posts. Fun-Obligation-5777 low reddit karma, so the post do not show up unless I'm guessing you are logged into reddit.

The gist is you need to proxy port 80 on the machine running vscode to port 8080. This allows you to enter just the IP address of your machine running vscode without ":8080" thus avoiding the "invalid url error"

windows

I was able to connect via the bridge with a work around.
VScode was running on a windows machine 192.168.0.116. first I used
.
netsh interface portproxy add v4tov4 listenport=80 listenaddress=192.168.0.116 connectport=8080 connectaddress=192.168.0.116
.
to forward port 80 to 8080.
Then I created a firewall rule to allow in connections from my phone IPAddr on port 80.
In the Enter VSCode Extension details I entered a Name, and 192.168.0.116 without any port numbering
I went this route because when I used "192.168.0.116:8080" I got a "Please enter a valid URL and name" error dialog box.


mac

I posted separate response on using port forwarding workaround on Window.
Today I goto a macos solution working based on
https://gist.github.com/novemberborn/aea3ea5bac3652a1df6b
need to be able to sudo on the mac to edit /etc/pf* files
I replaced 'dev' in github gist with 'jelly'
Note order is important, so rearrange at own risk
.
$CMD tail /etc/pf.conf
scrub-anchor "com.apple/"
nat-anchor "com.apple/"
rdr-anchor "com.apple/"
rdr-anchor "jelly"
dummynet-anchor "com.apple/"
anchor "com.apple/*"
load anchor "com.apple" from "/etc/pf.anchors/com.apple"
load anchor "jelly" from "/etc/pf.anchors/jelly"
.
// 192.168.0.139 is my iPhone ipaddr, can use "any" like in gist if like the element of danger
.
$CMD cat /etc/pf.anchors/jelly
rdr pass inet proto tcp from 192.168.0.139 to any port 80 -> 127.0.0.1 port 8080
.
$CMD sudo pfctl -F all -ef /etc/pf.conf
.
// in Jellycuts "Enter VSCode Extension details", I used raw ipaddr of mymac, no ":8080" postfix
// 192.168.0.218 is my mac ipaddr
name: mymac
Server Address:192.168.0.218

[Ambushfall]

I don't think the developer gives any @#$ about the donation, or support x'D

On a reddit post he pointed people towards his "Free" newsletter, which lands you to a subscription sign up.

I mean, I respect the effort he has gone through to provide value, however, almost all of the pro features don't work.

If there were no features, I'd consider supporting directly instead, however with the way there's no support, naa