-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Events are sent to the wrong domain #124
Comments
I was able to make it work with my self-hosted plausible instance Can you try <PlausibleProvider domain={process.env.DOMAIN}
customDomain="https://analytics.placeholder.com" selfHosted={true} /> |
Thank you for your help, unfortunately this still doesn't work. What does your process.env.DOMAIN look like? |
I have it hardcoded to my website's DNS which also matches with plausible's website dns EDIT: I have domain without |
Thank you for your help. It still seems like requests are not being sent out. I'm really not sure what I'm doing wrong
module.exports = withPlausibleProxy({
customDomain: process.env.PLAUSIBLE_CUSTOM_DOMAIN, // https://analytics.example.com
})(nextConfig);
<head>
<PlausibleProvider
domain={process.env.PLAUSIBLE_DOMAIN} // example.com
customDomain={process.env.PLAUSIBLE_CUSTOM_DOMAIN} // https://analytics.example.com
selfHosted={true}
/> |
are u sure your env variables are properly exposed/set? I did exactly the same but with hardcoded variables and it worked. |
First of all, thank you for your library! Unfortunately, I can't get it to work :(
I have my site hosted at
placeholder.com
, and my Plausible instance running (selfhosted) atanalytics.placeholder.com
Unfortunately, the library tries to access the
script.js
file atplaceholder.com
, resulting in a 404, and I can't seem to change this.Here is my
next.config.js
:And here is my
layout.tsx
:What am I doing wrong? Thank you!
The text was updated successfully, but these errors were encountered: