macOS Sequoia - no route to host

[abugray]

i cant connect to my servers after upgrade to macOS Sequoia 15.0. I think its problem because Transmission Remote GUI not appear in local network permission settings.

[dreyks]

as an immediate workaround running the app from cli (/Applications/Transmission\ Remote\ GUI.app/Contents/MacOS/transgui) seems to work (because it reuses the permissions from the terminal)

[abugray]

thx! Its helped me!

[moffatman]

I think it works, I got the permission question about it, but just had to relaunch the app for it to work.

[dreyks]

hmm... I'm not getting any permission prompts neither running standalone nor from the terminal. it just works when started from the terminal and doesn't work otherwise

[camhorn]

Prompts for me on on my M1 Studio, does not prompt on my M2 Air. The terminal workaround works in the latter case, but I had to trigger the prompt via a different action (e.g., curl <local address>).

[dreyks]

yup, I have an M2 Air as well. no prompt in any combination

[tcurdt]

I also have start it via Terminal. No prompt for me.

TBH I blame the shitty permission implementation in macOS 15 - but I guess we have to live with for now.

[itsNotMyUsername]

I was not getting any prompts and was using terminal to open. Just now Ive opened normally through the icon click and it eventually asked for some permissions and works now. I think I rebooted my MBP (intel) few times and maybe that eventually picked the right trigger, not sure.

[RyanFarley]

I rebooted and it happened to ask me for permission to discover devices on the local network. After allowing, it does work normally for me now without needing to launch from terminal.

[dreyks]

rebooted several times and each time a prompt for a different app was popping up. three reboots in and I finally got the prompt for transmission. now everything is working. still not sure how it is intended to work 🫠

[tcurdt]

For me it also took a reboot. I fear this a fail on Apple's part.
With the workarounds documented - I guess the ticket can be closed?

[syluccy]

Mac OS 15.1 solved it finally.

[wahlstedt]

For me 15.1 broke it. It was working on 15.0. After updating to 15.1 I got the "no route to host" error. The fix was to disable the permission in local network permission settings and then re-enable it.

[syluccy]

Yea, I've never used this solution.
At 15.0 I've encountered the problem, but been waiting for a better fix. Then 15.1 suddenly brought the solution. After first reboot the system asked for permission to Transmission remote accessing local network.

[Morgul]

I'm having this problem, upgraded directly to 15.1, and it will not pop the permission dialog for me, no matter what I do.

Running from the terminal worked, so I have a very annoying work-around, but I'd love to know if someone's found a way to consistently make it pop the permissions dialog.

[sIRwa2]

struggling with it for a while, i went to > System settings > Privacy & Security > Local Network: there i had to enable the button behind transmission remote gui. (hope it helps someone)

[Morgul]

If I knew how to make it show up there, that'd be great. 😅

Doesn't matter how many times I've run the program, it just doesn't show up. (I'm going to try fully removing it from the system and reinstalling; it's the last idea I have.)

[salvor-hardin]

This seems to be the reason:
https://apple.stackexchange.com/questions/475737/how-can-i-manually-allow-local-network-access-for-an-app

Developers to add new requirement.
In the meantime launching the app from terminal sounds like an acceptable workaround.

In the meantime, users for Sequoia unaware of this issue/workaround/github (the vast majority!) will NOT be able to use the app.

I am sure that @PeterDaveHello and the rest of the team can very easily get this fixed in a new release.

[lighterowl]

This seems to be the reason: https://apple.stackexchange.com/questions/475737/how-can-i-manually-allow-local-network-access-for-an-app

Developers to add new requirement.

I believe this isn't the right thing to look for, and that requirement cannot be "added" as it must be first granted by Apple. See linked issue in my fork for more information. On top of that, this "entitlement" only applies to iOS applications, not macOS (at least according to TN3179).

[sstrang]

I finally updated to Sequoia and encountered the same problem. Rebooting again gave me the prompt to enable Local Network access, and now all is well, at least on 15.2.

[Morgul]

Mine finally worked. I launched it from terminal (not iTerm, which is what I typically use), which asked for network for Terminal (but not Transmission), then the next time I launched it normally, I got the prompt.

I really wish I knew what triggered the dialog. I've tried maybe a hundred times to launch it, plenty of reboots, and I'm on 15.1.1 right now.

So far, this is the only app I use that's had this issue.