Login redirects to Registration

[realulim]

Hi all,

I've installed the CE on Kubernetes with the supplied Helm chart and configured an ingress. I can access the Plausible Base URL, but all it shows is the user registration page. If I click on "login" (or enter the /login URL manually), I get a 302 and are redirected to /registration.

I did provision for an admin account and would like to login as admin - not register a user. What could be the issue here?

I have even disabled registration in the values.yml file by putting disableRegistration: true # Restricts registration of new users.

Seems like I don't grasp some basic concept :)

[idca6390]

same problem here

[ruslandoga]

👋 @realulim

AFAIK there is no way to provision admin accounts through env variables anymore. It used to exist in older versions of Plausible but has been removed due to extra maintenance burden.

[realulim]

Not sure I understand that argument. I think precisely the way to reduce maintenance burden is automization via infrastructure as code. Or is Plausible not meant to be used on-premise?

[georgebuilds]

You ever figure this one out?

[realulim]

No, the functionality has been removed. I suppose that Plausible wants to promote their cloud offering and discourage people from running a production workload on premises. So I have switched to another tool.

[apata]

@georgebuilds
Just to clarify so you could make an informed decision on whether Plausible CE works for you or not:

The CE checks whether a user exists

analytics/lib/plausible_release.ex

Line 18 in c11d47a

not (_has_users? = Repo.exists?(Plausible.Auth.User))

If no users exists, it redirects the client to the registration page. The reason it happens is because if there is no user, there's nothing to log in with.

analytics/lib/plausible_web/router.ex

Line 13 in c11d47a

on_ee(do: nil, else: plug(PlausibleWeb.FirstLaunchPlug, redirect_to: "/register"))

Once you create a user, you can login with it, and you will be able to create or invite more users (depending on the CE configuration DISABLE_REGISTRATION).

@realulim I understand that you've switched to another tool, but if you don't mind, I'd like to understand what went wrong. When you said

I did provision for an admin account and would like to login as admin

how exactly did you do that?

[realulim]

@apata I did provision for an admin account in the values.yml file. I might have been looking at older documentation that still had the keywords to use for that. So when I was posting here I was under the impression I had provisioned for an admin account, but then was informed that the functionality has been removed. So I suppose there weren't actually any accounts configured.

[apata]

Thanks for clarifying, @realulim! I think it's a good lesson about deprecating features. For a popular CE config option, we should keep something like this

analytics/config/runtime.exs

Line 486 in c11d47a

DATABASE_SOCKET_DIR is deprecated, please use DATABASE_URL instead:

Also, I guess the Helm chart could have specified a particular CE version that it's tested with, then it would have still run.

[apata]

Just to have this 100% cleared up, Login redirecting to Registration until the first CE user is created is intentional. Otherwise there's nothing to login with. The solution is to create the user in the Registration flow.

The confusion came from a deprecated config option to automatically create the first user: it didn't alert loudly enough that it's deprecated and doesn't work any more.