sergix44 / XBackBone

A lightweight file manager with full ShareX support and more
https://xbackbone.app
GNU Affero General Public License v3.0
993 stars 81 forks source link

CSS loading fails when using #514

Closed Crown0815 closed 1 year ago

Crown0815 commented 1 year ago

System Info

Describe the bug Using vagrant and the provided docker image leads to an instance that does not load any css.

In the nginx error.log file there are two access errors for the css files

2023/01/20 13:12:47 [alert] 239#239: *9 sendfile() failed (22: Invalid argument) while sending response to client, client: 10.0.2.2, server: _, request: "GET /static/bootstrap/css/bootstrap.min.css?1674216767 HTTP/1.1", host: "127.0.0.1:4567", referrer: "http://127.0.0.1:4567/install/"
2023/01/20 13:12:47 [alert] 238#238: *14 sendfile() failed (22: Invalid argument) while sending response to client, client: 10.0.2.2, server: _, request: "GET /static/bootstrap/js/bootstrap.bundle.min.js?1674216767 HTTP/1.1", host: "127.0.0.1:4567", referrer: "http://127.0.0.1:4567/install/"

Unfortunately, I am not familiar with PHP or nginx; therefore, I am unable to determine what the issue is. The user access (PUID:1000 and PGID:1000) is configured to the main user (i.e., vagrant).

To Reproduce

  1. Install vagrant and the vagrant docker-compose plugin.
  2. Create a folder with the aforementioned Vagrantfile, docker-compose.yml file, and an empty folder called config.
  3. Start vagrant by calling vagrant up from the created folder
  4. Enter the virtual machine using vagrant ssh, navigate to the /vagrant folder and call docker compose up
  5. Go to 127.0.0.1:4567 in your browser
  6. The page is only HTML without CSS and the error message can be seen in config\log\nginx\error.log

Expected behavior No error message and properly styled HTML

Screenshots image

Logs access.log error.log

Crown0815 commented 1 year ago

It seems to be an issue with the shared vagrant folder. Sorry for bothering you guys ;-)