Mystery to me. Working fine here on my Synology.
Are you sure you don't have any Firewall rules enabled?
Control Panel > Security > Firewall
Try enabling debug for the static file server so it logs to the container log
environment:
- DEBUG=true
static-file-server:
image: halverneus/static-file-server:latest
container_name: static-file-server
dns_search: ${DOMAIN}
ports:
- ${HOST_SFS_PORT}:8080
environment:
- DEBUG=true
- FOLDER=${FOLDER}
volumes:
- ${HOST_DIR}/olivetin/data:${FOLDER}
restart: unless-stopped
Not sure what this means, but here is the output of the SFS log.
Using the following configuration:
cors: false
debug: true
folder: /web
host: ""
port: 8080
allow-index: true
show-listing: true
tls-cert: ""
tls-key: ""
tls-min-vers: ""
url-prefix: ""
referrers: []
access-key: ""
What does it log when you try to access it and get the 403 error?
2025/01/01 18:37:21 REQ from '192.168.176.1:35544': GET HTTP/1.1 192.168.0.11:8088/ -> /web/
Edit: Sorry, here is a request fro the actual m3u file.
2025/01/01 18:39:19 REQ from '192.168.176.1:37364': GET HTTP/1.1 192.168.0.11:8088/192.168.0.11-8089/YTlivestreams.m3u -> /web/192.168.0.11-8089/YTlivestreams.m3u
I don't know what the issue is. I have to assume the static file server is giving you the 403 error.
You could verify that using the developer tools network inspector in your browser when you try to access it.
Going to move this conversation to a new topic.
Here's something to try.
I found running docker containers on a Synology causes permission issues, unless you select this shared folder /volume1/docker for persistent docker container data.
In your OliveTin for Channels Portainer stack environment variables, change HOST_DIR=/volume1/data to HOST_DIR=/volume1/docker and see if that fixes it.
I changed the stack env to HOST_DIR=/volume1/docker but I knew the stack would fail to deploy because none of my olivetin stuff exists in that path. So I copied the entire /volume1/data/olivetin directory over to /volume1/docker/olivetin.
Success! I can now see the m3u in the browser.
Now I have to see if I need to adjust the env variables for the other stacks that have put stuff in the /volume1/data path. Maybe it makes no difference to the other stacks but I'm going to need to check that out. I remember having a bunch of trouble deploying Stream Link Manager and maybe this persistent docker container data issue was causing problems.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.