OK, thank you
On Sun, Jan 23, 2022 at 9:47 AM Sergey A. Osokin wrote:
> Hi Julian,
>
> hope you're doing well.
>
> On Sat, Jan 22, 2022 at 03:22:40PM -0600, Julian Brown wrote:
> > Currently I run Nginx as a reverse proxy in a Docker container.
> >
> >
Currently I run Nginx as a reverse proxy in a Docker container.
FROM nginx
ENV DEBIAN_FRONTEND noninteractive
... Details hidden ...
EXPOSE 80
EXPOSE 443
CMD nginx -g 'daemon off;'
We are wanting to use Graylog, and have it for our other containers. So I
want to now use it for Nginx. Graylo
I am having a problem and not sure which side of the ocean it is on (Nginx
or Apache).
I am internally setting up an Nginx reverse proxy that will eventually go
public.
I have two domains I want Nginx to proxy for, both go to different machines.
The second domain is for a bugzilla host, bugzilla
019 at 08:08:47PM -0500, Julian Brown wrote:
>
> Hi there,
>
> Well done in spotting that -- it has come up before, but obviously wasn't
> something that someone noticed quickly enough this time.
>
> > I finally figured it out, and I cannot believe it passed a syntax
&
do not know what it was trying to do.
Anyway thank you all.
Julian
On Thu, Apr 25, 2019 at 6:21 PM OiledAmoeba
wrote:
> 25. April 2019 21:27, "Julian Brown" schrieb:
>
> > listen 443;
> > listen [::]:443;
>
> I'm lazy, so I used "listen [::]:443 ssl
I just tried both, (removed the ipv6 entry) and tried both of the above.
Now nothing is on 443, not even ipv6 (which is ok).
This is totally wierd.
Thank you
Julian
On Thu, Apr 25, 2019 at 2:37 PM Rainer Duffner
wrote:
>
>
> Am 25.04.2019 um 21:27 schrieb Julian Brown :
>
>
ce web
server and a reverse proxy server.
I tried to strace it, and it does not even try to bind to 443 on ipv4, it
is almost like it is compiled to ignore port 443 on ipv4.
Can someone help me?
Thank you
Julian Brown
___
nginx mailing list
nginx@n
