Cloudron and Apps Behind a Proxy

[doodlemania2]

@girish this is likely just me not knowing how nginx works:

Was hoping crtest.altdomain would pass to existing my.apps.primarydomain and it would "just work" but I got the "You've found a cloudron in the wild"

That was somewhat expected cause the CR doesn't know about crtest.altdomain. Was kind of hoping NGinx would have done that translation for me by keeping the destination as the 'URL' that I wanted.

I suppose I could create a crtest.altdomain in CR and things would magically just start working, but I'd have to assign the altdomain names to each of my apps, I think??

[girish]

@doodlemania2 As a first step, you can try this to understand how it might work:

curl -k -H 'Host: app.domain.com' https://<cloudron-server-ip>

To explain the above, first we try to reach the cloudron server by IP via https. In your case, (if I understood your setup), this IP will be the intranet cloudron server IP (and not the public one). Next, the Host header helps (cloudron) nginx decide which vhost/app the request is meant for. Finally, the -k is needed because curl will not be able to match the server cert because we are accessing by IP but the cert will be whatever the host header was set to.

If the above works, you just have to make it work in the above UI:

• Make sure destination is https://ip
• I am guessing the Host header is automatically set
• You have to accept the cert.

[doodlemania2]

@girish Some success! This is wicked cool - and, by the way, I now have BBB server up and running for CR folks to use anytime they/yall need.

One question - when I go to my CR sites now, I am getting a cert error - you indicated that would likely happen I think. Any way to avoid that?

https://conference.cloudromdomain is nginx proxy to https://ip-address-of-cloudron.

[girish]

@doodlemania2 I think this is because nginx proxy manager does not have valid certs for the conference subdomain. Does it say it has valid certs?

[doodlemania2]

@girish I think it's clean now - I tweaked the nginx. Should be able to see it at https://conference.apps.thedoodleproject.net huzzah!

[girish]

@doodlemania2 Can confirm I can see it with proper certs

[doodlemania2]

well, spoke almost too soon - now that I've got that up and running, I thought that I could force https, but Let's Encrypt doesn't like that because it needs to hit HTTP at a well known endpoint. So, am going to continue to tinker to see if I can pass both http and https

[girish]

@doodlemania2 Cloudron does not require http for certs if you use the programmatic DNS backends (since it obtains certs by putting entries in DNS and not using http callbacks).

[doodlemania2]

@girish ahhh that's cool! Sad for me, using Azure DNS
I'm gonna try and figure out how to make my NGinx let both HTTP and HTTPS through on the same domain name - that would seem to be an obvious option hehe

[Jan Macenka]

@doodlemania2 did you make any progress here?

My Use-Case:
I love CR for my own business and recommended it to one of my clients aswell. We want to operate it in their own infrastructure so in some private networks that are not fully exposed to the internet ans also I cant route 80/443 soley to CR since they are also operating other Web-Services which are not available in CR.

What I am trying to achieve
Get cloudron to run on a private network behind a NginxProxyManager in parallel to other web-services.
SSL handling can be left to CR and Nginx should behave like a proxy server but only for sub-domains that are in conjunction with CR-Services. Ideally the forwarding rules would automatically get updated through

What I tried so far
Pretty much what you and others also tried. Setup is:
Internet => NignxProxyManager => Cloudron as VM on a lager ESXi in Parallel to other Webservices

Did you make any progress there or gave up eventually?

[doodlemania2]

@Jan-Macenka I did! Here's my setup:

1. Set up a wildcard cert with nginx proxy manager
2. I forward *.domain bound for Cloudron to my cloudron server (in my instance located via a wireguard tunnel)
3. I set DNS in Cloudron to NoOp

Easy peasy!

[Jan Macenka]

@doodlemania2 thank you for the suggestion. I replicated the setup though with no success as of yet. Could you be so kind and check if you did anything different?

Here is what I did:

Created DNS Records pointing to the public IP which will lead to the NPM:

Configure Wildcard certificate in NPM pointing my *.<DOMAIN> to the server within the private network.

Set Cloudron DNS to NoOp:
<for some reason cant paste the screenshot>

I notices that there is also a "Wildcard" Option in the CR DNS Settings but choosing this one also yielded no success. Any hint on what you did differently?

[fbartels]

@Jan-Macenka I would expect that you need to change the destination port to https…:443.

[Jan Macenka]

@fbartels tried that aswell but with no success so far. I'll keep trying and can post again if I am successfull.

[doodlemania2]

@Jan-Macenka that's almost exactly what i did. check your firewalls and make sure you aren't blocking 443 inbound from your CR server on your private IP address?

[alwynispat]

@doodlemania2 somewhat related, does the apps in cloudron report client ip as your nginx proxy manager's ip or their true ip?

[girish]

@alwynispat X-Forwarded-For should be set when forwarding. Does nginx proxy manager support reading the IP from a header?

[alwynispat]

@girish said in Cloudron and Apps Behind a Proxy:

X-Forwarded-For

I got it setup like this but doesn't seem to work. Does anyone have better luck?

[alwynispat]

I'll create a new thread on this topic.