Enabling https for stanalone runtime app server

What I’m trying to do:
Enable https for standalone app server

Why I’m doing this
I’ve read on this forum that when you’re using anvil standalone app server remember login session only works if you give an origin parameter starting with https followed by FQDN

Here is some details about my environment:

Platform: Vmware ESXi
OS: Ubuntu 20.04
IP: 10.71.11.XX
Hostname: sub

#provided in config.yaml
origin: "https://sub.domain.com"

#OS firewall is disabled and 443 is open

#confugred with domain registrar
sub.domain.com points to --> real-ip:3030 

#configured port forwarding
real-ip:3030 points to --> 10.71.11.XX:3030

when run with this config traefik fails to get SSL certificate from lets encrypt for my FQDN

app works fine without https in config.yaml

Please forgive my ignorance…

maybe It only works if my app server has a real ip and subdomain pointing directly to it?

maybe my i need to port forward like this?

real-ip:3030 → local-ip:443

or maybe like this?

real-ip:443 → local-ip:443

which i can not do because real-ip:443 is already used.

How should i update my setup to make it work?

Has anyone else had issue with enabling https for their standalone app server?

You might try this first. It is the easiest way to set up https for the server, I need to do try and error million times before it works:

After that, you can try your own configuration.

However, you might face this issue after that:

@rsmahmud Were you able to resolve your issue? I’m running into a similar problem. For at least our QA server, I would like to host multiple anvil-runtime containers (each with a different application and sub-domain combination) behind an nginx reverse proxy configured with Let’s Encrypt SSL certs.

Our application doesn’t run properly with any combination of origin URL and reverse proxy from nginx that we’ve tried thus far. If we go directly to the :3030 port of the anvil-runtime it functions correctly.

Using the proxy we see this: