CouchBase ui kicks me out frequently even while running queries

Hi
I am using CouchBase 6.6 and it just keeps kicking me out frequently no matter what I am doing, forcing me to log in again and start all over.
Is there anyone who can help?
@matthew.groves I am not sure if it will help, but here is an image of what my network shows when it kicks me out


Thanks

Hi @Elad_Ghuy,

Do you mean that you keep getting logged out of the Couchbase web UI?

  • How frequently?
  • Which browser are you using?
  • Where is the server installed (local machine, docker, Azure, etc)
  • Have you tried in a different browser?
  • Are you running any browser extensions?

Exactly.

  • How frequently? no rules, it can be 1 min from the login up to a few hours. but most of the time it is very quick
  • Which browser are you using? Chrome
  • Where is the server installed (local machine, docker, Azure, etc) VM on Azure
  • Have you tried in a different browser? Yes. explorer/edge - same behavior
  • Are you running any browser extensions? very few

Thanks

If by chance you’re trying to do this with a loadbalancer over multiple nodes in Azure, note that Couchbase Server doesn’t currently allow for this. You’ll appear to be kicked out if your request goes to another node. This is covered in MB-31756.

The workaround for now is to just expose one of the UI/management ports (typically, 8091).

Also, maybe check out cbshell, an Open Source effort that lets you run UI locally, just using the services directly. It’s not quite the same, but addresses the problem a bit differently.

Only one node… and no load balancer …

Any ideas?
Any info that I can add to help shed some light on this weird issue…

Can you take a look at and/or share the logs link in the UI? It sounds like something underneath might be crashing repeatedly. Couchbase will automatically restart its internal processes so that’s why it might seem like you’re getting kicked out…

If that doesn’t show what we need, then we can gather more logs and look deeper

The HTTP 401 error suggests that the server logged you out, for some reason. Do you know how much load was on the server when that happened?