JoakimR Wrote: ------------------------------------------------------- > Whitout any configuretion it's imposible to do much rather than refer > you to nginx.org documentation > http://nginx.org/en/docs/http/ngx_http_ssl_module.html The configuration in the vhost file is: ssl on; ssl_certificate /etc/ssl/private/server.crt; ssl_certificate_key /etc/ssl/private/server.key;by nrahl - Nginx Mailing List - English
We have client certificates set up and working for desktop browsers, but when using the same certificates that work on the desktop browser from an iPad, we get a "400: The SSL certificate error" in the browser, and the following in the log: "18205#18205: *11 client SSL certificate verify error: (26:unsupported certificate purpose) while reading client request headers, client"by nrahl - Nginx Mailing List - English
I found soemthing that I think works, but it feels very hackish: location ~ ^/(+)/ { error_page 418 = @apache; #proxy pass recursive_error_pages on; if ($arg_nc = 1) { return 418; } try_files /cache/$1.html @apache; } Is this the best (only?) way to bypass a location based on query sting?by nrahl - Nginx Mailing List - English
> It would need testing, and it does depend on what is in the > "apache-pass" > file, but presuming that it does do "proxy_pass" and does not do > anything > that is invalid in an "if in location", then > > > location ~ ^/(+)/ { #Use cache if possible, then > proxy pass > > if ($arg_nocache = true) { >by nrahl - Nginx Mailing List - English
We'd like to bypass a location if a query string varaible is present. Is this an approriate place to use "if", and if so, how should it be done? If the URL is a forward slash, followed by anything, followed by a forward slash, it attempts to find a static html.gz file in the cache folder matching the url, and then passes it to apache. This is the desired behavior, except when the URL conby nrahl - Nginx Mailing List - English
Thanks, I got it working. My goal was to avoid repeating both the proxy config and the password blocks, but I was able to make them inlcudes to avoid a bunch of duplicate lines. Thanks again!by nrahl - Nginx Mailing List - English
> You have denied access by ip address here, so 403 is the expected > response, no? > > > You may have more success if you can describe what response you > expect, > and provide a complete (small) server{} configuration that > demonstrates > the unwanted behaviour that you see. > The expected response is a password prompt on all locations, unless the IPby nrahl - Nginx Mailing List - English
> Are you sure that the test url that you are requesting matches this > location? > > There may be more useful information in the debug log regarding what > is going wrong for you. > With debug logging on, I ahve confirmed it is matching the correct location. With: location ^~ /Public { satisfy any; allow all; auth_basic off; try_filesby nrahl - Nginx Mailing List - English
> location /Public { auth_basic off; } > This prevents the password prompt from appearing on /Public, but results in an immediate 403 Forbidden error on that location. I've also tried: location /Public { auth_basic off; allow all; } But adding "allow all" causes the password prompt to appear on that location again.by nrahl - Nginx Mailing List - English
I'm trying to deny access to all locations on the server, unless the user has a specific IP address or enteres a password. This part is working. I'm also trying to add an exception, where any path starting with /Public is allowed by anyone with no password. I've tried to override it in a location block, but this doesn't seem to have any effect. server { ... satisfy any; allowby nrahl - Nginx Mailing List - English
I created a default conf file: server { listen 80 default; listen 443 default; server_name ""; return 444; } and linked it in sites-enabled. The other server is declared with: server { listen 80; listen 443 ssl; server_name .mydomain.com; Accessing the https://xx.xx.xx.xx (the IP address) uses the mydomain.com host instead of using theby nrahl - Nginx Mailing List - English
> With wordpress MU setups, you need to manually set up the blog id > ( well, at least I have so far )... here's some extracts from one of > my > site configs: > > location ^~ /blogs.dir { Thanks for sharing your config. What version of WordPress are you running? Mine doesn't have a blogs.dir directory. I think they did away with that in 3.5. My WPMU setup was workingby nrahl - Nginx Mailing List - English
Ok, at this point I have removed everything from the config just to try and get the most basic thing working. This is the entire config now: location ^~ /wordpress/ { fastcgi_pass unix:/var/run/php5-fpm.sock; } location / { return 403; } That's all the location blocks. What happens: 1. Going to any page that does not start with /wordpress/ produces a 403. This is correctby nrahl - Nginx Mailing List - English
Side Note: It appears the forum is down.http://forum.nginx.org says, "The database connection failed. Please check your database configuration in include/db/config.php. If the configuration is okay, check if the database server is running." > That's not what ^~ means. The manual says, "If the longest matching prefix location has the "|^~|" modifier then regular eby nrahl - Nginx Mailing List - English
I'm trying to move a working Apache2 config to Nginx and failing miserably. The site has a main application, a custom CMS and a wordpress multi-site with a few blogs. The CMS rules are setup and working, but I can't get the wordpress rules to 1. Work and 2. Get executed ebcause the CMS rules are being too greedy. The structure is: / - root is the CMS else, not wordpress /*Anything*/ - Pass toby nrahl - Nginx Mailing List - English
I'm migrating an application from Apache2 to nginx and having trouble configuring my server. What it should do is: 1. If the requested URI is a real file or directory, serve it. 2. If not, and it is the root, /, execute the file Director.php in the web root using a fastcgi_pass. 3. If the URL has one segment, ie. "mydomain.com/SomeWhere/", then execute the file Director.php in theby nrahl - Migration from Other Servers
![]() |
![]() |
![]() |
![]() |
![]() |