I have the gut feeling that the problem (challenge?) might involve this minor technical detail:
Private Relay replaces the user’s original IP address with one assigned from the range of IP addresses used by the service.
Be it as it may, my WebSocket clients using Apple private relay can't connect to my WebSocket server. They connect perfectly if I disable Limit IP Address Tracking here:
Has anyone found a way around this recent roadblock?
I believe that if Apple really restricts this replacement of IP addresses to Mail and Safari (leaving everything else undisturbed), our WebSocket clients would continue working well when using Apple private relay.
I have the gut feeling that the problem (challenge?) might involve this minor technical detail:
Private Relay replaces the user’s original IP address with one assigned from the range of IP addresses used by the service.Be it as it may, my WebSocket clients using Apple private relay can't connect to my WebSocket server. They connect perfectly if I disable
Limit IP Address Trackinghere:Has anyone found a way around this recent roadblock?
The note from Apple: https://developer.apple.com/support/prepare-your-network-for-icloud-private-relay/
An example of Apple Developer conversations: https://forums.developer.apple.com/forums/thread/734947
I believe that if Apple really restricts this
replacement of IP addressesto Mail and Safari (leaving everything else undisturbed), our WebSocket clients would continue working well when using Apple private relay.Thanks for any guidance.