How to setup BTCPayServer with Litecoin MWEB

setup.md

Setup btcpayserver-docker with the opt-add-ltcmweb fragment.

Install the plugin (or restart BTCPayServer if already installed).

Add MWEB View Keys to Litecoin MWEB Wallet settings in BTCPayServer admin.

They can be retrieved using Electrum MWEB (release-9 and later).

Nope. I've gone the same way, but only the Litecoin, not the MWEB Node, is working. ;/ But additionally, I decided to activate the pruning of the LTC node. But it's impossible, that I have to run a full LTC node for running MWEB.

That's what the server says;

LTC MWEB Node available: False Last updated: 01/01/0001 00:00:00 Synced: False (0 / 0)

It is permitted to run the LTC node in pruning mode.
For the MWEB node, did you install the mweb fragment? And check that the mweb docker container is running?

I found out, what the issue was:
In opt-add-ltcmweb.yml the "ports" and "depends_on" was missing.
Also in litecoin.yml Ive added
BTCPAY_LTC_MWEB_ENABLED=true;
after adding and restarting, it starts working

From opt-add-ltcmweb.yml:

version: "3"

services:
  btcpayserver:
    environment:
      BTCPAY_LTC_MWEB_DAEMON_URI: http://mwebd:12345
  mwebd:
    restart: unless-stopped
    container_name: mwebd
    image: hectorchu1/mwebd
    volumes:
      - "mwebd_datadir:/data"
  ports:
    - "12345:12345" 
  depends_on:
    - litecoind 
volumes:
  mwebd_datadir:
required:
  - "litecoin"

I found out, what the issue was: In opt-add-ltcmweb.yml the "ports" and "depends_on" was missing. Also in litecoin.yml Ive added BTCPAY_LTC_MWEB_ENABLED=true; after adding and restarting, it starts working

From opt-add-ltcmweb.yml:

version: "3"

services:
  btcpayserver:
    environment:
      BTCPAY_LTC_MWEB_DAEMON_URI: http://mwebd:12345
  mwebd:
    restart: unless-stopped
    container_name: mwebd
    image: hectorchu1/mwebd
    volumes:
      - "mwebd_datadir:/data"
  ports:
    - "12345:12345" 
  depends_on:
    - litecoind 
volumes:
  mwebd_datadir:
required:
  - "litecoin"

Thank you, well done on getting it working. It's really odd though that nobody else previously had a problem. Perhaps it is a peculiarity of your docker setup.