Allow/Deny rules in Location block

Hello, I am trying to restrict some Location block in my Nginx configuration to specific IPs. Below are the changes I made - Version: nginx:1.21.0 location / { > proxy_pass http://127.0.0.1:8080; > } > location = /auth { > proxy_pass http://127.0.0.1:8080; >

Re: Allow/Deny rules in Location block

Hi Sandeep, I rather suspect that your top two CIDR allow lines are allowing too many people in. Remove them, and check that only the last two lines are allowed in. Then create the two top addresses very carefully, and test. 1.2.3.4/8 allows all C level addresses of the format 1.*.*.* in. I

RE: Allow/Deny rules in Location block

> I am trying to restrict some Location block in my Nginx configuration to > specific IPs. Below are the changes I made - > >location = /auth { > } > > Here, the deny rule is not working. Users are still able to access the > page publicly. Am I missing something? Are you s

Re: module geoip2 with map directive

El sáb, 21 ene 2023 a las 19:16, Francis Daly () escribió: > > On Sat, Jan 21, 2023 at 04:34:26PM -0600, Rick Gutierrez wrote: > > I'm pretty sure that this "include" line works, but... > Hi francis > > part of my nginx.conf > > > > map $geoip2_data_country_code $allowed_country { > >default

Re: Allow/Deny rules in Location block

Thanks Ian for the reply. I did it because the container was failing to start with the error below, will restrict that too. - > [error] 7#7: *1 connect() failed (111: Connection refused) while > connecting to upstream, client: 10.10.0.38, server: _, request: "GET > /api/saml-links HTTP/1.1", upstr

Re: Allow/Deny rules in Location block

Thanks Reinis for the reply, There are other locations like /auth, /auth/, /auth/admin, /auth/admin/ and few more which have the same rules. I am trying to restrict access to /auth and /auth/admin which are sensitive for public access. Do you think removing "=" can help in this case? On Mon, Jan