Loving twingate so far. Have an issue that is puzzling me and would love guidance/advice on finding a potential solution.
I have the twingate connector and client installed on a VPS running Almalinux 9.3 (called it, rproxy)
This VPS (rproxy) serves as a reverse proxy for my backend server (call it, bend01)
The connector serves as an entry way for my clients (e.g. windows laptop, iPhone) to reach the VPS (rproxy) from the outside securely without opening inbound 22 and 9090 to the world.
Port 22 and Port 9090 map to services that enable me to manage the rproxy server. My iPhone and Windows laptop have the twingate clients installed, so they can reach rproxy on those ports.
The headless client on the VPS (rproxy) connects to my backend server (bend01), and the backend server (bend01) has the twingate connector on it.
When both the client and connector are installed on VPS (rproxy), my windows and iPhone clients stop communicating to the VPS (rproxy).
When the connector and only the connector is installed on VPS (rproxy), my windows and iPhone clients can reach it no problem, but, when the head-less client is installed my windows and iPhone clients cannot reach it anymore.
Here is what i’m trying to accomplish:
I have services and apps running on my backend server, some services (e.g. Jellyfin) I want to access without needing a connector installed on every device.
I have the connector set-up on my backend server, this is what the headless client on my reverse proxy instance connects to in order to reach the backend server and it’s services and apps, securely.
With this set-up I can open port 443 on the reverse proxy, and the proxy will take incoming requests and route to the appropriate backend services. This design masks my backend from the world, and the world only sees my reverse proxy and not my backend server.
All that said, I want to know why, when the connector and client is installed at the same time on my rproxy host, my clients, iphone and windows, cannot communicate to it.
Thank you so much!