A docker image to proxy outside requests to your local network

docker run -e TARGET=https://yandex.ru -p 3000:3000 ghcr.io/fandsdev/adhoc-proxy

Images are published to GHCR for linux/amd64 and linux/arm64. Use :latest, or pin a release — e.g. ghcr.io/fandsdev/adhoc-proxy:0.2.0.

Or via docker-compose

        services:
          adhoc-proxy:
            image: ghcr.io/fandsdev/adhoc-proxy
            environment:
              - TARGET=http://192.168.19.8:15672

You can quickly use a self-signed certificate, by passing SELF_SIGNED_TLS environment variable.

        services:
          adhoc-proxy:
            image: ghcr.io/fandsdev/adhoc-proxy
            environment:
              - TARGET=http://192.168.19.8:15672
              - SELF_SIGNED_TLS=1

Some russian hosts — gosuslugi.ru, sberbank.ru, most of .gov.ru — serve certificates issued by the Ministry of Digital Development CA (НУЦ Минцифры), which is not in the Mozilla or system trust store. Proxying to such a TARGET fails with unable to verify the first certificate.

Pass RUSSIAN_TLS to additionally trust the Russian Trusted Root CA and Sub CA:

        services:
          adhoc-proxy:
            image: ghcr.io/fandsdev/adhoc-proxy
            environment:
              - TARGET=https://www.gosuslugi.ru
              - RUSSIAN_TLS=1

This is opt-in and additive: without it nothing changes, and with it the regular public CAs stay trusted as well. The certificates are vendored in certs/russian-trusted-ca.pem (source: https://www.gosuslugi.ru/crt) — the Sub CA expires in March 2027 and will need a refresh.