Hello,
If the error comes from apache itself you should have an error log entry,
what does it say?
El mar., 20 abr. 2021 4:03, Dave Wreski
escribió:
> Hi,
>
> I have an apache-2.4.46 system on fedora33 and having weird 500 errors
> that I can't explain.
>
> 72.70.38.104 - -
Hi,
I have an apache-2.4.46 system on fedora33 and having weird 500 errors
that I can't explain.
72.70.38.104 - - [19/Apr/2021:21:38:56 -0400] "GET
/advisories/debian/debian-dsa-2944-1-gnutls26-security-update HTTP/1.1"
500 12704 "-" "Mozilla/5.0 (compatible; bingbot/2.0;
Thank you Michael.
On Tuesday, April 20, 2021, 12:35:08 AM GMT+4:30, Michael Wechner
wrote:
sure, happy to help! I also received a lot of help on mailing lists :-)
I also understand Nick's statement though, that in order to learn, you
have to dig in yourself.
But it can be a
On Mon, Apr 19, 2021 at 3:05 PM Michael Wechner
wrote:
>
> sure, happy to help! I also received a lot of help on mailing lists :-)
>
> I also understand Nick's statement though, that in order to learn, you
> have to dig in yourself.
>
> But it can be a difficult balance sometimes, because
sure, happy to help! I also received a lot of help on mailing lists :-)
I also understand Nick's statement though, that in order to learn, you
have to dig in yourself.
But it can be a difficult balance sometimes, because sometimes one
cannot see the forest for the trees anymore.
I have
K
From: Nick Folino
Sent: Monday, April 19, 2021 1:00 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Apache Reverse Proxy and HTTPS.
You'll never learn anything if you keep asking people to solve your problems
for you.
Read the docs I posted for you and look for working
Thanks.
When I browse my IP with the HTTPS protocol, then problem solved.
On Monday, April 19, 2021, 11:30:34 PM GMT+4:30, Nick Folino
wrote:
You'll never learn anything if you keep asking people to solve your problems
for you.
Read the docs I posted for you and look for working
You'll never learn anything if you keep asking people to solve your
problems for you.
Read the docs I posted for you and look for working examples on-line.
On Mon, Apr 19, 2021 at 2:14 PM Jason Long
wrote:
> Thank you Michael.
> I changed my Virtual Host config file as below:
>
>
>
Thank you Michael.
I changed my Virtual Host config file as below:
ServerName 192.168.56.9
ErrorLog ${APACHE_LOG_DIR}/error_log
CustomLog ${APACHE_LOG_DIR}/access_log combined
RewriteEngine on
RewriteCond %{SERVER_NAME} =192.168.56.9 [OR]
RewriteCond %{SERVER_NAME}
On Mon, Apr 19, 2021 at 10:20 AM Michael Wechner
wrote:
>
> Hi Jason
>
> The reverse proxy entries should look something like
>
>
(I'm not the OP - - - but - - - - )
Thank you - - - - I find most docs and almost all man pages are written
by experts for experts who just might need a reminder and
Hi Jason
The reverse proxy entries should look something like
ServerAdmin michael.wech...@wyona.com
ServerName www.wechner.ch
ServerAlias wechner.ch
ErrorLog ${APACHE_LOG_DIR}/wechner.ch-error_log
CustomLog ${APACHE_LOG_DIR}/wechner.ch-access_log combined
RewriteEngine on
You need to read the documentation and search for examples on how to
configure HTTPS.
On Mon, Apr 19, 2021 at 8:26 AM Jason Long
wrote:
> I created a Self-Signed SSL Certificate for Apache and changed my Apache
> configuration file on Apache Reverse Proxy Server as below:
>
>
>
I created a Self-Signed SSL Certificate for Apache and changed my Apache
configuration file on Apache Reverse Proxy Server as below:
ServerName 192.168.56.9
ProxyPreserveHost On
ProxyPass / http://192.168.56.9/
ProxyPassReverse / http://192.168.56.9/
http://httpd.apache.org/docs/2.4/ssl/
Nick
On Mon, Apr 19, 2021 at 6:37 AM Jason Long
wrote:
> Thank you.
> On my Apache Reverse Proxy, I have a .conf as below:
>
> # cat /etc/httpd/conf.d/reverse_proxy.conf
>
> ProxyPreserveHost On
> ProxyPass / http://192.168.56.9/
>
Thank you.
On my Apache Reverse Proxy, I have a .conf as below:
# cat /etc/httpd/conf.d/reverse_proxy.conf
ProxyPreserveHost On
ProxyPass / http://192.168.56.9/
ProxyPassReverse / http://192.168.56.9/
And my website configuration file is on "192.168.56.9" server.
my "definitely at the proxy" was probably answered a little bit too
quickly/intuitive :-)
As Nick is writing, it depends on your requirements and I was too
focused on my own requirements :-)
Thanks
Michael
Am 19.04.21 um 12:17 schrieb Nick Folino:
That depends on your requirements. You
Hi Jason
Definitely "Apache Reverse Proxy (Public IP)", whereas you could use for
example
https://letsencrypt.org/
https://certbot.eff.org/
Depending on how your connection between "Apache Reverse Proxy (Public
IP) ---> Web Site (Internal IP)" is protected, you might also want to
consider
That depends on your requirements. You can terminate SSL at the proxy or
the web server,
Nick
On Mon, Apr 19, 2021 at 6:08 AM Jason Long
wrote:
> Hello,
> In below diagram, which server must use HTTPS certification?
>
> The Internet ---> Apache Reverse Proxy (Public IP) ---> Web Site
Hello,
In below diagram, which server must use HTTPS certification?
The Internet ---> Apache Reverse Proxy (Public IP) ---> Web Site (Internal IP)
Thank you.
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For
19 matches
Mail list logo
