Cloudron Forum

Glad to hear that you got it working! By the way, have you had any luck logging into the HomeAssistant companion app (iOS in my case) using the proxied domain?

You have to install nginx and put those configs on the server where you deployed odoo . That is the correct place for putting those multiple port configs. Then nginx will then answer to a single port 80 which you can then put into cloudron.

@senthilkumaran said in Cloudron Subdomain pointing to a different IP for Apps not on Cloudron: https://i.imgur.com/3gtJVw1.png - wildcard means that all the *.thinnal.org will point to the cloudron's ip. If you have *.domain.org and foo.domain.org entries in your DNS provider , then foo.domain.org being more specific wins. One crucial note: this is not a feature of DNS since DNS protocol itself no concept of wildcard. This feature comes from the DNS providers (I think this comes from bind9 configuration files). But interestingly, I have the root domain thinnal.org pointing to a different IP and it works fine. Yes! because *.domain.org does not include domain.org . It only includes subdomains of domain.org but not the bare domain itself. This is another important DNS quirk to know.

Thanks sorry did not see that

@doon Perhaps you can do a writeup as a guide for the rest of the forum on your use case?

I forked this into a separate thread. Think we need some more context. Are you saying using localhost:port of your MacOS device does not work with the app proxy anymore? In the recent releases, an app proxy related change that happened is that we set the Host header to the initial request endpoint. Would your set up be affected by this change by any chance? Related issue in NPM - https://github.com/NginxProxyManager/nginx-proxy-manager/issues/127

@nebulon test, as in previous testing proxying across cloudrons, and to other search engines worked just fine, and these tools sites, didn't.

@robi new cloudron release

I've tried to use pgadmin and jupyter notebook under App Proxy today and I can confirm that the issue still exists, since /login/ locations are required by both apps but are also reserved for cloudron. Pretty annoying ! @joseph : this is not solved, can you unmark it?

@MooCloud_Matt I think you can just use "no-op" in your situation and also use a custom wildcard certificate. The proxy can then accept just that wildcard cert. no-op ignores DNS checks. The cert can be Let's Encrypt or not depending on if your proxy can carefully forward well-known HTTP requests.

@girish Perfect, that's where I went wrong, thanks.

Thanks for the insights, @arshsahzad and @girish, I’ll explore these solutions. As for tailscale and cloudflare, I’d have to set them up externally to cloudron on the server, right? Which I’ve always thought was not recommended. Think I’ll try it anyway and get back to you guys. I’ve already setup a vpn on my home server with wireguard so maybe I’ll go with that. Thanks!

Feature request at https://forum.cloudron.io/topic/8487/enhance-app-proxy-app-with-path-and-port-support

@matthijs that's not possible because HTML/Javascript is opaque "data" and one cannot replace things without understanding what the data is. For example, the HTML could say "Your IP is NOT xxxxx" or "Your friend is at IP yyyy" or just about anything else. There is no way to reliably replace HTML (other than the app itself).

@dominikjannis Do you think you can send me the IP address to support@cloudron.io ? I can test it out from my test instance.

@robi Thank you!! Nginx Proxy Manager is a UI + LetsEncrypt for Nginx if I have to simplify it. Do you have a sample Nginx proxy conf for this setup? Thanks again!

Fixed in https://git.cloudron.io/cloudron/box/-/commit/84ba333aa11fe7d0e2ae00d2b1437efc27a876b4