Second user on selfhost instance cannot be owner of a website (needs a subscription)

[GoudronViande24]

I tried creating a second user and transferring ownership of a website. The message showing up when accepting says that it will need an active subscription, even though that's not something on the selfhosted version. I clicked accept anyway (it's a test website I don't care about it's data), and now the following is showing up instead of the stats:

[GoudronViande24]

Of course the manage my subscription is not working, it redirects to user's settings page which has nothing about subscriptions.

Is that a bug? Should I open an issue for this?

[GoudronViande24]

oh and when I add a new website with the second account, there is also the subscription message showing up:

[ruslandoga]

👋 @GoudronViande24

Can you please share your configuration? docker-compose.yml, how you deploy, env vars (with secrets redacted), etc.

[zenminimalist]

Would the ENV variable DISABLE_SUBSCRIPTION=true in the plausible server solve his issue?

[ruslandoga]

This env var has been removed for about two years: e873d79 Right now subscriptions are disabled by default.

All currently supported env vars (both documented and undocumented) can be found in https://github.com/plausible/analytics/blob/master/config/runtime.exs

[GoudronViande24]

Here are the configuration files:

docker-compose.yml

version: "3.3"
services:
#  mail:
#    image: bytemark/smtp
#    restart: always

  plausible_db:
    # supported versions are 12, 13, and 14
    image: postgres:14-alpine
    restart: always
    volumes:
      - ./db-data:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=[REDACTED]

  plausible_events_db:
    image: clickhouse/clickhouse-server:22.6-alpine
    restart: always
    volumes:
      - ./event-data:/var/lib/clickhouse
      - ./clickhouse/clickhouse-config.xml:/etc/clickhouse-server/config.d/logging.xml:ro
      - ./clickhouse/clickhouse-user-config.xml:/etc/clickhouse-server/users.d/logging.xml:ro
    ulimits:
      nofile:
        soft: 262144
        hard: 262144

  plausible:
    image: plausible/analytics:v2.0
    restart: always
    command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"
    depends_on:
      - plausible_db
      - plausible_events_db
#      - mail
    env_file:
      - plausible-conf.env

  tunnel:
    container_name: cloudflared-tunnel
    image: cloudflare/cloudflared
    restart: unless-stopped
    command: tunnel run
    environment:
      - TUNNEL_TOKEN=[REDACTED]

plausible-conf.env

BASE_URL=[REDACTED]
SECRET_KEY_BASE=[REDACTED]
MAILER_EMAIL=[REDACTED]
MAILER_NAME=[REDACTED]
SMTP_HOST_ADDR=[REDACTED]
SMTP_HOST_PORT=465
SMTP_USER_NAME=[REDACTED]
SMTP_USER_PWD=[REDACTED]
SMTP_HOST_SSL_ENABLED=true
SMTP_RETRIES=2
DISABLE_REGISTRATION=invite_only
MAXMIND_LICENSE_KEY=[REDACTED]
MAXMIND_EDITION=GeoLite2-City

@ruslandoga do you need something else?

Thanks in advance for the support!

[ruslandoga]

Thank you! I've been able to reproduce the issue. Here's a quickfix that manually sets trial_expiry_date for the new user to some distant date:

$ cd hosting
$ docker compose exec plausible_db psql -h localhost -U postgres

> \c plausible_db
-- ruslan says: I've transferred ownership to koolhazcker and that account didn't get trial_expiry_date set to "long distant future"
> select email, trial_expiry_date from users;
--            email            | trial_expiry_date
-- ----------------------------+-------------------
--  [email protected]       | 2122-08-10
--  [email protected]      |
(5 rows)
-- ruslan says: so I set it manually
> update users set trial_expiry_date = now() + interval '100y' where email = '[email protected]';
-- UPDATE 1
> select email, trial_expiry_date from users;
--            email            | trial_expiry_date
-- ----------------------------+-------------------
--  [email protected]       | 2122-08-10
--  [email protected]      | 2123-10-28

I'll open a PR with a proper fix today :) It's already been fixed in #3376 and that fix would be included in the next release.

[dominiwe]

Just want to leave a comment for anyone still running into this issue with a self hosted deployment.

First I built the docker image from the latest commit on the main branch with sudo docker build -t "plausible/analytics:$(git rev-parse HEAD)" . which includes commit e67850c that merges #3376. Then I adjusted the deployment to use this tag.

After that I did the change in the db as suggested by @ruslandoga. But the issue still persisted so I realized I had to unlock the sites like this:

-- you may not want to do this for all sites but I did
update sites set locked = false;

After that everything in our self hosted instance worked again.