Hi All,
I had GeoIP work on nginx 1.14.x. I upgrade to nginx 1.16.x and the whole thing
broke so I decided to just upgrade to GeoIP2. I have the following below in
nginx.conf which I saw on the nginx page.
load_module "/usr/local/libexec/nginx/ngx_http_geoip2_module.so";
load_module "/usr/local/
Hi All
I seem to be having a problem with my NGINX config. I have a website behind
nginx. The site seems to return a 500 error every time a client requests a
partial page load from the website. Whenever a full page load is requested,
the page loads just fine.
Any ideas why this could be happening?
Well I have been testing this further. What I have found is that the issue
is really not autodiscovery. When the device initially tries to connect it
uses autodiscovery but when that fails, you are presented with several
boxes to type in the server name, domain name etc. At this point, when I
put i
Thanks for the pointer. I took a look at the solution. From what I gather
though, that user used his solution for all clients. My problem that I am
trying to figure out is that the Android Phones work just fine. I guess I
was just trying to see if anyone could help me figure why only the later
mode
Hi All
I have my owa reverse proxy working. For some strange reason, all ipads
cannot now sync. Android is fine. I am seeing an error that they are trying
to connect using autodiscovery and I am not seeing a way to disable this in
IOS. Is there a way then to proxy the autodiscovery attempt in nginx
You were absolutely correct. It is working now. I changed three things. I
firstly forced TLS 1.0 then changed the directive ssl_protocols to
proxy_ssl_protocols as you suggested. Finally, I restricted to Cipher list
as you also mentioned. I had thought that I would leave all that out and
tie things
I did an ssldump and this is the conversation between both servers:
New TCP connection #1: nginx.domain.net(46318) <-> backend.domain.net((443)
TCP: nginx.domain.net((46318) -> backend.domain.net((443) Seq
54751863.(307) ACK 350741031 PUSH
1 1 1421082336.3009 (0.0012) C>SV3.1(302) Handshake
Sorry for taking so long to reply. I am running FreeBSD 10.1 RELEASE and it
is Openssl version is OpenSSL 1.0.1j and I installed it from the ports tree
(source).
Regards
On Tue, Jan 6, 2015 at 4:56 PM, Lukas Tribus wrote:
> > Hi. Thanks for replying.
> > I read it in two places. Here are the li
Hi. Thanks for replying.
I read it in two places. Here are the links.
1.
http://serverfault.com/questions/436737/forcing-a-particular-ssl-protocol-for-an-nginx-proxying-server
2.
http://w3facility.org/question/forcing-a-particular-ssl-protocol-for-an-nginx-proxying-server/
The full error is this:
Hi All
I'm trying to use nginx to also proxy to owa. I am getting the error
*peer closed connection in SSL handshake while SSL handshaking to upstream*
I have read that this is due to a bug and that the solution is to downgrade
to openssl 1.0
I don't want to downgrade because I would want users t
w.wiredrive.com/>www.twitter.com/wiredrive
> <http://www.twitter.com/wiredrive>www.facebook.com/wiredrive
> <http://www.wiredrive.com/facebook>*
>
> On Tue, Dec 30, 2014 at 1:18 PM, Peter Fraser
> wrote:
>
>> Thanks for that. I found out also that I need to export all
redrive.com
> <http://www.wiredrive.com/>www.twitter.com/wiredrive
> <http://www.twitter.com/wiredrive>www.facebook.com/wiredrive
> <http://www.wiredrive.com/facebook>*
>
> On Tue, Dec 30, 2014 at 11:34 AM, Peter Fraser
> wrote:
>
>> Hi All
>>
Hi All
I managed to get the nginx reverse proxy up and forwarding to my https web
server.
I think I have missed something though as a user just let me know that when
he tried to access the site he gets a message that the certificate is
invalid.
I just did a test with ssllabs and noticed that it sh
Hi All
I'm building my configuration slowly. Thanks for all the help so far. My
current obstacle is this:
As it is now, external users will access an internal IIS web server by
using http://my.domain.com. The firewall points to the web server and the
web server automatically redirects to https://
Hi All
I am very new to nginx and am currently doing a lot of reading but would
just love to have a nudge in the right direction
I want to set up nginx as a reverse proxy for about three IIS servers
behind a firewall.
One of them is a public web server that handles secure logins. It is
configured
Hi All
I am very new to Nginx and am very interested in setting it up as a reverse
proxy. Is it possible to have an nginx host behind a firewall with one
network card that forwards requests to more than one IIS web server behind
the firewall also, or do I need to make the nginx host inline with two
16 matches
Mail list logo
