Description

msun68

opened on Jul 18, 2023

Issue body actions

Describe the bug

I am using OrbStack 0.14.1 in a corp network. Any connection to external needs to go through proxy(configured in MacOS settings via .pac)
If I set to Automate in OrbStack, my containers are keeping getting stopped due to “license check failed”
If I set to Custom, the proxy exclusions configured in MacOS settings is not respected and they can not be configured in OrbStack.

To Reproduce

No response

Expected behavior

Proxy exclusions configured in MacOS settings should be respected or OrbStack should allow configure proxy exclusions when Custom proxy is chosen.

Logs

No response

Screenshots and additional context (optional)

No response

Activity

1. msun68

   added

   t/bugSomething isn't workingSomething isn't working

   on Jul 18, 2023
2. kdrag0n commented on Jul 19, 2023

   

   kdrag0n

   on Jul 19, 2023

   Member

   More actions

   Can you share as much of your proxy exclusion list as possible? It's not always possible to respect domain exclusions due to how transparent proxying works. Only IP exclusions can be implemented 100% reliably, so it'd be helpful to see what your exclusion list looks like.
3. msun68 commented on Jul 19, 2023

   

   msun68

   on Jul 19, 2023

   Author

   More actions

   The exclusion list is like following: .local,169.254/16,10/8,.trusted.xyz.com
   It is not configurable. We have a private docker registry using a domain docker.trusted.xyz.com
   I can not access this registry when custom proxy is set in OrbStack.
4. kdrag0n commented on Jul 19, 2023

   

   kdrag0n

   on Jul 19, 2023

   Member

   More actions

   Is there any chance you could also share the PAC file with exact hosts redacted? No worries if not.
5. msun68 commented on Jul 19, 2023

   

   msun68

   on Jul 19, 2023

   Author

   More actions

   It is long file and I can not share in GitHub (blocked by firewall)
6. kdrag0n commented on Jul 19, 2023

   

   kdrag0n

   on Jul 19, 2023

   Member

   More actions

   OrbStack was already using system exclusions, but it couldn't parse the 10/8 subnet syntax. Fixed for the next version.

   Domain-based exclusions have also been implemented and will be respected whenever possible.

   As a workaround, changing the exclusion to 10.0.0.0/8 should work for now.
7. kdrag0n

   closed this as completedon Jul 19, 2023
8. kdrag0n

   added this to the v0.14.2 milestone on Jul 19, 2023
9. kdrag0n commented on Jul 23, 2023

   

   kdrag0n

   on Jul 23, 2023

   Member

   More actions

   Released in v0.15.0.

Issue actions