couchbase 3 web admin redirecting to cluster view

[ch...@ochsnet.com]

I have a single node setup on a host with a private ip only, and I have nginx reverse proxying port 8091.  Not sure if that has anything to do with the issue I am having.

What's happening is that any action that would modify anything, be it deleting a document, changing setttings, anything, just redirects back to the cluster view.  Sometimes it gives me a generic error message but that's it.

I dug around in the log files but found nothing that looks interesting.

My java client is working fine, able to add/remove/update documents.  So I think it's web console specific, and I'm thinking it might be a security thing with the proxying I am doing.  That's the only thing that makes sense.  I'm not logged in as a read only user, I don't even have a read only user setup.

Chris

[ch...@ochsnet.com]

Hmm actually I did find this in the error log:

[stats:error,2014-09-16T5:41:35.205,ns...@192.168.150.216:<0.482.0>:stats_collector:handle_info:124]Exception in stats collector: {exit,

                                  {{badmatch,{error,closed}},

                                   {gen_server,call,

                                       ['ns_memcached-gamemachine',

                                        {stats,<<>>},

                                        180000]}},

                                  [{gen_server,call,3,

                                       [{file,"gen_server.erl"},{line,188}]},

                                   {ns_memcached,do_call,3,

                                       [{file,"src/ns_memcached.erl"},

                                        {line,1401}]},

                                   {stats_collector,grab_all_stats,1,

                                       [{file,"src/stats_collector.erl"},

                                        {line,84}]},

                                   {stats_collector,handle_info,2,

                                       [{file,"src/stats_collector.erl"},

                                        {line,116}]},

                                   {gen_server,handle_msg,5,

                                       [{file,"gen_server.erl"},{line,604}]},

                                   {proc_lib,init_p_do_apply,3,

                                       [{file,"proc_lib.erl"},{line,239}]}]}

[ns_server:error,2014-09-16T5:41:36.274,ns...@192.168.150.216:ns_doctor<0.312.0>:ns_doctor:update_status:229]The following buckets became not ready on node 'ns...@192.168.150.216': ["gamemachine"], those of them are active ["gamemachine"]

[ch...@ochsnet.com]

So looking in chrome dev tools I'm seeing POST requests hit urls with a just_validate=1 param, and returning a 401.  So it's doing some kind of extra authentication and failing.

Chris

On Monday, September 15, 2014 11:08:15 PM UTC-7, ch...@ochsnet.com wrote:

[Aliaksey Kandratsenka]

On Mon, Sep 15, 2014 at 11:47 PM, <ch...@ochsnet.com> wrote:

So looking in chrome dev tools I'm seeing POST requests hit urls with a just_validate=1 param, and returning a 401.  So it's doing some kind of extra authentication and failing.

I'd suggest this:

* disable nginx proxying and see if things work without it (they should)

and then assuming that it works without nginx:

* either leave it disabled (UI won't work with it anyways one you have more than 1 node due to details of how UI sessions work)

* or fix your nginx setup