v2.1.0-rc.1 #4084
Replies: 12 comments 48 replies
-
|
If anyone else has problems with this version refusing to start, check if your 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 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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
It can be done with a custom config as well: import Config
config :plausible, Plausible.Mailer, protocol: :ssl |
Beta Was this translation helpful? Give feedback.
-
|
I have created my-config.exs file inside /opt/plausible with the following content: 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? |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much, mate. SMTP is finally working for my Plausible server :) |
Beta Was this translation helpful? Give feedback.
-
|
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: |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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! |
Beta Was this translation helpful? Give feedback.
-
|
Ran the upgrade steps, and the containers look like they are running, but Plausible isn't working. Running The setup is out of the box, based on the instructions provided, so nothing customised etc. |
Beta Was this translation helpful? Give feedback.
-
|
According to the error (invalid base64 padding), it seems like there might be a typo or something similar in your |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
@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. |
Beta Was this translation helpful? Give feedback.
-
|
Where do the log lines in #4084 (reply in thread) come from? Why do you use |
Beta Was this translation helpful? Give feedback.
-
|
The log lines are from I'm using curl with Yes, those instructions. |
Beta Was this translation helpful? Give feedback.
-
|
Can you please share the config files for nginx? |
Beta Was this translation helpful? Give feedback.
-
|
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.
I am now wondering if it's Looks to be the reverse-proxy that's still listening. 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! |
Beta Was this translation helpful? Give feedback.
-
|
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. 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. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe you could give this guide a try https://github.com/plausible/community-edition/tree/v2.1.0#google-integration? :) |
Beta Was this translation helpful? Give feedback.
-
|
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Does it work if you downgrade to the version where it was working previously? If not, what have you tried doing to debug this? |
Beta Was this translation helpful? Give feedback.
-
|
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I meant that you you should try downgrading :) |
Beta Was this translation helpful? Give feedback.
-
|
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Logged to where? How do I access these log files? |
Beta Was this translation helpful? Give feedback.
-
|
The frustrating thing is that Google Search Console integrates fine, but the GA4 import goes through the login etc successfully, then when it gets back to Plausible it shows a floating error; I've disabled and renabled APis on Google...basically undoing and redoing the full Google integration, but still only Search not GA. |
Beta Was this translation helpful? Give feedback.
-
To stdout, which Docker captures and makes available with |
Beta Was this translation helpful? Give feedback.
-
Have you been through this step?
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, I've been through all the steps multiple times. The next step after that screenshot is when it goes back to Plausible, and that's when I get the floating error message. Google Search Console is connected fine, GA is not. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @ruslandoga Sorry for the tag but since the update to 2.1.0 RC1 I am unable to use the This was working fine before the upgrade but now: 
I did originally experience 401 issues because the API key didn't have the Now it just returns a 404 as if the URL has changed. Is this expected, a regression, or have I done something wrong somewhere? |
Beta Was this translation helpful? Give feedback.
-
|
Actually my understanding of what is going wrong here is not correct. If I try to access curl But my API calls which were previously working are now generating 404 errors. Is this error code now hiding something that might have previously had a clearer error? Or have the expected parameters now changed somehow? |
Beta Was this translation helpful? Give feedback.
-
|
FWIW I've checked and triple checked: I cannot currently seem to use any API endpoints as documented here: |
Beta Was this translation helpful? Give feedback.
-
|
Wait a second... I've just looked back on some commits. It seems the Phoenix router configuration is gating the API stuff conditionally and is now exclusively only built for Enterprise Edition? Is that correct? While I potentially understand why you would do this, I don't see this change documented anywhere. That seems like a big thing to introduce without warning existing users first. |
Beta Was this translation helpful? Give feedback.
-
|
Just seen this is intentional. Highly disappointing. Plausible is no longer viable for us. |
Beta Was this translation helpful? Give feedback.
-
This change has been explained in the blog: https://plausible.io/blog/community-edition#a-stronger-moat-for-our-official-managed-hosting |
Beta Was this translation helpful? Give feedback.
-
|
👋 v2.1.0 has been released: #4125 |
Beta Was this translation helpful? Give feedback.
-
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
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_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_dbdocker-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 v2.1.0-rc.0, you can switch 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 #3905Removed
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-rc.1.
Beta Was this translation helpful? Give feedback.
All reactions