v2.1.0 #4125
Replies: 12 comments 46 replies
-
|
First of all. Thanks for version 2.1 and the whole team who make it possible. 🎉🔥 I'm not sure if it's directly related to the version, but on a server with Ubuntu 22.04.4 LTS and Plesk 18.x I ran into an 502 NGINX error:
However, this can be fixed with the following additional NGINX configuration:
|
Beta Was this translation helpful? Give feedback.
-
|
Basically the same problem for me. I was getting 502 after the upgrade, adding the line you suggested to the nginx.conf fixed things. |
Beta Was this translation helpful? Give feedback.
-
|
Successfully upgraded from v2.1.0-rc.1 to v2.1.0. |
Beta Was this translation helpful? Give feedback.
-
|
Same here. From v2.0.0-rc.0 to v2.1.0., I just had to add To my nginx config. Otherwise it was returning websocket error and the spark charts were not loading. |
Beta Was this translation helpful? Give feedback.
-
|
After updating from v2.0.0, I am getting only 403 error when trying to login. I did follow the update process documented above. Same thing happened when I was tryin rc.1 earlier. |
Beta Was this translation helpful? Give feedback.
-
|
Same when I try to reset the password (/password/request-reset). |
Beta Was this translation helpful? Give feedback.
-
|
👋 @hudus There is some ongoing discussion in #4126 It would be great if you could participate to help us find out what's causing this! |
Beta Was this translation helpful? Give feedback.
-
|
@ruslandoga Thank you. The problem was BASE_URL and websocket proxy settings in nginx. I always duplicate the server and try dry run for the update, before updating production setup. That means the test server runs on a different hostname. It wasn't a problem with previous versions. Update on production went smooth. No 403s. But I had to adjust Nginx config for the websockets. Might be worth updating the instructions to mention this. |
Beta Was this translation helpful? Give feedback.
-
|
is postgresql version 16 supported, or does it remain on 14? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, version 16 is supported :) |
Beta Was this translation helpful? Give feedback.
-
|
I lost all my previously imported Google Analytics data after upgrading from 2.0. |
Beta Was this translation helpful? Give feedback.
-
|
@bblanchon hi! Yes. We forgot to add the migration to populate You'd need to run it manually for now: $ cd hosting
$ docker compose exec plausible bin/plausible remoteiex> Plausible.DataMigration.SiteImports.run(dry_run?: true)
#==> check output, does it make sense? if it does
iex> Plausible.DataMigration.SiteImports.run(dry_run?: false) |
Beta Was this translation helpful? Give feedback.
-
|
Fix: #4155 |
Beta Was this translation helpful? Give feedback.
-
|
It worked! Thanks!!! |
Beta Was this translation helpful? Give feedback.
-
|
Worked for me too |
Beta Was this translation helpful? Give feedback.
-
|
v2.1.1 now performs this migration automatically. |
Beta Was this translation helpful? Give feedback.
-
|
Hi I can't get this new mail client to work: no email is sent when using invitation or password reset. This is my configuration : MAILER_ADAPTER=Bamboo.Mua
[email protected]
SMTP_HOST_ADDR=ssl0.ovh.net
SMTP_HOST_PORT=587
[email protected]
SMTP_USER_PWD=xxxxxxxxxHowever, I receive emails with this command : {:ok, _delivered_email} =
Plausible.Mailer.deliver_now(
Bamboo.Email.new_email(
# pick one of your own mailboxes
to: "[email protected]",
from: PlausibleWeb.Email.mailer_email_from(),
subject: "how are you?",
text_body: "I'm fine",
html_body: "I'm <i>fine</i>"
)
) |
Beta Was this translation helpful? Give feedback.
-
|
Please describe your setup in more detail. I've never used Portainer so I might not be able to help much. Can you please try and reproduce the issue with the example Docker Compose installation from https://github.com/plausible/community-edition? |
Beta Was this translation helpful? Give feedback.
-
|
Portainer does indeed allow the setup & configuration of Docker containers, but for Plausible, I do not use it for the installation, and I do use the git you specified. In my case, it is just used to quickly view the logs of each Plausible container (in addition to the other commands I specified). |
Beta Was this translation helpful? Give feedback.
-
|
For your information, I noticed that emails are NOT sent if some of the |
Beta Was this translation helpful? Give feedback.
-
PlausibleWeb.Email and you can also search for mailer.deliver or mailer.send
There is only bytecode in the Plausible container image :) However, it's possible to compile and redefine whole modules by copy-pasting their definition in IEx. $ cd hosting
$ docker compose exec plausible bin/plausible remoteiex> defmodule PlausibleWeb.Email do
def a, do: :b
endIt's not the optimal way to debug this, though. I would suggest either setting up your dev env or using tracing. |
Beta Was this translation helpful? Give feedback.
-
Depends on your mailing server, I guess. I use Gmail and this emails gets delivered: Plausible.Mailer.deliver_now(
Bamboo.Email.new_email(
to: "[email protected]",
from: PlausibleWeb.Email.mailer_email_from(),
html_body: "I'm <i>fine</i>"
)
) |
Beta Was this translation helpful? Give feedback.
-
|
Hello, thanks for releasing 2.1.0. However, I've lost all of the Custom Properties and associated data I had previously setup when upgrading from 2.0. Settings for [website] > Custom Properties > No properties configured for this site. |
Beta Was this translation helpful? Give feedback.
-
|
We can also confirm that this happened to us. We had to recreate them manually |
Beta Was this translation helpful? Give feedback.
-
|
can confirm this also happened. |
Beta Was this translation helpful? Give feedback.
-
|
Me too. All my custom properties are dynamic (created by javascript). Also the button is not working. |
Beta Was this translation helpful? Give feedback.
-
|
This line from the changelog might be related:
PR: #3242
It's unlikely any data had been lost. But you might need to add your properties explicitly now. |
Beta Was this translation helpful? Give feedback.
-
Correct, it doesn't seem as though data was lost. After manually re-adding the custom properties again I could filter by them on the site's dashboard. |
Beta Was this translation helpful? Give feedback.
-
|
Rolled back to 2.0.0, too much problem with Goals and Custom Properties for me EDIT : site settings is no more working after downgrade
|
Beta Was this translation helpful? Give feedback.
-
|
👋 v2.1.1 has bee released with some bug fixes. |
Beta Was this translation helpful? Give feedback.
-
|
You can try disabling middlebox_comp_mode and it should work with the new adapter in v2.1.1:
my_config.exs import Config
config :plausible, Plausible.Mailer,
ssl: [middlebox_comp_mode: false]
plausible:
image: ghcr.io/plausible/community-edition:v2.1.1
+ volumes:
+ - ./my_config.exs:/app/my_config.exs
[email protected]
MAILER_NAME=Plausible Analytics
SMTP_HOST_ADDR=email-smtp.eu-central-1.amazonaws.com
SMTP_HOST_PORT=587
SMTP_USER_NAME=username
SMTP_USER_PWD=password
MAILER_ADAPTER=Bamboo.Mua
CRON_ENABLED=true
+ EXTRA_CONFIG_PATH=/app/my_config.exs |
Beta Was this translation helpful? Give feedback.
-
|
Is there any way to set this config in the docker-compose file itself? I usually try to have all my env vars there. And am I right in thinking this is specifically for the Bamboo.Mua adapter, and it's worth trying again without it? |
Beta Was this translation helpful? Give feedback.
-
|
yes, yes, no :) |
Beta Was this translation helpful? Give feedback.
-
|
@ruslandoga thanks for the steps to fix this issue. My config:
# **************************************
# PLAUSIBLE SERVICE
# **************************************
plausible:
image: ghcr.io/plausible/community-edition:v2.1.1
container_name: plausible_plausible
hostname: plausible
restart: always
volumes:
- ./config/my-config.exs:/app/my-config.exs:ro
command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"
depends_on:
- plausible_db
- plausible_events_db
ports:
- 127.0.0.1:8000:8000
env_file:
- plausible-conf.env
The
This is the error I'm getting: |
Beta Was this translation helpful? Give feedback.
-
|
Replied in #4149 (reply in thread) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ruslandoga,
For these changes, how is plausible handling existing contributions that have been provided without CLA, while under the AGPLv3? Somewhat related to previous old discussion #992. |
Beta Was this translation helpful? Give feedback.
-
|
I'll ask a core team member how it was handled on the call next week. |
Beta Was this translation helpful? Give feedback.
-
|
@ssddanbrown Hey 👋 I had to manually go through all the existing contributions and get the authors to sign a CLA retroactively via email. Our lawyer advised we only needed to do this for contributions that would be considered 'significant' which is a hard line to draw. As a rule I considered anything over 10 lines to actual product code (not docs, tests) as significant. |
Beta Was this translation helpful? Give feedback.
-
|
@ukutaht Thanks for confirming your approach. Did you gain consent from all without much trouble? Or was it a challenge? I'm curious on this since I've seen various start-ups reference plausible, and your older blog post post regarding the AGPLv3, for their licensing approach, but I've often felt they thought the AGPLv3 offered more author-focused protection than it actually provided. I feel that others may follow your lead an approach on this change, so transparency in regard to requirements and challenges (if any) would provide an useful example case to help avoid others skipping or ignoring (purposefully or inadvertently) the requirements of the license they chose if they choose to switch up their licensing too. By the way, thanks for the commitment to keep an open offering, and good job on putting the open offering under its own distinct CE name to avoid conflation between open and non-open offerings, I often see this as an issue with open-core offerings. Lastly, just a minor thing, In your latest messaging around the CE version I see a lot of mention of “free as in beer” which I thought is a little odd. Since it's under the AGPL, it's still free in both beer and speech. Specifically solely stating it was “free as in beer” made me think it's somehow not "free as in speech", which as far as I can tell it still is? |
Beta Was this translation helpful? Give feedback.
-
|
Hey, many thanks for this awesome update!
|
Beta Was this translation helpful? Give feedback.
-
|
It's the It only needs to be performed when upgrading from v1 to v2 :) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot for your quick reply! |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I have this error when migrating from v2.0. to v2.1.0 Does this ring a bell ? What files would you like to see ? |
Beta Was this translation helpful? Give feedback.
-
Please search for this value in
The value itself seems like an injection attack attempt ... for an Oracle database? The fix is to update that value to |
Beta Was this translation helpful? Give feedback.
-
|
You are absolutely right about the injection attack. Thanks for your accurate answer. There was about 20 "[email protected]*" in my users table, one had an email such as "[email protected]'//and//DBMS_PIPE.RECEIVE_MESSAGE('t',0)='t" among many other [email protected] in the users table. I removed all the [email protected] because I saw online it was a spam address. Only one legitimate user had a "light" theme, I didn't touch it though. It now works perfectly. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the follow-up. I'll email them to let them know we use PostgreSQL. Eh.
|
Beta Was this translation helpful? Give feedback.
-
The highlights of this release are:
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
Important
This guide assumes you are using v2.0.0 and have already run the data migration.
Update config
Add a secret key for the new required
TOTP_VAULT_KEYenvironment variableconsole
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
plausibleandplausible_events_dband remove/entrypoint.sh db init-adminfrom yourplausible.commanddocker-compose.yml
and restart the containers
console
This will boot up the new version of the app.
New SMTP client
If you were having problems with email delivery in the previous versions you can try switching to the new SMTP client by setting
MAILER_ADAPTERtoBamboo.Mua. All theSMTP_*environment variables can stay the same.plausible-conf.env
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
conversion_rateto Stats API Timeseries and on the main graphtotal_conversionsandconversion_ratetovisitors.csvin a goal-filtered CSV exportconversion_rateto Stats API Timeseries and on the main graphtime_on_pagemetric into the Stats APIviews_per_visitmetric based on imported data as well if possibleoperating_system_versionsbyoperating_systemin Stats API breakdownoperating_system_versions.csvinto the CSV exportTotal visitors,Conversions, andCRin the "Details" views of Countries, Regions and Cities (when filtering by a goal)conversion_rateto Regions and Cities reports (when filtering by a goal)conversion_ratemetric to Stats API Breakdown and Aggregate endpointscontains/matchesoperator for Sources, Browsers and Operating Systems.event:goalpropertycontains/matchesoperator for custom propertiesreferrers.csvto CSV exportcustom_props.csvto CSV export (almost the same as the oldprop_breakdown.csv, but has different column headers, and includes props for pageviews too, not only custom events)referrers.csvto CSV exportCLICKHOUSE_MAX_BUFFER_SIZE_BYTESenv var which defaults to100000(100KB)EXTRA_CONFIG_PATHenv var to specify extra Elixir config Allow importing extra config #3906robots.txtfor self-hosted make robots.txt restrictive by default #3905DATA_DIRenv var for exports/imports add DATA_DIR #4100Removed
prop_namesreturned in the Stats APIevent:goalbreakdown responseprop-breakdown.csvfile from CSV exportCLICKHOUSE_MAX_BUFFER_SIZE/app/init-admin.shthat was deprecated in v2.0.0 remove init-admin.sh #3903DISABLE_AUTHdeprecation warning remove DISABLE_AUTH deprecation warning #3904Changed
entry_pageandexit_pageis only set and updated for pageviews, not custom eventsCLICKHOUSE_MAX_BUFFER_SIZEwithCLICKHOUSE_MAX_BUFFER_SIZE_BYTESFixed
entry_pageandexit_pagebreakdownsVersionedCollapsingMergeTreeto store visit data to avoid rare race conditions that led to wrong visit data being shownconversion_ratemetric in abrowser_versionsbreakdownconversion_ratepercentage change in the same way likebounce_rate(subtraction instead of division)bounce_ratepercentage change in the Stats API in the same way as it's done in the dashboard(none)values in custom property breakdown for the first page (pagination) of resultswidth=manualin embedded dashboards fix manual embed width #3910This discussion was created from the release v2.1.0.
Beta Was this translation helpful? Give feedback.
All reactions