Self-managed installation served in subdirectory

[walderich]

Support guidelines

• I've read the support guidelines
• My request is not listed as a very good idea, but unfortunately...
• I've used the search and this has not been requested before.

Description

I am trying to install Firefly III on a machine with an existing webserver. Therefore I want to serve it under a subdirectory. My issue is the that I can't find information about the nginx configuration. Actually the FAQs contain a small snippet which looked promising, so I tried that with small adaptions to match my configuration (the replaced parts are commented-out and replaced in the follow-up line):

location ^~ /budget {
  alias [...]/firefly-iii/public;
  try_files $uri $uri/ @budget;

  location ~* \.php(?:$|/) {
    #include snippets/fastcgi-php.conf;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $request_filename;
    fastcgi_param modHeadersAvailable true; #Avoid sending the security headers twice
    #fastcgi_pass unix:/run/php/php8.3-fpm.sock;
    fastcgi_pass unix:/var/run/php-fpm.sock;
  }
}
location @budget {
  rewrite ^/budget/(.*)$ /budget/index.php/$1 last;
}

Unfortunately this only gives me a 403 when navigating to /budget.

When I navigate to /budget/index.php I am redirected to /budget/index.php/login, which is correct, I guess? But that page gives my a custom 500 page. The browser debugging tools show that neither the CSS nor the logo image can be loaded due to the fact that they are searched in the /public directory instead of the custom subdirectory. Additionally the following error message is shown:

Could not access the database: SQLSTATE[HY000]: General error: 1 no such table: users (Connection: sqlite...

I verified that the database file firefly is correctly located in the root directory. I can access it with the sqlite3 command-line tool, list its tables and also query the users table stated in the error.

To get any further, I also tried to move the database file to the public subdirectory. This in fact routes me from /budget/index.php to /public/index.php/register. I guess that this is indeed correct, but now I get a 404 error due to leaving the subdirectory.

Solution

It would be great to have an updated FAQ answer that correctly routes the requests.

What are alternatives?

No response

Additional context

No response

[JC5]

Hey, thanks for starting a discussion.

I'm seeing a lot of questions. What have you found in previous discussions about this? Both subjects have been discussed a lot.

[walderich]

Actually, I have to admit that I didn't find many useful discussion about these topics. Most of the subdirectory topics are addressing Apache and self-managed discussions seem to be very rare. Thus I feel quite lost here.

[JC5]

Sorry about that. I know very little about it myself.