Hi Satay,
On 19.02.2020 09:09, Satay Epic wrote:
> Hello,
>
> I've NGINX 1.12-1 running on CentOS 7.2 and being used for DNS load
> balancing. However I'm seeing lots of errors in the "dns.log".. I've
> no access to the system right now but error was like.. "No response
> received from the upstre
Hello,
I've NGINX 1.12-1 running on CentOS 7.2 and being used for DNS load
balancing. However I'm seeing lots of errors in the "dns.log".. I've
no access to the system right now but error was like.. "No response
received from the upstream server" The occurrence of the errors is no
continuous but i
On Wed, Feb 12, 2020 at 07:43:11AM -0500, adrian.hilt wrote:
Hi there,
> I'm running a reverse proxy with nginx and using certbot for ssl. It's been
> working great but recently with an php server installation it's been giving
> me problems.
> I get access to the index but any other page I get a
Thank you for your suggestion. I changed gitlab as follows and removed
default from sites-enabled. This worked.
server {
listen 0.0.0.0:80 default_server;
listen [::]:80 default_server;
server_name abcd.com; ## Replace this with something like
gitlab.example.com
server_tokens off; ## Don't
On Thu, Feb 13, 2020 at 03:46:53PM -0500, CJ Ess wrote:
Hi there,
> curl -H "Host: x.com" "http://127.0.0.1/wp-admin/";
> Which succeeds - I can see in the php-fpm log that it does "GET
> /wp-admin/index.php"
>
> I have a second test case:
> curl -H "Host: x.com" "http://127.0.0.1/wp-admin/load-
Thanks again for the information! So that's typical for a cert to not
include the distribution point URIs in the certificate itself? Seems strange
to have to contact a certificate authority to find out the CRL distribution
point, no?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,28704
Hello!
On Tue, Feb 18, 2020 at 01:50:36PM -0500, trstringer wrote:
> Thanks for the quick response! How am I supposed to get the CRL for the
> other 2 certs in the chain if there is no CRL URI?
Contact CA administrators.
--
Maxim Dounin
http://mdounin.ru/
__
Thanks for the quick response! How am I supposed to get the CRL for the
other 2 certs in the chain if there is no CRL URI?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,287045,287047#msg-287047
___
nginx mailing list
nginx@nginx.org
http://
Hello!
On Tue, Feb 18, 2020 at 12:58:26PM -0500, trstringer wrote:
> I am attempting to add CRL support to my nginx proxy, and it seems to not be
> working due to the following error:
>
> client SSL certificate verify error: (3:unable to get certificate CRL) while
> reading client request header
I am attempting to add CRL support to my nginx proxy, and it seems to not be
working due to the following error:
client SSL certificate verify error: (3:unable to get certificate CRL) while
reading client request headers
>From my research, this is because nginx senses a missing CRL. But here is
t
> Now while accessing my VM ip http://x.y.z.a, I am getting "403 Forbidden"
> error in the browser. However gitlab still working. How to get both the sites
> working listening on port 80 but with different context of location?
First of all you should check the error log to see why the 403 is retur
I installed gitlab in behind nginx reverse proxy and it worked fine. Added
the below configuration. Note that location path was changed.
upstream gitlab-workhorse {
server unix:/var/opt/gitlab/gitlab-workhorse/socket;
}
server {
listen 0.0.0.0:80 default_server;
listen [::]:80 default_serve
12 matches
Mail list logo
