lightning-charge not answering

[jagottsicher]

I am trying to revive some installation of nanotip.
My btc node is up and running (for years now),actual version and fully synced not pruned. It's running in a container and bitcoin-cli accessed it by a symlink opening a tempory container. works smoothly for years.

Same for the clightning-node- which is on top of BTC up and running. Actually with screen on the same machine a but synced.

Nanotip I also run via screen. it's easier to see what's going on if I reach the frontend, which is served by nginx configured as reverse proxy and equipped with some certs.

Once upon a time (2-3 years ago) it worked fine. today it is broken.

Probably because lightning-charge is not running. I cannot use nodejs because of several issues and downgrading to 7.6 is directly leading into the seventh circle of hell -- dependency hell. purgatory included for free. on the other hand starting the lightning-charge container works with

docker run -it -u 'id -u' -v 'pwd'/data:/data -v /scratch/bitcoin/mainnet/clightning:/etc/lightning -v /scratch/bitcoin/mainnet/bitcoind:/etc/bitcoin -p 9735:9735 -p 9112:9112 shesek/lightning-charge --api-token MYSUPERSECRETTOEKNALSOUSEDWITHNANOTIP

starting the container gives me the output:
`Using lightningd directory mounted in /etc/lightning... waiting for RPC unix socket...

And that it was. If I give the frontend a visit and start request, I can the it is processed by nanotip, but nanotip is not able to handle it to lightning-charge. I guess not correctly working with the actuall lightning-node. the lightning node itself I can easily reach the lightning-cli. it is responsive.

but

CHARGE=http://api-token:MYSUPERSECRETTOEKNALSOUSEDWITHNANOTIP@localhost:9112
curl $CHARGE/info

gives me
curl: (56) Recv failure: Connection reset by peer

Any ideas?
Is lightning-charge anyway outdated and should not be implemented anymore?
Is there a better entitiy which could serve a a connector between nanotip and clighting?