It looks like the latest release removed the possibility to access mapped ports (e.g.,

-p 127.0.0.1:2638:2638

) on localhost and is forcing the bridge device on us – is that on purpose? Because this is a huge problem for us to the point that we can't use OrbStack anymore. The Python version we use (https://github.com/astral-sh/python-build-standalone) can't resolve .orb.local hostnames (

gaierror: [Errno 8] nodename nor servname provided, or not known

), the IPs change all the time, and we use OrbStack to run a local database, so we need to be able to configure it to something static. Any workarounds?

I also got this issue and managed to fix it by clean uninstalling OrbStack with

brew uninstall --zap orbstack

and reinstalling

hmmm my orb is not under homebrew but i'll try a reinstall. maybe a reboot first since macOS networking is sometimes a bit spicy

I can't vouch for 2638 specifically, but TCP port 5432 stopped working post-update and started working again after the clean reinstall

OK thanks, there seems to be some weirdness around 2638 which worked for years before the latest update but now stopped. changing it to 26380 seems to work 😳

there is some really weird jank going on too, tho. i've changed the port number to 26380 and it works… but somehow also in apps that are configured to 2638. this smells of some nasty global state business 😐

fix should be out within an hour

can confirm it works now! thanks, that's a huge relief! 😮‍💨

Thx !!!