On Monday 21 November 2022 at 18:16:45, Frank Gingras wrote:
> Do not remove nginx without checking if anything depends on it first. As
> counter-intuitive as this may look, many hosters use nginx as a front-end
> proxy.
Hm. I had assumed that whatever this system was. the OP had set it up for
their own use, rather than that someone else may have pre-configured it, and
for me the concept of using nginx as a front-end proxy to Apache is just
bizarre.
They can both be proxies and they can both be web servers, so why not just
pick one and use it for whatever you need?
Oh well, I agree that if the OP did not set this system up themselves, such
things are worth checking.
Antony.
> On Mon, 21 Nov 2022 at 12:12, Antony Stone wrote:
> > On Monday 21 November 2022 at 17:59:58, Ju lien wrote:
> > > Hello,
> > >
> > > We are developers and supposed to create a website. The website is
> > > created but we are also supposed to put it on line through Apache.
> >
> > The first thing I recommend that you do, then, is to remove nginx from
> > the machine.
> >
> > In case you are not aware, Apache and nginx are both web servers, and you
> > will run into all sorts of trouble if you try to run both on the same
> > machine.
> >
> > I also recommend that you do no configuration of apache whatsoever, and
> > make sure you can get to the example web page which is supplied with every
> > installation of Apache I have come across.
> >
> > Here is a random example I just found from a Google search:
> > http://www.lukminer.net/
> >
> > Once you can get your web server to show *that* then you are ready to
> > start configuring it for your own content.
--
I know I always wanted to be somebody, but I guess I should have been more
specific.
Please reply to the list;
please *don't* CC me.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|