Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Autoupdates to new php version for application #37

Open
1 task done
The-MEO opened this issue Jan 19, 2025 · 2 comments
Open
1 task done

[BUG] Autoupdates to new php version for application #37

The-MEO opened this issue Jan 19, 2025 · 2 comments

Comments

@The-MEO
Copy link

The-MEO commented Jan 19, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Upload of files result in Error=500 and no files are stored on the server.

Expected Behavior

Return code 200 and store files in the storage.

Steps To Reproduce

  1. use latest version 3.8.0
  2. login
  3. start inspecting network traffic in your browser
  4. try to upload file

Steps To fix

Environment

Distributor ID: Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:        12
Codename:       bookworm

Docker version 27.5.0, build a187fa5
Docker Compose version v2.32.4

CPU architecture

x86-64

Docker creation

xbackbone:
    container_name: xbackbone
    image: lscr.io/linuxserver/xbackbone:latest
    environment:
      - "PGID=998"
      - "PUID=1001"
      - "TZ=Europe/Berlin"
    volumes:
      - ./xbackbone/config:/config
    expose:
      - 80
      - 443
    restart: unless-stopped
    networks:
      - "infranet"

Container logs

nothing visible.
Interesting logs are stored inside the container.
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@aptalca
Copy link
Member

aptalca commented Jan 19, 2025

According the the PR description, the issue is present in php 7.1+. There is no way we can pin php to a version older than that. Even if we could, we wouldn't anyway since 7.1 went eol more than 5 years ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Issues
Development

No branches or pull requests

2 participants