Getting error on accessing admin panel of Firefly 6.1.11

[jameswill]

Support guidelines

• I've read the support guidelines

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem
• ... it's definitely a Firefly III issue, not me

Description

HI,

I have installed Firefly 6.1.11 on my test server with PHP 8.3 and Mysql 5.7. I am able to installed it successfully using the documentation.

I am getting "500 Internal Server Error" error on accessing admin panel ie. http://domain.com/[[sub-dir]]/public/register
On turning on the debug I found the following error.

Uncaught Illuminate\Foundation\ViteManifestNotFoundException: Vite manifest not found at: [[path]]/public/build/manifest.json in [[path]]/vendor/laravel/framework/src/Illuminate/Foundation/Vite.php:728

Also attaching here the log file
ff3-fpm-fcgi-2024-03-20.log

I feel the the installer is failing to generate /public/build/* files and hence causing the issue.

Debug information

[2024-03-20 12:50:44] production.ERROR: Exception is: {"class":"Illuminate\View\ViewException","errorMessage":"Vite manifest not found at: [[path]]/public/build/manifest.json (View: [[path]]/resources/views/auth/register.blade.php)","time":"Wed, 20 Mar 2024 12:50:44 +0100","file":"[[path]]/vendor/laravel/framework/src/Illuminate/Foundation/Vite.php","line":728,"code":0,"version":"6.1.11","url":"http://[[domain]]/manual/firefly6111/public/register","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0","json":true,"method":"GET","post":""}
[2024-03-20 12:50:44] production.WARNING: [Bcc] Could not email or log the error. Please validate your email settings, use the .env.example file as a guide.
[2024-03-20 12:50:44] production.ERROR: Vite manifest not found at: [[path]]/public/build/manifest.json

Expected behaviour

Login page should load without any error.

Steps to reproduce

1. php composer create-project grumpydictator/firefly-iii --no-dev --prefer-dist firefly-iii 6.1.11
2. Fill up DB details in .env
3. php artisan firefly-iii:upgrade-database
4. php artisan firefly-iii:correct-database
5. php artisan firefly-iii:report-integrity
6. php artisan passport:keys
7. Visit http://domain/sub-dir/public and getting the error.

Additional info

No response

[JC5]

https://docs.firefly-iii.org/how-to/firefly-iii/upgrade/self-managed/#created-using-composer-create-project

Using create-project is no longer supported for the installation or upgrade of Firefly III. You'll have to follow the new instructions.

[jameswill]

I thought that is for upgrade. Do we need to follow in install as well ?

[JC5]

Yes, see https://docs.firefly-iii.org/how-to/firefly-iii/installation/self-managed/

[jameswill]

HI.

Thank you..It resolves the issue.. However few images are failing to load on admin panel.

What could be the issue for that ?

[JC5]

Those icons are part of a font, and it should be included in the zip download.

If you open the developer console (ctrl-shift-i) and reload the page, do you see any 404's?

[Maxco10]

@JC5 i

The same issue on login page.

The .htaccess file is the same of repository.

Ideas?

[JC5]

Alright, thanks. I see a 403 error. So the file exists, you're just not allowed to access it. I don't think I can fix that.

[Maxco10]

@JC5
i saw it but the file and folder 's permissions are ok and I am using the htaccess of project.
What permissions do you have for that folder?

[JC5]

Are you using Apache as a web server?

This is from the demo:

[Maxco10]

Yes, Apache. I suppose the htaccess is the same on repository, yes?

[JC5]

Indeed. The demo site unpacks the zipfile.

Could be that the extension is blocked by another part of your configuration?

[jameswill]

HI,

Getting the same issue on firefly 6.1.12 version as well.

The fonts are present in /public/build/assets directory.

Also I noticed that script is trying to load the fonts from the root url and I have made an installation in a sub directory and hence it's failing to load. Is the sub directory installation discontinued ?

[jameswill]

Is there any mentioning about it on the installation documentation ?

[Maxco10]

no, but it is an issue after this release.

[JC5]

I'll pick it up over the weekend, thanks for letting me know!

[Maxco10]

@JC5 @jameswill

I fixed the "bug" on /public/assets/app-de4f62e0.css file. The issue is on path for the font. To have a clean UI before next release we can change the file "app-de4f62e0.css" removing "build/assets/" from path.

For the next release:
We need to remove "build/assets/" from "src" when we generate this app-css file.

[JC5]

The next (development) release will point to ./fa-solid-900-9fc85f3a.woff2.