Skip to content
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

Failed to load resource: the server responded with a status of 500 () #118

Open
niqwithq opened this issue Mar 22, 2024 · 0 comments
Open

Comments

@niqwithq
Copy link

Hi,

I started having issues with next-plausible after I updated to next-13.5.6.

After npm run dev already gave me an error for next.config.js, I updated next-plausible to 3.11.2 according to #104.

The build error disappeared but Plausible still doesn't show me any requests.

Here is what the browser console says for my production site:
Failed to load resource: the server responded with a status of 500 () (in Google Chrome)
Loading failed for <script> with source .../script.outbound-links.js (in Firefox)

next-config.js (Has been working until I updated to next-13.5.6)

/** @type {import('next').NextConfig} */
const { withPlausibleProxy } = require('next-plausible');
const nextConfig = {
};
   
module.exports = withPlausibleProxy()(nextConfig);

_app.js (has been working until I updated to next-13.5.6)

import '../styles/global.css';
import PlausibleProvider from 'next-plausible';
import {ubuntu, neuton, norican} from '../src/utils/fonts';
import environmentVariables from "../components/environment-variables";

export default function App({ Component, pageProps }) {
    const plausibleDomain = environmentVariables.plausibleDomain;
    return (
        <PlausibleProvider domain={plausibleDomain} trackOutboundLinks="true">
        <div className={`${ubuntu.variable} ${neuton.variable} ${norican.variable}`}>
        <Component {...pageProps} />
        </div>
        </PlausibleProvider>
    )
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant