On Tue, Jan 10, 2023 at 06:45:15PM -0500, Paul wrote:
Hi there,
> BUT... for that one step further and have all server (nginx) responses go
> back to the end-client as:
> https://a.example.com
> and NOT as:
> https://www.a.example.com
> ^^^
> I have written an /etc/nginx/conf.
On 2023-01-10 13:43, Francis Daly wrote:
Using nginx (1.18.0 on Ubuntu 20.04.5) as proxy to back-end, I have three
sites (a|b|c.example.com) in a fast, reliable production environment. I have
DNS records set up for www.a|b|c.example.com. I have CertBot set up for
only a|b|c.example.com.
To avo
On Tue, Jan 10, 2023 at 12:03:06PM -0500, Paul wrote:
Hi there,
> Using nginx (1.18.0 on Ubuntu 20.04.5) as proxy to back-end, I have three
> sites (a|b|c.example.com) in a fast, reliable production environment. I have
> DNS records set up for www.a|b|c.example.com. I have CertBot set up for
> o
Happy 2023 to all on this list.
Using nginx (1.18.0 on Ubuntu 20.04.5) as proxy to back-end, I have
three sites (a|b|c.example.com) in a fast, reliable production
environment. I have DNS records set up for www.a|b|c.example.com. I
have CertBot set up for only a|b|c.example.com.
To avoid "do
