#Cannot start instproxy server on this device
1 messages · Page 1 of 1 (latest)
We want to help you to the best of our ability, but first we have to ask and make sure you have taken the proper steps to installing SideStore before we can help.
Without WiFi AND the WireGuard VPN, SideStore cannot function correctly. Try toggling the VPN a few times.
If you have AltStore installed as well as SideStore, you will only be able to install 1 or NO apps in SideStore!
If you are using the official SideStore server you can check https://ani.sidestore.io/ in Safari for a text output.If there is no output, ping a Project Developer immediately!
Please provide as much information about the error you are experiencing. You can send the minimuxer.log file from inside Files > SideStore as well as in-app screenshots, and that would help us diagnose your issues much faster!
Patience! Please have patience with our Helpers and Developer staff, we are all open source maintainers who do all of this for free on our own time. Thank you!
I have the exact same issue on the same phone. My best solution currently is the just sideload ipa's from sideserver or sideloadly until it's fixed
When you say reset pairing file, what do you mean by that? Did you plug your phone into your computer and regenerate your pairing file?
@native aspen You as well, did you regenerate your pairing file? I personally don’t have a 15 Pro, so i’m hoping this issue can be fixed
It might be that iOS 17.0 -> 17.0.2 on the 15 might need a new pairing file, try rerunning jitterbugpair on your computer with your device plugged in
yes i've regenerated pairing several times and i've done a clean insall a couple of times
no sorry i have uninstalled but i can install again and try installing an app if that would help
That’s alright, logs would be appreciated! Having logs would definitely help us pinpoint the error. Also make sure to have the WireGuard VPN on, maybe give it a toggle before opening SideStore as well
And WireGuard is on? 😨
yes
@storm saffron This looks pretty bad, heartbeat can’t start on iOS 17.0.2
Instproxy happens on lower iOS versions also.
Just not as prominent
I’ve never seen a heartbeat fail log so consistent, and they say the VPN is on
Just to double check, WireGuard and WiFi?
yes
I’m afraid of new iOS versions somehow patching us, this might be it. We’ll see what nature has to say.
redhead do you have a Mac? Can you get device logs?
No
Rip, okay. If we’re broken, libimobiledevice might be broken, but idk. Your device shows up on your computer?
didn’t apple like fixed a bug or an exploit in 17.0.1+?
Yeah, but they said it was CoreTrust-like, not VPN related
oh ok
Yeah it’s inconsistent on older iOS. Nature has said in past it’s a miracle that minimuxer can even start heartbeat on iOS
I’m tempted to update for the team, but I was hoping I could stay on 17.0 for CoreTrust boogaloo on my 14 Pro
As minimuxer implimentation is kinda bad for heartbeat
@native aspen with that i’d say give it a few goes I guess, and maybe try another WiFi if you can.
Ok
My only other question: Did you use the right pairing file? hehe
Wrong pairing file would explain the consistency of failure
does this error mean that the device cannot interact with the server
It means the device cannot interact with itself
ok
heartbeat is us talking to the device
Or well, device supposed to be talking to us
could be that the ops internet company blocked the server or smth
There is no server
Your device is talking to itself here
ohhh
SideStore is forcing iOS to talk to itself, or simply SideStore is talking to iOS, and iOS isn’t listening
probably would be better to downgrade to ios 17
We’ve gotta investigate changes anyway, plus Riley’ll be panicking too i’m sure
We’ll see
i mean most people are having issues in ios 17
I’m thinking a lot are pairing file errors
Though it could be something else
We wanna investigate
Sorry for the late response but I’m not sure the only thing I did is side load the same as on my old phone. I use Linux but i just run a windows 10 vm and have never had issues with my old phone
Doubtful, my 14 Pro is also exhibiting this behaviour on 17.0.1 (which is fundamentally the same code but for non-15 devices)
Logs? This is big. First report I’ve seen of another device
Give me instructions and I'll help ya
Files > SideStore > minimuxer.log
Share to Discord, this channel should appear
I've tried pairing reset
@storm saffron @bronze mauve
Did you regenerate your pairing file with jitterbugpair? You’re on WiFi?
Never used jitterbugpair
Should I do a reinstall from sideserver is that what you're saying?
Since almost everything is tied to heartbeat it all fails
macOS or Windows? If you’re on Windows:
- Download AltServer
https://altstore.io - Download jitterbugpair
https://github.com/osy/Jitterbug/releases - Open AltServer while holding shift on Windows or Alt on Mac, it should show “sideload ipa” select your device and choose SideStore’s ipa file
- Open jitterbugpair, it should create a pairing file next to itself, send that profile to your device (Don’t use Discord or Google Drive, they mess up the file extension, so zip it first if you do use these but DO NOT SEND THEM ANYWHERE PUBLIC)
- Open SideStore, it’ll ask for that pairing file you sent, if you zipped it, make sure to unzip it in iOS
Macos
Try AltServer then with jitterbugpair, same instructions above
So I shouldn't try to reinstall through sideserver?
Just for now
I've never had to use jitterbugpair before
To rule out everything
And sideserver can't do it? Must be AltServer?
I wanna see if jitterbugpair fails, if not i’ll have questions maybe. AltServer doesn’t do the pairing file automatically, so it helps us debug further
If pairing is different I wouldn’t be surprised
But it’s likely fine
Never know tho
Sure
For sure, I just wanna see if there is damage, and how far it goes
Install JitterbugLite.ipa using shift+install ipa, then run jitterbugpair on my mac?
Nahh jitterbugpair for macOS
No the jitterbugpair.dmg then install to Mac
That’s all you need
We just use jitterbugpair because it’s easier, we should probably fix SideServer to do it for us..
Dmg?
Though I wanna make sure SideServer has a manual pairing mode for debugging
It's an executable no?
It might just be an exe
Lmao, exe
jitterbugpair-macos or something
I'm a software engineer
I’m TS, you?
I can run binaries on macos
Just need to know what you want me to run
jitterbugpair for sure with your iPhone plugged in
You might also want Console later
Yeah, sorry hehe
how do i get sidestore to ask for the pairing file?
Install it with AltServer
Yeah, hehe
SideServer mangling the app id incorrectly?
but i'll do it, just for you guys
no i mean, installing ipa from altserver will install the widget as well and consume an extra app id
Ohh. You could extract the ipa and delete AltWidget
The drama of it all lol
You know what I know, it’s not entirely wrong
No, try the normal one from Github or the one in #announcements
MDC is only for MDC devices, 17.0.1 is not that
took from announcements, already installed, you're too slow
I’m working from my phone, i’m going as fast as I can 
||sonic||
fuck, forgot to start wireguard profile
If it’s only user error i’ll point and laugh at you, but only for a little bit
Try installing another app
Oh nice! 17.0.1 is safe
something did happen though
Show?
I wonder what would happen if you update to 17.0.2 💀
17.0.2 doesn't exist for 14 pro
It would’ve been the pairing file when it was failing
but i've not had issues signing stuff previously, only after 17.0.1 update
17.0->17.0.1 might’ve needed a new pairing file
yeah 17.0.1 security content is the same as 17.0.2
@stable meteor that's what im thinking
My new guess is security updates invalidate all pairing files
so thanks for walking me through it, never done it before
(i can extrapolate the bits i don't need to do next time)
That’d explain why sometimes you can use the same pairing file for multiple updates, but security updates would force reset them
but it appears sidestore couldn't create its own
so the reset pairing file button didn't do anything
or i mean it did something, it just didn't work
Yeah, it’s because of the way SideServer embeds the pairing file into the app, essentially making the reset pairing file useless on SideServer installs for right now. We have a lot of bugs we need to fix 
why can't it just be march 6th 2024 already
i'm worried they're gonna still require app review and official signatures, just "ok, good, now feel free to distribute this however you like"
but definitely crossing my fingers for a different implementation
aha, so this install i have now is without integrated pairing file, so it'll work like I expect and let me do it myself?
Yep!
or will that be gone once i've resigned it from sidestore once?
that includes sidestore ipa updates installed without sideserver?
but not if the initial install is from altserver?
SideServer embeds it into the Info.plist, meaning SideStore will always have it even after refreshing unless we add code to remove it from the Info.plist. SideStore from AltServer doesn’t have it embedded and stores it in Files > SideStore where you could delete it too.
If you use Xcode, I assumed that’d make sense, hehe
absolutely not
Game dev?
Oh I didn’t know that
Well if you ever wanna learn iOS development, could always look at SideStore, hehe.
well the frontend is usually react i guess, but i build my backends in c# on dotnet 7
haha
i have wanted to, infact i have tried actually
just not for long enough to actually get it
might try my hand at it again some time
built a little demo for a customer to streamline a process for them
Yeah, it’s a rough entry, but if you need help us devs can help get you started in #off-topic ! I’m planning on doing a rewrite anyway soon, hopefully.. Whenever motivation turns up
but they didn't want to pay for the development of the actual app in the end
so, no paid ios dev learning experience for me haha
Check DM
these instructions actually fixed it. ios 17.0.2
Whewww thank goodness
This worked for me as well. iPhone 15 pro on iOS 17.
This is just bad pairing file, it happened to me
We should be tracking the iOS version last used with SideStore and then reset the pairing file if it changes
And also, we need to get rid of ALTPairingFile in info.plist
Just dropping in to confirm this also fixed it for me! Thanks! Do you maybe want to post those instructions on this issue: https://github.com/SideStore/SideStore/issues/482 ?
so use jitterbugrepair so that instproxy server works?
Agreed and just import pairing file to the actual file that’s accessible when pairing manually
not sure if i understand how to load the profile into sidestore
ziped it and sent it over through my gmail
downloaded and unzip in files app
opened side store clicked the plus button on my apps page. Dosent let me select the profile
im on 17.02 side store 0.5.1
@minor berry
'Reset pairing file' in settings
if that doesn't work rename it to ALTPairingFile.mobiledevicepairing and put it in the SideStore directory in Files
@long cove
@minor berry I had tried that initially but didn’t work Someone in general suggested adding the file directly to SideStore directory which did the trick
Thanks!
You know, it would be really nice if this team had any bit of transparency in it. Now because i had 0 idea this would be an issue, i ended up resetting and restoring to 17.0.2 from 17.1B1 this morning and now on top of how useless sidestore was before, it's now rendered truly useless. Known issue, absolutely no announcement or warning.
And no, the workarounds listed here didn't work one bit.
Transparency has little to do with this. I'd argue we are pretty transparent though, especially when compared to apps like AltStore
I also don't see what you downgrading has to do with anything
Every issue is out in the open in the support thread and GitHub issues which are publicly accessible. We update people when we do changes or need testing. We warn when we can also. We talk to our users all the time what we are doing. We’re very transparent even to little ideas we get. Meanwhile you can’t even talk to developers on altstore.
Part of problem is also users not reading the issue they have so they make essentially spam messages and have to mention it’s a duplicate issue which is very time consuming. We work on our free time in this project as we don’t use sidestore as a full time job like Riley in altstore team. Community maintained which also means people outside of us can also fix issues if it has not been fixed. We are investigating other issues also which can take good amount of time also.
Just to confirm, there’s no good solution yet? Tried to install sideserver on my brother’s 15 pro using my mac, got the instproxy error.
did you follow the instructions to generate a new pairing file?
that and not having wireguard enabled are the two causes AFAIK
both easily fixable
Let me scroll back up and try to find it. I don’t see it pinned unfortunately
I assume its this one. I’ll give it a shot