This does look like a problem on Render.com rather than in Phoenix already. I’ve never used it myself. I suspect now the Phoenix app works and main_proxy too as expected but there’s some additional problem with generating SSL certificate or serving it over render.com…
hubertlepicki
elmercante
Yea I think you’re right. I’ve removed my https configurations for main_proxy after reading about their policy on TLS (SSH) certificates and this post in their community. I’m going to try reaching out to their support team about it. If things don’t work out with Render, which service would you suggest using for this sort of setup with main_proxy?
0
hubertlepicki
I was using it with both Heroku and Gigalixir, also have the app now moved to Google Kubernetes Engine. This library is pretty deployment-agnostic.
1
stefanluptak
I think there could be a mismatch between your backends specification and the custom domains (with certificates) you set-up in the render.com settings for your app.
EDIT: I ran few apps with MainProxy on render.com successfully.
2
elmercante
So you’re saying that I need to have the actual custom domains configured in the backends specification, @stefanluptak?
Right now I’ve got the backends configured to use the domain from the RENDER_EXTERNAL_HOSTNAME env variable that Render provides for their provisional onrender.com domains (I haven’t got to setting up the custom domain yet).
0
stefanluptak
elmercante
defmodule MyAppProxy.Proxy do
use MainProxy.Proxy
@render_external_hostname Application.compile_env!(:my_app_proxy, :render_external_hostname)
@impl MainProxy.Proxy
def backends do
[
%{
domain: @render_external_hostname,
phoenix_endpoint: MyAppWeb.Endpoint
},
%{
domain: "my-cms.#{@render_external_hostname}",
phoenix_endpoint: MyCmsWeb.Endpoint
},
%{
domain: "my-admin.#{@render_external_hostname}",
phoenix_endpoint: MyAppAdminWeb.Endpoint
}
]
end
end
0
stefanluptak
If the RENDER_EXTERNAL_HOSTNAME is app-123.onrender.com for example, then it means that for MyCmsWeb and MyAppAdminWeb to work, domains my-cms.app-123.onrender.com and my-admin.app-123.onrender.com would have to exist, but that’s not the case, because you’re not able to create DNS records for onrender.com subdomains.
If you don’t want to use your own custom domain, you should probably use :path instead of :domain.
But I suggest to set up your custom domain. Then save it’s value to a CUSTOM_DOMAIN env var for example and use that one in your MyAppProxy.Proxy code instead of the RENDER_EXTERNAL_HOSTNAME.
3
elmercante
Ok I gave :path a try, but the problem I’m running into now is that the cms is taking up all the spare paths. That is to say all the paths which aren’t already defined in the router file as routes for the app’s functionality are reserved for the cms. There’s probably a way to skirt around this, but I’d prefer not to complicate things further.
I think the only way forward is to use a custom domain as you suggested, but I was hoping to test things out with Render’s provided onrender.com subdomain first. I’ll continue to experiment with this and I’ll drop an update here if there’s anything useful to share. Thanks for your help @stefanluptak!
2