Hi!

I think the problem is the localhost address in the nginx.conf. It resolves a 
IPv6 address and the other log said that you use the client 127.0.0.1. What did 
you configure as bind_address in the CouchDB Configuration?

Does it work for you when you edit the nginx configuration from 
http://localhost:5984 to http://127.0.0.1:5984


server {
    #simple proxy setup
    location / {
        proxy_pass http://127.0.0.1:5984;
        proxy_redirect off;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
    #continuous replication
    location ~ ^/(.*)/_changes {
        proxy_pass http://127.0.0.1:5984;
        proxy_redirect off;
        proxy_buffering off;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}



Regards,

Michael


Am 30.10.18 um 09:30 schrieb Sinan Gabel:

@max the user www-data should access to the nginx .conf files, not the
couchdb database files.

On Tue, 30 Oct 2018 at 05:18, Anik Das 
<maila...@gmail.com><mailto:maila...@gmail.com> wrote:



Can you provide which OS and version of OS are you using?

Recently I’ve faced similar issues with RHEL 6.

On Mon, 29 Oct, 2018 at 10:11 PM, max 
<maxima...@gmail.com><mailto:maxima...@gmail.com> wrote:



In my nginx.conf (enclosed in my previous mail) there is "user


www-data;".


Do you mean this user is supposed to get read access to all my CouchDB
database files?

Le lun. 29 oct. 2018 à 16:57, Sinan Gabel 
<sinan.ga...@gmail.com><mailto:sinan.ga...@gmail.com> a


écrit


:



There should normally be a .conf file at:

/etc/nginx/nginx.conf

, it has http {...} and more parameters set:

In that file ensure that the user set, also has access to the file with


the


couchdb location parameters.



On Mon, 29 Oct 2018 at 11:44, max 
<maxima...@gmail.com><mailto:maxima...@gmail.com> wrote:



Hi,

I noticed strange error in my Nginx logs:

2018/10/29 09:36:57 [error] 1163#1163: *1057266 connect() failed


(111:


Connection refused) while connecting to upstream, client: 127.0.0.1,
server: , request: "GET /database1/Object_VKGSJ-kxWEakirO1VDlA9w


HTTP/1.1",


upstream: "http://


[::1]:5984/database1/Object_VKGSJ-kxWEakirO1VDlA9w",


host: "127.0.0.1:80"

I'm using nginx as reverse-proxy with this simple configuration
(documented at
https://cwiki.apache.org/confluence/display/COUCHDB/Nginx+as+a+proxy


):



#max body size (attachment upload) : disable check
client_max_body_size 0;

server {
    #simple proxy setup
    location / {
        proxy_pass http://localhost:5984;
        proxy_redirect off;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
    #continuous replication
    location ~ ^/(.*)/_changes {
        proxy_pass http://localhost:5984;
        proxy_redirect off;
        proxy_buffering off;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

I removed all other Nginx conf files in order to test it but this


issue


keeps popping in my log. Please find enclosed my nginx.conf if needed
(which seems to be the default nginx conf).

Anyone know where it could comes from?

Thanks.









--
Sent from Gmail for iPhone






Reply via email to