v2.1.0-rc.1

[ruslandoga]

Warning

The previous v2.1.0-rc.1 image had incorrect settings that disabled GA4 imports and CSV exports/imports.
Please re-pull the image if you don't see "Imports & Exports" section in site settings.

The highlights of this release candidate are:

• 🎉 Introduction of Community Edition [see below]
• ⬇️ GA4 import
• 🔁 CSV data export and import between self-hosted and cloud
• 🔐 TOTP for 2FA [docs]
• ✉️ New SMTP client [see below]
• 🔌 The new WordPress integration now works better thanks to the Plugin API
• 📚 Hosting documentation (now at plausible/community-edition) got an update and now includes a more thorough Google integration guide
• 📈 Sites page got a new look with spark charts
  

Introduction of Community Edition

As of version 2.1.0 this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these features. Read more here.

As part of this change, we are also rebranding the project. The new logos for CE and EE will be different so as to clarify which version is being referred to or used at any given time.

And finally as a contributor, you will have to sign a Contributor License Agreement (CLA) in order for your PRs to be considered for merging.

Upgrading to v2.1.0-rc.1

Important

This guide assumes you are using v2.0.0

Update config

Add a secret key for the new required TOTP_VAULT_KEY environment variable

_console

$ openssl rand -base64 32
aihU7k+GSBKbcVFuX9VEPyUhuwlKEomqA94/SQQ0NR4=

_{plausible-conf.env}

  BASE_URL=https://plausible.example.com
  SECRET_KEY_BASE=PkVcxRgQDfQyhPETlog3vvCrj5LdYFSv4ejPEJHJO+i/37w6RZfRjeVCpJayjUjJMfXsNurcv5upPhTRoD3KgQ==
+ TOTP_VAULT_KEY=aihU7k+GSBKbcVFuX9VEPyUhuwlKEomqA94/SQQ0NR4=

This new key is used to encrypt TOTP secrets at rest.

Update images

Update the images used for plausible and plausible_events_db

_{docker-compose.yml}

plausible:
- image: plausible/analytics:v2.0.0
+ image: ghcr.io/plausible/community-edition:v2.1.0-rc.1

plausible_events_db:
- image: clickhouse/clickhouse-server:22.6-alpine
+ image: clickhouse/clickhouse-server:23.3.7.5-alpine

and restart the containers

_console

$ cd hosting
$ docker compose stop plausible plausible_events_db
$ docker compose rm plausible plausible_events_db
$ docker compose up -d

This will boot up the new version of the app.

New SMTP client

If you were having problems with email delivery in v2.1.0-rc.0, you can switch to the new SMTP client by setting MAILER_ADAPTER to Bamboo.Mua. All the SMTP_* environment variables can stay the same.

_{plausible-conf.env}

  BASE_URL=https://plausible.example.com
  SECRET_KEY_BASE=PkVcxRgQDfQyhPETlog3vvCrj5LdYFSv4ejPEJHJO+i/37w6RZfRjeVCpJayjUjJMfXsNurcv5upPhTRoD3KgQ==
  TOTP_VAULT_KEY=aihU7k+GSBKbcVFuX9VEPyUhuwlKEomqA94/SQQ0NR4=
  SMTP_HOST_ADDR=smtp.gmail.com
  SMTP_HOST_PORT=587
  [email protected]
  SMTP_USER_PWD="wnqj fkbn jcwc byxk"
+ MAILER_ADAPTER=Bamboo.Mua

In addition, here's a short guide on using your Gmail account for email delivery.

Changelog

Following changes have been made since v2.0.0:

Added

• Hostname Allow List in Site Settings
• Pages Block List in Site Settings
• Add conversion_rate to Stats API Timeseries and on the main graph
• Add total_conversions and conversion_rate to visitors.csv in a goal-filtered CSV export
• Ability to display total conversions (with a goal filter) on the main graph
• Add conversion_rate to Stats API Timeseries and on the main graph
• Add time_on_page metric into the Stats API
• County Block List in Site Settings
• Query the views_per_visit metric based on imported data as well if possible
• Group operating_system_versions by operating_system in Stats API breakdown
• Add operating_system_versions.csv into the CSV export
• Display Total visitors, Conversions, and CR in the "Details" views of Countries, Regions and Cities (when filtering by a goal)
• Add conversion_rate to Regions and Cities reports (when filtering by a goal)
• Add the conversion_rate metric to Stats API Breakdown and Aggregate endpoints
• IP Block List in Site Settings
• Allow filtering with contains/matches operator for Sources, Browsers and Operating Systems.
• Allow filtering by multiple custom properties
• Wildcard and member filtering on the Stats API event:goal property
• Allow filtering with contains/matches operator for custom properties
• Add referrers.csv to CSV export
• Add a new Properties section in the dashboard to break down by custom properties
• Add custom_props.csv to CSV export (almost the same as the old prop_breakdown.csv, but has different column headers, and includes props for pageviews too, not only custom events)
• Add referrers.csv to CSV export
• Improve password validation in registration and password reset forms
• Adds Gravatar profile image to navbar
• Enforce email reverification on update
• Add Plugins API Tokens provisioning UI
• Add searching sites by domain in /sites view
• Add last 24h plots to /sites view
• Add site pinning to /sites view
• Add support for JSON logger, via LOG_FORMAT=json environment variable
• Add support for 2FA authentication
• Add 'browser_versions.csv' to CSV export
• Add CLICKHOUSE_MAX_BUFFER_SIZE_BYTES env var which defaults to 100000 (100KB)
• Add alternative SMTP adapter add Bamboo.Mua #3654
• Add EXTRA_CONFIG_PATH env var to specify extra Elixir config Allow importing extra config #3906
• Add restrictive robots.txt for self-hosted make robots.txt restrictive by default #3905
• Add Yesterday as an time range option in the dashboard

Removed

• Removed the nested custom event property breakdown UI when filtering by a goal in Goal Conversions
• Removed the prop_names returned in the Stats API event:goal breakdown response
• Removed the prop-breakdown.csv file from CSV export
• Deprecated CLICKHOUSE_MAX_BUFFER_SIZE
• Removed /app/init-admin.sh that was deprecated in v2.0.0 remove init-admin.sh #3903
• Remove DISABLE_AUTH deprecation warning remove DISABLE_AUTH deprecation warning #3904

Changed

• A visits entry_page and exit_page is only set and updated for pageviews, not custom events
• Limit the number of Goal Conversions shown on the dashboard and render a "Details" link when there are more entries to show
• Show Outbound Links / File Downloads / 404 Pages / Cloaked Links instead of Goal Conversions when filtering by the corresponding goal
• Require custom properties to be explicitly added from Site Settings > Custom Properties in order for them to show up on the dashboard
• GA/SC sections moved to new settings: Integrations
• Replace CLICKHOUSE_MAX_BUFFER_SIZE with CLICKHOUSE_MAX_BUFFER_SIZE_BYTES
• Validate metric isn't queried multiple times

Fixed

• Creating many sites no longer leads to cookie overflow
• Ignore sessions without pageviews for entry_page and exit_page breakdowns
• Using VersionedCollapsingMergeTree to store visit data to avoid rare race conditions that led to wrong visit data being shown
• Fix conversion_rate metric in a browser_versions breakdown
• Calculate conversion_rate percentage change in the same way like bounce_rate (subtraction instead of division)
• Calculate bounce_rate percentage change in the Stats API in the same way as it's done in the dashboard
• Stop returning custom events in goal breakdown with a pageview goal filter and vice versa
• Only return (none) values in custom property breakdown for the first page (pagination) of results
• Fixed weekly/monthly e-mail report rendering issues
• Fix broken interval selection in the all time view Fix the interval selection in the all time view #3110
• Fixed IPv6 problems in data migration add transport_opts to data migration #3179
• Fixed long URLs display in Outbound Link breakdown view
• Fixed Sentry reports for ingestion requests derive jason encoder for request #3182
• Fix breakdown pagination bug in the dashboard details view when filtering by goals
• Update bot detection (matomo 6.1.4, ua_inspector 3.4.0)
• Improved the Goal Settings page (search, autcompletion etc.)
• Log mailer errors log mailer errors #3336
• Allow custom event timeseries in stats API Allow custom event timeseries in stats API #3505
• Fixes for sites with UTF characters in domain Fix domains that start with UTF character #3560
• Fix crash when using special characters in filter Escape special regex characters #3634
• Fix automatic scrolling to the bottom on the dashboard if previously selected properties tab UX improvement: don't autofocus on Custom properties on dashboard #3872
• Allow running the container with arbitrary UID Dockerfile and co updates #2986
• Fix width=manual in embedded dashboards fix manual embed width #3910
• Fix URL escaping when pipes are used in UTM tags Fix escaping of source filters #3930

---

This discussion was created from the release v2.1.0-rc.1.

[Alexander01998]

If anyone else has problems with this version refusing to start, check if your docker-compose.yml still has this line from older versions:

command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh db init-admin && /entrypoint.sh run"

If so, you need to remove the && /entrypoint.sh db init-admin part, because that command no longer exists:

plausible:
    image: ghcr.io/plausible/community-edition:v2.1.0-rc.1
    restart: always
-   command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh db init-admin && /entrypoint.sh run"
+   command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"

This fixed my issue. Just posting it here in case anyone else runs into it.

[nsgoyat]

Somehow, SMTP isn't still not working for me. The SMTP Credentials are the same ones that used to work before Plausible 2.0. I upgraded to the new version and added a new adapter variable in the configuration, but the outgoing emails aren't working.

[ruslandoga]

How do I configure SMTPS on 465?

It can be done with a custom config as well:

import Config

config :plausible, Plausible.Mailer, protocol: :ssl

[nsgoyat]

I have created my-config.exs file inside /opt/plausible with the following content:

import Config

config :plausible, Plausible.Mailer, transport_opts: [versions: [:"tlsv1.2"]]

import Config

config :plausible, Plausible.Mailer, protocol: :ssl

This is what I added to docker-compose.yml:

Here is the last line of my plausible-conf.env

Should I go ahead and re-create the plausible containers?

[ruslandoga]

No, your configuration is a bit wrong. If you want to include both changes, you'd need to merge them like this:

import Config

config :plausible, Plausible.Mailer,
  transport_opts: [versions: [:"tlsv1.2"]],
  protocol: :ssl

[nsgoyat]

Thank you so much, mate. SMTP is finally working for my Plausible server :)

[ruslandoga]

For reference, the issue seems to be erlang/otp#6772, I'll read a bit more about it and maybe open another issue, since the problem is still present in otp-27-rc.3 (opened it erlang/otp#8470)

Minimal reproducible example:

iex> :ssl.connect(~c"eagle.mxlogin.com", 465, verify: :verify_none)
{:error,
 {:tls_alert,
  {:unexpected_message,
   ~c"TLS client: In state hello_middlebox_assert at ssl_gen_statem.erl:763 generated CLIENT ALERT: Fatal - Unexpected Message\n {unexpected_msg,{internal,{encrypted_extensions,\#{sni => {sni,[]}}}}}"}}}

Logs:

14:26:40.790 [warning] Description: ~c"Failed to assert middlebox server message"
     Reason: [missing: {:change_cipher_spec, 1}]

14:26:40.791 [notice] TLS :client: In state :hello_middlebox_assert at ssl_gen_statem.erl:763 generated CLIENT ALERT: Fatal - Unexpected Message
 - {:unexpected_msg, {:internal, {:encrypted_extensions, %{sni: {:sni, []}}}}}

[wheeleran]

update from v2.1.0-rc.1 not working for me, @ruslandoga. self-hosted community edition on a Synology NAS, Plausible container starts, but all i'm getting is a 502 error. it's "up," but it's not running... 'command' was right from rc.0, and clickhouse was on the right version already. checked with the latest version of the yaml file and DO see two new volumes under plausible_events_db? clickhouse-config and clickhouse-user-config? so it feels like there's a built in long term error in my docker-compose. rolled back to rc.0 to check and it runs, so i'm not sure what's actually wrong.

[ruslandoga]

👋 @wheeleran

We would need more info about the error to start fixing this :) Logs, reverse proxy logs, attempt to access the container locally bypassing the proxy and the result of that, etc.

[wheeleran]

i understand and appreciate that, but i've had to roll back to rc.0 immediately because i'm in the middle of an ad campaign and don't want to lose any data. i'm not very good with docker: can you give me a list of commands to print these logs to a remote local folder so that i can get this information to you as quickly as possible without faffing around?

[ruslandoga]

Sure, it would be something like this

$ cd hosting
$ docker compose logs
$ cat /var/log/nginx/access.log
$ cat /var/log/nginx/error.log
$ curl http://localhost:8000 -vvv

[chrisdeeming]

I had a bit of a hairy moment as I think I shut down my caddy container as well and was wondering why it wasn't working but got it up in the end.

Somehow managed to miss the RC version. Thanks @ruslandoga for pointing me in the right direction!

[olimortimer]

Ran the upgrade steps, and the containers look like they are running, but Plausible isn't working.

Running docker composer logs outputs a lot of the following;

plausible-1  | ERROR! Config provider Config.Reader failed with:
plausible-1  | ** (ArgumentError) incorrect padding
plausible-1  |     (elixir 1.16.0) lib/base.ex:735: Base.decode64base!/2
plausible-1  |     /app/releases/0.0.1/runtime.exs:163: (file)
plausible-1  |     (elixir 1.16.0) src/elixir.erl:405: :elixir.eval_external_handler/3
plausible-1  |     (stdlib 5.2) erl_eval.erl:750: :erl_eval.do_apply/7
plausible-1  |     (stdlib 5.2) erl_eval.erl:1026: :erl_eval.expr_list/7
plausible-1  |     (stdlib 5.2) erl_eval.erl:456: :erl_eval.expr/6
plausible-1  |     (stdlib 5.2) erl_eval.erl:539: :erl_eval.expr/6
plausible-1  |     (stdlib 5.2) erl_eval.erl:325: :erl_eval.expr/6
plausible-1  |
plausible-1  | Runtime terminating during boot ({#{message=><<"incorrect padding">>,'__struct__'=>'Elixir.ArgumentError','__exception__'=>true},[{'Elixir.Base','decode64base!',2,[{file,"lib/base.ex"},{line,735}]},{elixir_eval,'__FILE__',1,[{file,"/app/releases/0.0.1/runtime.exs"},{line,163}]},{elixir,eval_external_handler,3,[{file,"src/elixir.erl"},{line,405}]},{erl_eval,do_apply,7,[{file,"erl_eval.erl"},{line,750}]},{erl_eval,expr_list,7,[{file,"erl_eval.erl"},{line,1026}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,456}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,539}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,325}]}]})
plausible-1  |
plausible-1  | Crash dump is being written to: erl_crash.dump...ERROR! Config provider Config.Reader failed with:
plausible-1  | ** (ArgumentError) incorrect padding
plausible-1  |     (elixir 1.16.0) lib/base.ex:735: Base.decode64base!/2
plausible-1  |     /app/releases/0.0.1/runtime.exs:163: (file)
plausible-1  |     (elixir 1.16.0) src/elixir.erl:405: :elixir.eval_external_handler/3
plausible-1  |     (stdlib 5.2) erl_eval.erl:750: :erl_eval.do_apply/7
plausible-1  |     (stdlib 5.2) erl_eval.erl:1026: :erl_eval.expr_list/7
plausible-1  |     (stdlib 5.2) erl_eval.erl:456: :erl_eval.expr/6
plausible-1  |     (stdlib 5.2) erl_eval.erl:539: :erl_eval.expr/6
plausible-1  |     (stdlib 5.2) erl_eval.erl:325: :erl_eval.expr/6

The setup is out of the box, based on the instructions provided, so nothing customised etc.

curl http://localhost:8000 -vvv
* Host localhost:8000 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
*   Trying [::1]:8000...
* connect to ::1 port 8000 from ::1 port 59036 failed: Connection refused
*   Trying 127.0.0.1:8000...
* Connected to localhost (127.0.0.1) port 8000
> GET / HTTP/1.1
> Host: localhost:8000
> User-Agent: curl/8.5.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection
curl: (56) Recv failure: Connection reset by peer

[ruslandoga]

According to the error (invalid base64 padding), it seems like there might be a typo or something similar in your plausible-conf.env. The env vars to check are SECRET_KEY_BASE and TOTP_VAULT_KEY

[olimortimer]

That's what I originally thought, but the only change is TOTP_VAULT_KEY. I've recreated this a number of times, but still the same error, however I've just tried again and now it seems to be working.

[olimortimer]

Is there anything we need to do in 2.1.0-rc.1 for GA4 importing to work? GA3 importing was working in 2.0.0, but now seeing the following in 2.1.0-rc.1

We were unable to authenticate your Google Analytics account. Please check that you have granted us permission to 'See and download your Google Analytics data' and try again.

[olimortimer]

@ruslandoga the setup is out of the box, based on the instructions provided, so nothing customised etc, and no reverse proxy unless configured by default.

[ruslandoga]

Where do the log lines in #4084 (reply in thread) come from? Why do you use [::1] with curl, can you try using localhost? By instructions, do you mean https://github.com/plausible/community-edition/tree/v2.1.0?

[olimortimer]

The log lines are from /var/log/nginx/plausible.X.io.error.log

I'm using curl with [::1] as that's what's showing in the logs.

Yes, those instructions.

[ruslandoga]

Can you please share the config files for nginx?

[olimortimer]

Of course, thank you, appreciate the help. This is the first time I've properly used docker, so I'm sure I've screwed up somewhere.

/etc/nginx/sites-available/plausible.X.io.conf

server {
    listen       80;
    listen       [::]:80;
    server_name  plausible.X.io;

    access_log  /var/log/nginx/plausible.X.io.access.log;
    error_log   /var/log/nginx/plausible.X.io.error.log;

    location / {
      proxy_pass http://localhost:8000;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  }
}

I am now wondering if it's proxy_pass causing it, however I have since removed that, and restarted Nginx, but it's not even running on the server, so I'm even more confused.

× nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2024-05-15 18:58:04 BST; 46s ago
   Duration: 42min 32.447s
       Docs: man:nginx(8)
    Process: 13186 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
    Process: 13188 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
        CPU: 15ms

May 15 18:58:03 X.io nginx[13188]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
May 15 18:58:03 X.io nginx[13188]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
May 15 18:58:03 X.io nginx[13188]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
May 15 18:58:03 X.io nginx[13188]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
May 15 18:58:04 X.io nginx[13188]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
May 15 18:58:04 X.io nginx[13188]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
May 15 18:58:04 X.io nginx[13188]: nginx: [emerg] still could not bind()
May 15 18:58:04 X.io systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
May 15 18:58:04 X.io systemd[1]: nginx.service: Failed with result 'exit-code'.
May 15 18:58:04 X.io systemd[1]: Failed to start nginx.service - A high performance web server and a reverse proxy server.

Looks to be the reverse-proxy that's still listening.

grep -R listen *
README.md:Configures the IP address to bind the listen socket for the web server.
README.md:Configures the port to bind the listen socket for the web server.
reverse-proxy/nginx/plausible:	listen 80;
reverse-proxy/nginx/plausible:	listen [::]:80;

I've tried quite a few things, but I've exhausted my knowledge. I get Plausible working so I can collect and see stats, but then the same error is in the logs when I try and add a Goal etc, then I try and fix and bust it again!

[olimortimer]

Hi @ruslandoga

I ended up removing docker and nginx completely, and started over. As Plausible was working with nginx down, I removed that, and left it removed - I previously followed a guide on installing Plausible, and they included nginx (https://flaviocopes.com/how-to-self-host-plausible-analytics/). After just installing Docker, then following the install for v2.1.0, everything is now working - graphs showing on the homepage, Goals > Pageview working etc, so there must have been a conflict with nginx?

However, I'm still getting the below error when trying to connect Google Analytics, which I had working previously. The Google client id and secret has been added.

We were unable to authenticate your Google Analytics account. Please check that you have granted us permission to 'See and download your Google Analytics data' and try again.

As nginx on the Plausible docker is being used, I'm not sure how to access the nginx logs to see what errors are being thrown.

[ruslandoga]

👋 @olimortimer

Maybe you could give this guide a try https://github.com/plausible/community-edition/tree/v2.1.0#google-integration? :)

[olimortimer]

Yes, I've done that already, and it was working previously. "However, I'm still getting the below error when trying to connect Google Analytics, which I had working previously. The Google client id and secret has been added."

…

On Fri, 17 May 2024, 05:12 ruslandoga, ***@***.***> wrote: 👋 @olimortimer <https://github.com/olimortimer> Maybe you could give this guide a try https://github.com/plausible/community-edition/tree/v2.1.0#google-integration? :) — Reply to this email directly, view it on GitHub <#4084 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJCRY2IBVGDXWPSTVMGVBLZCV7RBAVCNFSM6AAAAABHMQZUL6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TINRVGI4TO> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ruslandoga]

Does it work if you downgrade to the version where it was working previously? If not, what have you tried to debug this?

[olimortimer]

No, I haven't downgraded since starting fresh, but it was working on 2.0.0 correctly. I've checked the docker logs, but nothing about it shows in there. I'm not sure how to access the nginx logs for the site on the Plausible container.

…

On Fri, 17 May 2024, 07:10 ruslandoga, ***@***.***> wrote: Does it work if you downgrade to the version where it was working previously? If not, what have you tried doing to debug this? — Reply to this email directly, view it on GitHub <#4084 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJCRY4UQ3XCYK32CDYUSSDZCWNOBAVCNFSM6AAAAABHMQZUL6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TINRWGE2TE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ruslandoga]

I meant that you you should try downgrading :)

[olimortimer]

I'm reluctant to downgrade again, as everything is now working on 2.1.0, except the GA import.

…

On Fri, 17 May 2024 at 07:29, ruslandoga ***@***.***> wrote: I meant that you you should try downgrading :) — Reply to this email directly, view it on GitHub <#4084 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJCRY5P4VATZHEY6E5LSX3ZCWPTXAVCNFSM6AAAAABHMQZUL6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TINRWGI4TI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ruslandoga]

What exactly do you want me to re-post?

[ruslandoga]

#4084 (reply in thread)?

[olimortimer]

Thank you, but I replied with the output of that, and we went a little further through, and on Jun 19 I posted the output of the oban_jobs table as requested. I believe that was everything requested?

[ruslandoga]

No :) You didn't post the output from running the job manually and I don't think you posted any traces.

[ruslandoga]

I think you might've missed my last request in #4084 (reply in thread).

[chrisdeeming]

Hey @ruslandoga

Sorry for the tag but since the update to 2.1.0 RC1 I am unable to use the /api/v1/sites endpoint - it is returning a 404.

This was working fine before the upgrade but now:

I did originally experience 401 issues because the API key didn't have the sites:provision: scope, but once that was resolved I was able to automate the creation of new sites.

Now it just returns a 404 as if the URL has changed.

Is this expected, a regression, or have I done something wrong somewhere?

[chrisdeeming]

Just seen this is intentional. Highly disappointing. Plausible is no longer viable for us.

[ruslandoga]

👋 @chrisdeeming

I don't see this change documented anywhere.

This change has been explained in the blog: https://plausible.io/blog/community-edition#a-stronger-moat-for-our-official-managed-hosting

[olimortimer]

Just seen this is intentional. Highly disappointing. Plausible is no longer viable for us.

So self-hosted Plausible no longer has an API? That's crazy!

[rmens]

It does have an API. Just not a site provisioning API. The stats API is working fine.

[olimortimer]

That's good to hear!

[ruslandoga]

👋

v2.1.0 has been released: #4125