On Wed, Dec 18, 2019 at 12:35:22PM -0500, deeztek wrote:
Hi there,
> server {
> listen 80 default_server;
> return 444;
> }
>
> Should take care of it?
Yes. (So long as every explicit-or-implicit "listen" directive is
equivalent to "listen 80", which it probably is.)
> How wo
okay that explains it. I appreciate that. So, a default config with the
following:
server {
listen 80 default_server;
return 444;
}
Should take care of it?
How would I got about doing a default SSL config since it would complain
about the certificate?
Thanks
Posted at Ngin
On Wed, Dec 18, 2019 at 10:33:44AM -0500, deeztek wrote:
Hi there,
> Sorry maybe I am confusing you. The config file that I posted, works fine.
> What I request actually responds. So, if I were to request www.domain.tld,
> the Apache server behind Nginx responds with the correct website for
> www
Sorry maybe I am confusing you. The config file that I posted, works fine.
What I request actually responds. So, if I were to request www.domain.tld,
the Apache server behind Nginx responds with the correct website for
www.domain.tld. However, if I were to delete the config file for domain.tld
from
On Wed, Dec 18, 2019 at 07:18:32AM -0500, deeztek wrote:
Hi there,
> Here's an example config that I use:
Thanks.
Note that it is possible that the "include" files contain some relevant
config; but we can worry about that if it looks like it is the case.
What request do you make?
What respons
Here's an example config that I use:
server {
server_name domain.tld www.domain.tld;
add_header Strict-Transport-Security "max-age=31536000; preload";
keepalive_timeout 70;
#LOGS CONFIG
access_log /usr/local/nginx/logs/domain.tld/domain.tld_access.
On Wed, Dec 18, 2019 at 04:48:33AM -0500, deeztek wrote:
Hi there,
> I have a nginx reverse proxy to forward requests to various Apache websites
> behind it. This all seems to work fine unless I remove one of the proxy_pass
> configurations from nginx. Even though I remove it, nginx still fowards
I have a nginx reverse proxy to forward requests to various Apache websites
behind it. This all seems to work fine unless I remove one of the proxy_pass
configurations from nginx. Even though I remove it, nginx still fowards the
requests back to Apache to a seemingly random website this time.
I ca
