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

Unabled to upload media - TypeError: RequestInit: duplex option is required when sending a body #106

Closed
daedric7 opened this issue Oct 21, 2023 · 9 comments
Assignees
Labels
bug Something isn't working no-issue-activity work-in-progress Stale exempt

Comments

@daedric7
Copy link

Everytime i try to upload missing media i get:

emulatorjs  | node:internal/deps/undici/undici:11576
emulatorjs  |     Error.captureStackTrace(err, this);
emulatorjs  |           ^
emulatorjs  | 
emulatorjs  | TypeError: RequestInit: duplex option is required when sending a body.
emulatorjs  |     at Object.fetch (node:internal/deps/undici/undici:11576:11)
emulatorjs  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
emulatorjs  | 
emulatorjs  | Node.js v18.17.1

How can i debug this ?

@j0nnymoe
Copy link
Member

Post information on how you've deployed the container.

@daedric7
Copy link
Author

Post information on how you've deployed the container.

Apologies, it was indeed a crappy issue.

EmulatorJS deployed via docker-compose.yaml:

services:
  emulatorjs:
    image: lscr.io/linuxserver/emulatorjs:latest
    container_name: emulatorjs
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - SUBFOLDER=/ #optional
    volumes:
      - ./config:/config
      - /share/emulatorjs/data:/data
      - /share/roms:/share/roms
    ports:
      - 3000:3000
      - 3080:80
      #- 4001:4001 #optional
    restart: unless-stopped

I've checked permissions on dirs, i've set everything to 777 to isolate a permission issue.

This is the file i'm trying to send, but a video causes the same problem:

image (2)

@j0nnymoe
Copy link
Member

Post your full path for your /config mount

@daedric7
Copy link
Author

Post your full path for your /config mount

That's exactly as it is in docker-compose.yaml, but if you need to know the full path (on the host):

/opt/emulatorjs/config/

@Jahn16
Copy link

Jahn16 commented Oct 28, 2023

@daedric7 As a workaround you can upload the image to /data/<emulator>/<game>/logos with the same name as the ROM file but ending with a image file extension like .png

@LinuxServer-CI
Copy link

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@thelamer thelamer self-assigned this Jan 8, 2024
@thelamer thelamer added work-in-progress Stale exempt bug Something isn't working labels Jan 8, 2024
@thelamer
Copy link
Member

thelamer commented Jan 8, 2024

I was still using js-ipfs while updating the ipfs in the container constantly I need to refactor everything to a new lib that is not depreciated this might take a bit.

@thelamer
Copy link
Member

I pinned back nodejs in the container to head 16.x it the uploading media is functional with the latest image.

@thelamer
Copy link
Member

Closing as this is now fixed, let me know if anything is not working on your end, and if you do improve a bunch of art the custom metadata tab in the backend provides the metadata I need to add it to everyone's installs.

@LinuxServer-CI LinuxServer-CI moved this from Non-Docker Issues to Done in Issue & PR Tracker Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working no-issue-activity work-in-progress Stale exempt
Projects
Archived in project
Development

No branches or pull requests

5 participants