Hi Maxim,
>
> You are trying to connect to an upstream server with an IPv6
> address, yet your system has no IPv6 addresses configured, so
> the connection attempt fails. This is not fatal, as nginx is able
> to switch to using other addresses of the same server, but
> probably a configura
Hello!
On Mon, Mar 01, 2021 at 11:35:47AM +0200, Señor J Onion wrote:
> I want to set up nginx as a forward proxy - much like Squid might work.
First of all, you probably already know it, but to clarify: nginx
is not a forward proxy. What you are trying to do is not
supported and entirely at
I want to set up nginx as a forward proxy - much like Squid might work.
This is my server block:
server {
listen 3128;
server_name localhost;
location / {
resolver 8.8.8.8;
proxy_pass http://$http_host$uri$is_args$args;
}
}
Hello!
On Mon, Jun 10, 2019 at 02:15:03PM +, Vivek Solanki wrote:
> I have setup a nginx server through which requests are forwarding to AWS ELB
> by nginx proxy_pass (configured on /etc/nginx/default.d/my.conf) on. Behind
> AWS ELB tomcat application running on instances. After performing
Hi Team,
I have setup a nginx server through which requests are forwarding to AWS ELB by
nginx proxy_pass (configured on /etc/nginx/default.d/my.conf) on. Behind AWS
ELB tomcat application running on instances. After performing load test
(15k-20k throughput) using Jmeter it is working fine, but
below upstream
error message (5XX errors).
--
2019/05/07 04:20:38 [error] 18168#0: *684822 no live upstreams while connectin
I tried appling the noperm flag on my test environment, but once I applied the
other fix of adding gid/uid to the cifs mount, the chmod() error went away. Now
I face a new error that happens infrequently which is rename() fails. I’m
guessing the real problem is that without a lot of additional c
On Sat, Jan 20, 2018 at 12:47:29PM +, Friscia, Michael wrote:
Hi there,
> 2018/01/20 07:37:44 [crit] 122598#122598: *91 chmod()
> "/etc/nginx/cache/nginx2/main/a5/d8/e0/72677057b97aef4eee8e619c49e0d8a5.13"
> failed (1: Operation not permitted) while reading upstream, client:
> 35.2
Ok, found it. It was a permission issue. I did not have the uid and gid in the
fstab, I set that the the www-data user that nginx is running as and the errors
went away. I’m just not sure I understand how it made the cache
files/directories in the first place. But clearly this is a problem when
As usual, try disabling selinux if it’s active. If that helps, investigate
audit log..
br,
Aziz.
> On 20 Jan 2018, at 15:47, Friscia, Michael wrote:
>
> I’m stumped and have exhausted pretty much every google search I could come
> up with on this. I have NGINX setup for caching. I’m using
I’m stumped and have exhausted pretty much every google search I could come up
with on this. I have NGINX setup for caching. I’m using Ubuntu 17.10 and Nginx
1.12.1. Everything appears to be working just fine by the error log is getting
filled with errors like this
2018/01/20 07:37:44 [crit] 12
11 matches
Mail list logo
