Is It Possible To Connect NGINX As A Reverse Proxy Manager To Argo?

Is it possible to run NGINX as a reverse proxy connected to Argo and have CNAME DNS entries pointing to the root so that specific sub domains will hit the Cloudflare Tunnel , and NGINX can route the subdomain that was requested to the proper port that the service is running on? For example, NGINX reverse proxy running on http://example.com. DNS CNAME entry of subdomain1, and NGINX has an entry for subdomain1 to route to http://localhost:3000.

Hello,
Would it be possible for you to clarify what you trying to achieve here?
Is there a specific point of having nginx as a reverse proxy here?
You can find more details about Cloudflare Tunnel here:

1 Like

Nginx Proxy Manager, for example, has a well-defined UI which allows easy customization of access lists/routes to various backend services. Cloudflare currently requires these mappings be done by hand in the config.yml file. It would be convenient if you could connect a tunnel to an existing NPM instance by just specifying a wildcard in the YAML config to route to port 80 locally (where Nginx is running, acting as a reverse proxy).

tunnel: <tunnel-id>
credentials-file: /etc/cloudflared/<tunnel-id>.json

ingress:
  - hostname: "*.domain.tld"
    service: http://192.168.2.2
  - service: http_status:404

Expanding upon the UI to allow ingresses to be defined in a GUI may eliminate the want/need for NPM, in any case.

Hi there!
Any luck with the NPM and the Cloudflare Tunnel ?
Regards,

This has always worked…. No update needed.

Hello,
yes, exactly, I can see that now.
It took me a while to figure it out.

Thanks!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.