You need to publicly expose ports 80 and 443 to make use of Caddy’s Automatic HTTPS. Your Docker run command only maps port 9000 to the host, but not ports 80 and 443 (or 123 for that matter).
@francislavoie I think is not clear what I would like to obtain
My server on https on 9000 port works great.
What I would like to optain is to see as follows.
When I connect (from outside my home) to https://pippo.parecchio.org:123/1/ I would like to see the page that that I see (at home) browsing http://192.168.1.10:1/
Like I said, you won’t be able to get HTTPS on port 123. The HTTPS port is 443. ACME challenges are done on ports 80 and 443 unless you use the DNS challenge.
Also, you should be aware that low ports (under 1024) are typically reserved for other kinds of services, so I recommend using higher port numbers for applications.
I think you might be looking for the handle_path directive to decide how to handle your requests with different path suffixes, but I would recommend using subdomains for routing instead of subpaths. Read more here:
@francislavoie , I’m really thankful for your support but I see you don’t understand me.
Please, forget about the SSL part (I’ve already managed to configure it) and don’t focus on the number of the ports (I will change them, the one I’ve indicated are only for example).
Let’s do differently.
In the following situation:
But to reiterate, I recommend using subdomains whenever possible instead of subpath proxying if these are services you didn’t write yourself, see the subfolder problem link above.