Logs are not showing up, despite files clearly have content

[Kovah]

When opening the log viewer on my production site, all files I can see in the file system are listed, with their correct sizes shown too.

When I click on any file, no logs are actually shown.

I don't use the viewer often, so I don't know when this broke, but it worked before.

How can I debug this and find out what's wrong?

Configuration is basically the standard one with tweaks to the app name and url, as well as enabling unknown log types.

---

• Log Viewer 3.15.4
• Laravel 12
• PHP 8.4

[arukompas]

Hey @Kovah,

Let me guess, it's behind a load-balancer now? 😄

If so, please see the discussion (and answer) here:
#425 (comment)

[Kovah]

Unfortunately, no. It's the same server delivering the page and responding to any API calls. Server sit's behind a proxy, but every other Laravel feature works flawlessly. I hope that the problem with different file hashes does not also apply to single-server setups?

I have taken a look into the network requests. This is an example of what's returned after I click on a file:

{
    "file": {
        "type": {
            "value": "laravel",
            "name": "Laravel"
        },
        "identifier": "30708300-laravel-2025-04-03.log",
        "sub_folder": "\/app\/storage\/logs",
        "sub_folder_identifier": "e5bc2829",
        "path": "--redacted--\/storage\/logs\/laravel-2025-04-03.log",
        "name": "laravel-2025-04-03.log",
        "size": 8614,
        "size_in_mb": 0.008214950561523438,
        "size_formatted": "8.41 KB",
        "download_url": "--REDACTED--\/system-logs\/api\/files\/30708300-laravel-2025-04-03.log\/download",
        "earliest_timestamp": 1743663500,
        "latest_timestamp": 1743663500,
        "can_download": true,
        "can_delete": true,
        "loading": false,
        "selected_for_deletion": false
    },
    "levelCounts": [],
    "logs": [],
    "columns": [
        {
            "label": "Severity",
            "data_path": "level"
        },
        {
            "label": "Datetime",
            "data_path": "datetime"
        },
        {
            "label": "Env",
            "data_path": "extra.environment"
        },
        {
            "label": "Message",
            "data_path": "message"
        }
    ],
    "pagination": {
        "current_page": 1,
        "first_page_url": "\/?page=1",
        "from": null,
        "last_page": 1,
        "last_page_url": "\/?page=1",
        "links": [
            {
                "url": null,
                "label": "Previous",
                "active": false
            },
            {
                "url": "\/?page=1",
                "label": "1",
                "active": true
            },
            {
                "url": null,
                "label": "Next",
                "active": false
            }
        ],
        "links_short": [
            {
                "url": null,
                "label": "Previous",
                "active": false
            },
            {
                "url": "\/?page=1",
                "label": "1",
                "active": true
            },
            {
                "url": null,
                "label": "Next",
                "active": false
            }
        ],
        "next_page_url": null,
        "path": "\/",
        "per_page": 25,
        "prev_page_url": null,
        "to": null,
        "total": 0
    },
    "expandAutomatically": false,
    "cacheRecentlyCleared": false,
    "hasMoreResults": false,
    "percentScanned": 100,
    "performance": {
        "memoryUsage": "92.50 MB",
        "requestTime": "26ms",
        "version": "v3.15.4"
    }
}

Not much helpful stuff in there. When I try to open the download URL, I get a 403 error. It's so weird that Log Viewer knows the files and returns them in the sidebar, but once it tries to load that log it's no longer there. 🤔

[JustRutger]

I've got the same exact problem. It knows the files and returns them in the sidebar but just like you said, once it tries to load that log it's no longer there.

[arukompas]

hey @Kovah @JustRutger , there's also a possibility that Log Viewer does not recognise any Laravel logs inside file. It needs to match a specific regex, and if the log format has been changed to something non-standard, it might not recognise it.

Could you please share the actual log file that you're trying to load?

[Kovah]

I am using the Monolog JSON formatter so that I can parse it with Pomtail more easily.

If Log Viewer can't parse a log message, it could fall back to plain text instead of showing nothing.

[arukompas]

I am using the Monolog JSON formatter so that I can parse it with Pomtail more easily.

If Log Viewer can't parse a log message, it could fall back to plain text instead of showing nothing.

Ok, so that's why. It's no longer the default Laravel log format and it does not recognise it.

Falling back to plain text is something to consider and implement in the future, but there's a few edge cases to be considered first.

What you can do it extend the default Laravel log format and update the regex used and anything else needed.

https://log-viewer.opcodes.io/docs/3.x/log-types/custom