The route log-viewer/api/folders could not be found

[entoniperez]

From my local machine, I get this error when I try to get remote production log:

The project on production is in a subdomain in a shared hosting. And, if I try my website link https://subdomain.mydomain.com/log-viewer it returns a 404 | NOT FOUND Laravel view. But it works locally...

I'm missing something?

[arukompas]

hey @entoniperez , your first mission is to figure out why the https://subdomain.mydomain.com/log-viewer route is not working. Perhaps there's some misconfiguration on the subdomain or shared hosting side. I don't have experience with shared hosting providers, so I can't consult on that.

Try seeing if other routes of your app (not just the home page, but other pages too) work as expected, because I sense this might be an issue on the whole site, not just Log Viewer.

Let me know what you find.

[entoniperez]

Other routes works as expected... it's really strange. I was thinking that maybe I'm missing something about authorizing access to Log Viewer, but if I didn't change anything after installation, then on production should works as in local, right? Thanks for your time.

[arukompas]

@entoniperez could it be that your routes were cached in production? If they were cached before you installed Log Viewer and never re-cached again, that might explain it.

Run php artisan route:cache in production.

[entoniperez]

I've tried it calling this url through a route in web.php file:

Route::get('route-clear-cache', function () {
    Artisan::call('route:clear');
    Artisan::call('route:cache');
    return "Routes has been cleared and cached again.";
});

Same result for the url /log-viewer: 404.

[christoferd]

Suddenly having the same issue on production server.
It worked after I deleted the file: /config/log-viewer.php

[arukompas]

@christoferd did you at some point upgrade from an older Log Viewer version? I wonder if the config changes were clashing and something got messed up. Or maybe you had defined a different path for the log viewer? I.e. instead of /log-viewer you defined a different path to access it?

[christoferd]

@arukompas Not sure, but it's possible that I was missing something in the config, sometimes I run composer update.