Traefik + Cloudflared on Unraid

I have tried to follow the available guides from IbraCorp and TechnoTim and the like, but I just cannot manage to wrap my head around what I have configured incorrectly or how to proceed with troubleshooting.

There are no errors that I can see in the logs for Traefik or Cloudflare Tunnel. Traefik is able to detect all the services I want to when I add docker labels. There are no warnings or errors on the traefik dashboard. Yet for some reason I am unable to access any of my services same for Jellyfin. For some reason the configured hostname jellyfin.mydomain.tld does connect to the service (though it doesn't seem to be using traefik - if I add an authelia middleware I don't get a prompt for it). If i add a hostname for jellyseer.mydomain.tld - I get an error code: 522

Here are my traefik.yml and my fileConfig.yml config files.

Happy to provide any other info. Been trying to get this resolved myself for a month and I'm completely stuck. My gut says something is breaking in how the traffic is being routed, but I don't know how to identify where that might be.

Enable and check Traefik debug log (doc) and also Traefik access log in JSON format (doc).

Thanks for the suggestions. I do have debug level logging. I've tried to configure the access log using this:

global:
  checkNewVersion: true
  sendAnonymousUsage: false
# Log level INFO|DEBUG|ERROR
log:
  level: DEBUG
accessLog:
  format: json
  filePath: /etc/traefik/access.log
  fields:
    # Keep all the fields by default
    defaultMode: keep
    names:
      # Drop the Field ClientUserName
      ClientUsername: drop
    headers:
      # Keep all the headers by default
      defaultMode: keep
      names:
        # Redact the User-Agent header value
        User-Agent: redact
        # Drop the Authorization header value
        Authorization: drop
# Enable traefik ui
api:
  dashboard: true
  insecure: true
serversTransport:
  insecureSkipVerify: true

in my traefik.yml file - I added it after I posted the pastebin

Unfortunately, the access.log file is completely empty after restarting the container and attempting to access services again.