Orbot can not reconnet to tor

[VGFP]

Hi, I have issue with app. It can not reconnect to tor (after installation first connection is successful but if I want to connect a second time it says "connecting" stops after a second and connection is not created. OS: iOS 16.5 Device: iPhone 14 plus

[AW-2000]

DI have this exact same issue. Using an iPad with iOS 16.5. I installed Orbot after my Onion Browser app said I had to install Orbot to continue to use the app. Orbot worked the first time I installed it, but then cannot connect; just keeps trying to connect and then returns to start over. When I expand the window to see what is happening, I see “ Jun 17 10:02:20.000 [notice] {GENERAL} Parsing GEOIP IPv6 file /var/containers/Bundle/Application/A8425778-4EA2-442F-9109-E3A6F249D3AF/Orbot.app/Frameworks/Tor.framework/GeoIP.bundle/geoip6. Jun 17 10:02:21.000 [notice] {CONTROL} Bootstrapped 0% (starting): Starting”. I have another VPN on my device but it is disconnected and auto connect is off. If I delete the Orbot app and then re-install it, it again works the first time I use it, but then the above happens again if I try to use it a second time.

[tladesignz]

Cleaning the cache might help. (In the drop-down menu, Settings, at the very end.)

Unfortunately, Apple gives us a hard limit of 50 MByte RAM usage.

If the list of nodes, Tor acquires over time, gets too big, Tor hits the RAM limit on start and gets killed again. (This list is cached on disk and reused, so you can connect faster.)

Let me know, if this helps!

I get more and more notifications about this. Maybe, there's something with the network going on and we will need to rethink that cache handling. What do you think, @n8fr8?

[VGFP]

Cleaning the cache might help. (In the drop-down menu, Settings, at the very end.)

Unfortunately, Apple gives us a hard limit of 50 MByte RAM usage.

If the list of nodes, Tor acquires over time, gets too big, Tor hits the RAM limit on start and gets killed again. (This list is cached on disk and reused, so you can connect faster.)

Let me know, if this helps!

I get more and more notifications about this. Maybe, there's something with the network going on and we will need to rethink that cache handling. What do you think, @n8fr8?

Clearing cache works 🙂 I suggest adding option to automatically clear cache when disconnecting or moving clear cache button to faster to access place (main view)

[AW-2000]

Thanks. That worked for me also (even though it took a minute to find the Clear Cache command because it wasn’t showing under Settings until I scrolled down). AndyOn Jun 17, 2023, at 3:07 PM, Benjamin Erhart @.***> wrote: Cleaning the cache might help. (In the drop-down menu, Settings, at the very end.) Unfortunately, Apple gives us a hard limit of 50 MByte RAM usage. If the list of nodes, Tor acquires over time, gets too big. Then Tor hits the RAM limit on start and gets killed again. (This list is cached on disk and reused, so you can connect faster.) Let me know, if this helps! I get more and more notifications about this. Maybe, there's something with the network going on and we will need to rethink that cache handling. What do you think, @n8fr8?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[AW-2000]

Thanks. That worked for me also (even though it took a minute to find the Clear Cache command because it wasn’t showing under Settings until I scrolled down). AndyOn Jun 17, 2023, at 5:19 PM, VGFP @.***> wrote:

Cleaning the cache might help. (In the drop-down menu, Settings, at the very end.) Unfortunately, Apple gives us a hard limit of 50 MByte RAM usage. If the list of nodes, Tor acquires over time, gets too big, Tor hits the RAM limit on start and gets killed again. (This list is cached on disk and reused, so you can connect faster.) Let me know, if this helps! I get more and more notifications about this. Maybe, there's something with the network going on and we will need to rethink that cache handling. What do you think, @n8fr8?

Clearing cache works 🙂 I suggest adding option to automatically clear cache when disconnecting or moving clear cache button to faster to access place (main view)

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[tladesignz]

Closing this. Work will be tracked in #67. Thanks for letting me know!

[tladesignz]

https://twitter.com/tladesignz/status/1672202386310307840