I am encountering more and more issues with an app I created that binds to 127.0.0.1 on an obscure port. I have a domain name - due to needing an SSL cert - that resolves to 127.0.0.1.
I have this because my browser-based solution connects to the app on the local machine over a secure web socket, for example, I use wss://mydomain.com to connect.
For most people, this works just fine.
But more people are not connecting. I've come to learn DNS rebinding protections are likely at work. A solution for most people I've found is updating their local DNS to 8.8.8.8. If they do this it works. However, the out-of-the-box experience is being hindered.
Is there any reliable way to bypass DNS rebinding or set my app up in a way that doesn't have the issue?
I heard that using an obscure 127, like 127.211.134.233, could work.
Any help is greatly appreciated