Hi gang,
Very strange one happening at my end that I can’t get my head around.
Got an app that’s been running on a MacOS Ventura Mac for some time. Now, for whatever reason, it refuses to connect to a local cubeSQL server on the same subnet.
What’s even more bizarre, is another app on the same Mac, with pretty much the exact same connection code, launches and connects fine.
Also, if I put the Remote Debugger on that Mac and run it from my Dev Mac, it launches and connects!
I’ve created another user account on the Mac and same issue.
It’s as if there’s something on that Mac that’s stopping that particular app from connecting the cubeSQL Server.
Anyone able to assist / point me in right direction?
Regards,
Dave.
Is your app sandboxed? If so has it been given permission to connect to servers over a network.
Hi Ian,
No mate, private app, not going on the appStore - it’s just stopped working - quite bizarre. Just sits there and eventually the cubeSQL connection times out (set it really high too). Pulling my hair out heh. Cheers.
Are you using 2024r3 or above on Sequoia. There’s been a suggestion that it fails to allow network connections for the first few moments after staring the application? Is your problem solved if you try connecting after the app has been started for a while?
Dev, I’m using 2024r3.1 on Ventura… keeping MacOS Sequoia out of the picture for the time being. And no, the cubeSQL server connection times out, regardless of how much time I give it, which is normally instantaneous as it’s all on the same network - server is on a 10Gb connection, and is a rack mount MacPro, so plenty of horsepower and bandwidth available - I should also mention that there are about 70+ other Mac’s connecting to it just fine. It’s just this one Mac driving me scatty. Gonna format the thing and start over. Gah.
Kinda sounds like the usual suspects. Firewalls, antivirus software, etc. It’s the same subnet, so routing is out. If you try temporarily swapping the IP address with another working machine does the problem follow the IP address?
Indeed. I didn’t think of using an alternative IP - so I gave it a static IP outside of the DCHP range - same issue 
Other oddness, I can ping the cubeSQL Server and I can even start a SSH session to it using Terminal on the affected Mac…
A good server admin should have blocked IP addresses that shouldn’t exist. Which is why a suggested swapping two valid addresses.