DLNA + Docker + Let's Encrypt (not working)

I’m trying to set up DLNA on my Jellyfin server. With the following specs:
I run Jellyfin inside a Docker container, which runs on openmediavault4 on a RockPro64.

The Jellyfin is reachable over the internet via a Let’s Encrypt Reverse Proxy. I already found out that I should make a separate macvlan network to make DLNA work. Here are the relevant parts from my docker compose:

# Let's Encrypt
  letsencrypt:
container_name: letsencrypt
image: linuxserver/letsencrypt
restart: always
environment:
  - PUID=${PUID}
  - PGID=${PGID}
  - TZ=${TZ}
  - URL=${TLD}
  - SUBDOMAINS=${SUBS}
  - VALIDATION=${VAL}
  - EMAIL=${MAILADRES}
volumes:
  - ${APPDATA}/Letsencrypt:/config
networks:
  - jellyfin_net
  - nextcloud_net
ports:
  - 446:443
  - 82:80
cap_add:
  - NET_ADMIN

# Jellyfin
  jellyfin:
container_name: jellyfin
image: jellyfin/jellyfin
restart: always
environment:
  - PUID=${PUID}
  - PGID=${PGID}
  - TZ=${TZ}
volumes:
  - ${APPDATA}/Jellyfin:/config
  - ${APPDATA}/Jellyfin/cache:/cache
  - ${MEDIA}:/media
  - ${DOWNLOADS}:/downloads
  - ${UPLOADMAP}:/uploads
  - ${PERSOONLIJK}:/persoonlijk
ports:
  - 8096:8096
networks:
  jellyfin_net: {}
  jellyfin_macvlan:
    ipv4_address: 192.168.1.6

networks:
  nextcloud_net:
    driver: bridge
  jellyfin_net:
    driver: bridge
  jellyfin_macvlan:
    driver: macvlan
    driver_opts:
        parent: eth0
    ipam:
        config:
            - subnet: 192.168.1.1/16

This is the output of gssdp-discover, so as you can see, the macvlan trick seems to be working.

Using network interface wlp3s0
Scanning for all resources
Showing "available" messages
resource available
  USN:      uuid:55c3899bac844568b97a5d407fff2f19::upnp:rootdevice
  Location: http://192.168.1.6:8096/dlna/55c3899bac844568b97a5d407fff2f19/description.xml
resource available
  USN:      uuid:55c3899bac844568b97a5d407fff2f19
  Location: http://192.168.1.6:8096/dlna/55c3899bac844568b97a5d407fff2f19/description.xml
resource available
  USN:      uuid:55c3899bac844568b97a5d407fff2f19::urn:schemas-upnp-org:service:ConnectionManager:1
  Location: http://192.168.1.6:8096/dlna/55c3899bac844568b97a5d407fff2f19/description.xml
resource available
  USN:      uuid:55c3899bac844568b97a5d407fff2f19::urn:schemas-upnp-org:service:ContentDirectory:1
  Location: http://192.168.1.6:8096/dlna/55c3899bac844568b97a5d407fff2f19/description.xml
resource available
  USN:      uuid:55c3899bac844568b97a5d407fff2f19::urn:schemas-upnp-org:device:MediaServer:1
  Location: http://192.168.1.6:8096/dlna/55c3899bac844568b97a5d407fff2f19/description.xml
resource available

But there still is a problem, because the server is still not discovered by other devices. When I try to visit the url in the ‘available’ message: 192.168.1.6:8096/dlna/55c3899bac844568b97a5d407fff2f19/description.xml , the page is not loading, I get a connection time-out. When I replace 192.168.1.6:8096 for the internet address of the jellyfin server, I do get a XML file. So there seems to be a problem with the connection of the local address with the jellyfin webserver.

Any ideas?

Here are the references I used to get to this point:



dev.to/fredlab/make-docker-containers-available-both-on-your-local-network-with-macvlan-and-on-the-web-with-traefik-2hj1