Closed jokob-sk closed 12 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
FYI downgraded to linuxserver/filezilla:3.59.0-r0-ls81
> this one works
Remove the /config mount temporarily, you will lose your settings, but it looks like the app does not have permissions to create the pulseaudio pid for running audio. I know audio on a filezilla container does not make a ton of sense, but these base images start a series of default services to accommodate a full desktop environment. From there I am not 100% I don't have Synology hardware, but I know they do some super weird stuff with their permission layout. A 777 chmod might be your only choice there, but again not sure.
Can you please test the latest image and let me know if this is still occurring.
Even when removing the config mapping:
version: "3"
services:
filezilla:
container_name: filezilla
# image: linuxserver/filezilla:3.59.0-r0-ls81
image: linuxserver/filezilla:latest
network_mode: "bridge"
restart: always
ports:
- "3774:3000" # host:container
- "3773:3389" # host:container
- "3775:3785" # host:container
- "3779:3789" # host:container
volumes:
- ${BACKUP_LOCATION}/x_local/soft/favicons/filezilla/favicon.ico:/gclient/public/favicon.ico
- ${BACKUP_LOCATION}/x_local/soft/favicons/filezilla/ms-icon-70x70.png:/gclient/public/icon.png
- ${PLEX_LOCATION}:/mnt/Plex
# - ${APP_DATA_LOCATION}/filezilla/config:/config
# - ${APP_DATA_LOCATION}/filezilla/data:/data
Same error on latest image:
filezilla |
filezilla | Error: Access denied
filezilla | at /kclient/node_modules/pulseaudio2/lib/pulse.js:133:21
filezilla | at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
filezilla | Emitted 'error' event on Context instance at:
filezilla | at /kclient/node_modules/pulseaudio2/lib/pulse.js:135:22
filezilla | at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
filezilla |
filezilla | Node.js v18.14.2
filezilla | node:events:491
filezilla | throw er; // Unhandled 'error' event
filezilla | ^
filezilla |
filezilla | Error: Access denied
filezilla | at /kclient/node_modules/pulseaudio2/lib/pulse.js:133:21
filezilla | at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
filezilla | Emitted 'error' event on Context instance at:
filezilla | at /kclient/node_modules/pulseaudio2/lib/pulse.js:135:22
filezilla | at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
filezilla |
filezilla | Node.js v18.14.2
filezilla | node:events:491
filezilla | throw er; // Unhandled 'error' event
filezilla | ^
filezilla |
filezilla | Error: Access denied
filezilla | at /kclient/node_modules/pulseaudio2/lib/pulse.js:133:21
filezilla | at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
filezilla | Emitted 'error' event on Context instance at:
That is my bad I should have confirmed the rebuilds, forgot to set this to the latest release building now: https://github.com/linuxserver/kclient/releases/tag/0.3.5
Thanks, let me know if you want me to try to pull the latest image and give it another go.
Cheers for the hard work!
Ok built and pushed lets see if this is squashed.
this one works if I:
1) Right click
2) Open xterm
3) Launch filezilla
Otherwise I get a blank black screen
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.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
Getting a BAD gateway 502 error
Expected Behavior
No response
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation