Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

cverster's avatar

Laravel Nova trends not working on Prod

I have Laravel Nova installed locally and on my production server. I've created a trend metric for one of my models, and it works fine locally, and gives me a trend like this with my test data:

Populated trend

But, when I push this code to a remote server, the same trend returns this, though there is relevant data in the database:

Trend not populated

I've checked the response I get on my remote server when trying to call the information for this trend in Nova, and have seen the response is empty, as follows:

value: {value: false, trend: [], prefix: null, suffix: null, suffixInflection: true, format: null}
format: null
prefix: null
suffix: null
suffixInflection: true
trend: []
value: false

Which is strange, because the Nova API call to the actual resource works fine:

{label: "User Interactions", resources: [,…], prev_page_url: null,…}
label: "User Interactions"
next_page_url: "https://my_domain/nova-api/user-interactions?page=2"
per_page: 25
per_page_options: [25, 50, 100]
polling: false
pollingInterval: 15000
prev_page_url: null
resources: [,…]
showPollingToggle: false
softDeletes: false
sortable: true
total: 39

I don't really know where to start, but here is my Nginx config, as I'm thinking that is something that could be different between the two?

server {
        listen 80 default_server;
        listen [::]:80 default_server;

        root /path/to/app/public;

        # Add index.php to the list if you are using PHP
        index index.php index.html index.htm;

        charset utf-8;

        server_name my_domain;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ /index.php?$query_string;
        }

        # pass PHP scripts to FastCGI server
        #
        location ~ \.php$ {
                include snippets/fastcgi-php.conf;
        #
        #       # With php-fpm (or other unix sockets):
                fastcgi_pass unix:/var/run/php/php8.1-fpm.sock;
        #       fastcgi_index index.php;
        #       # With php-cgi (or other tcp sockets):
        #       fastcgi_pass 127.0.0.1:9000;
        }

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        location ~ /\.ht {
                deny all;
        }

Does someone have an idea of why I'm getting this strange behaviour?

0 likes
0 replies

Please or to participate in this conversation.