NPM reverse proxy, Cloudflare, Docker Compose help!

[sunnythe14]

This?

https://developers.cloudflare.com/dns/ma...addresses/

Also check if your router supports DDNS for Cloudflare.  Freshtomato, my router's firmware, supports Cloudflare's API for updating the IP.

Solved!
Was able to use this nifty little container: https://github.com/oznu/docker-cloudflare-ddns

Thank you, again!

[Zhaytoshi]

Hello i have a similar problem. can you share to me what did you do to make it work ?

I have installed the NPM together with the jellyfin using container, also setup the cloud-flare together with my domain
but the problem i can't connect my domain to JF in the NPM its not working.

Below is my container file

Code:

version: '3.5'
services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    user: 1000:1000
    network_mode: 'host'
    volumes:
      - ./config:/config
      - ./cache:/cache
      - /media/zhaytoshi/HDD/AllVideos:/media
    restart: 'unless-stopped'
    environment:
      - JELLYFIN_PublishedServerUrl=http://192.168.1.126
    extra_hosts:
      - "host.docker.internal:host-gateway"

  nginxproxymanager:
    image: 'jc21/nginx-proxy-manager:latest'
    container_name: nginxproxymanager
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./nginx/data:/data
      - ./nginx/letsencrypt:/etc/letsencrypt


  jellyfin-vue:
    image: ghcr.io/jellyfin/jellyfin-vue:unstable
    ports:
      - "8645:80"
    restart: unless-stopped

Below is my NPM setups and Audit Logs 
   

Code:

{
  "id": 2,
  "created_on": "2024-04-11 20:57:43",
  "modified_on": "2024-04-12 05:28:49",
  "owner_user_id": 1,
  "domain_names": [
    "jellyfin.home     .online"
  ],
  "forward_host": "192.168.1.126",
  "forward_port": 8096,
  "access_list_id": 0,
  "certificate_id": 3,
  "ssl_forced": true,
  "caching_enabled": false,
  "block_exploits": false,
  "advanced_config": "",
  "meta": {
    "letsencrypt_agree": false,
    "dns_challenge": false
  },
  "allow_websocket_upgrade": false,
  "http2_support": true,
  "forward_scheme": "http",
  "enabled": 1,
  "locations": [],
  "hsts_enabled": false,
  "hsts_subdomains": false
}

[TheDreadPirate]

Does Nginx have any way to resolve "jellyfin" to an IP address? Try swapping out "jellyfin" in the Forward Hostname field for an IP address (192.168.1.126?).

Also, enable web sockets and enable block common exploits. The latter is obviously good to have enabled, and web sockets is required by Jellyfin to work properly. But that isn't the reason you aren't able to connect.

[Zhaytoshi]

Thank you for the reply. I Did change it now to 192.168.1.126 still the same. But the nginx.home.domain.com its working and its using the SSL Cert very well. The only problem now is the JF I've been trying to make it work few days now still nothing.


   

[TheDreadPirate]

Can you access Jellyfin directly from the same LAN? http://192.168.1.126:8096 ? Did you enable remote connections in Jellyfin?

Also, since you meaned Cloudflare, Cloudflare Tunnels or enabling proxying in your Cloudflare DNS config to stream video is against their TOS and I recommend not using it and setting the DNS config to "DNS Only".

[Zhaytoshi]

Yes did enable the remote connection and also I was able to Access Via LAN and WIFI using my phone     

        I just followed some of the info I've seen here.

---

Also watched this guy video and did what he exactly show in the video https://www.youtube.com/watch?v=qlcVx-k-02E&t=588s

[TheDreadPirate]

You did this part?

   

And you setup port forwarding in your router for ports 80 and 443?

[Zhaytoshi]

Yes, I did that part. Why ? About the port forwarding, it's already setup, but if I understand correctly, based on his video he did not turn on his port because NPM already took care of it, Right ??

[TheDreadPirate]

You still need to forward ports 80 and 443. How else will external requests get through your router? The port publishing in the docker config for Nginx is only for allowing those ports into the container since it isn't using host networking. You don't need to forward port 8096, though.

[Zhaytoshi]

Oh I see. Thank you for that information But the port has been open for almost 2 days now, And still nothing has changed.
    as you can see in my router config. but maybe adding 8096 will give some hope.