Am 14.08.2020 um 19:47 schrieb Carsten Bäcker:
Domain-Names are HTTP-specific. No ssh, nor telnet or ftp know anything
about that.
Hmm. Forget about that...
It's basically an issue related to firewall / port-forwarding.
___
freebsd-jail@freebsd.org mai
Hi,
nginx will only see packets that passed the firewall, so you need to
allow incoming traffic to port(s) 80, 443 to whereever your
reverse-proxy is running.
Domain-Names are HTTP-specific. No ssh, nor telnet or ftp know anything
about that.
Personally i wouln't even thing about using telnet or
On Fri, 14 Aug 2020 10:58:03 -0400
Ernie Luzar wrote:
> Carsten Bäcker wrote:
> > Hi,
> >
> > you may want to have a look into reverse proxying, e.g. using nginx on
> > your jail-host.
> > Really basic example:
> >
> > |http { server { listen 80; server_name your.1st.domain.com; location /
> >
Carsten Bäcker wrote:
Hi,
you may want to have a look into reverse proxying, e.g. using nginx on
your jail-host.
Really basic example:
|http { server { listen 80; server_name your.1st.domain.com; location /
{ proxy_pass http://127.0.1.2; } } server { listen 80; server_name
your.2nd.domain.com;
Hi,
you may want to have a look into reverse proxying, e.g. using nginx on
your jail-host.
Really basic example:
|http { server { listen 80; server_name your.1st.domain.com; location /
{ proxy_pass http://127.0.1.2; } } server { listen 80; server_name
your.2nd.domain.com; location / { proxy_pass
