cant set the forward server to host name

[Alacard]

when setting up a new proxy host, your unable to use the server hostname for the destination, show error data/forward_host must match pattern "^(([^.]+.)+[^.]+)|([[0-9a-f:]+])$" when you try

[Zoey2936]

I think jellyseerr is a docker container, right? I would recommend you to use static ips, since nginx has not the best dns implementation, but if you need to use a hostname you can try to use <container-name>.<docker-network-name> as input this should also work, but as I wrote dns can fail.

I personally handle it like this:
I run NPMplus in network mode host and to connect to my containers I expose the needed ports of them like this "127.0.0.1::" and in npmplus I proxy to 127.0.0.1 with . Through this I don't need static IPs and have no problem with DNS. Also containers of diffrent services can't talk to each other since they don't need to be in the same docker network so that NPMplus can talk to them (or NPMplus doesn't need to be in all docker networks). And the non docker services could connect to all containers anyway

[Cantello]

can you send me your compose.yaml please?

I just edited my response as it nearly works now (with the container_name instead of 127.0.0.1) but here's an excerpt from my docker-compose.yml:

networks:
  network:
    name: network

services:

  npmplus:
    container_name: npmplus
    image: docker.io/zoeyvid/npmplus:latest # or ghcr.io/zoeyvid/npmplus:latest
    restart: always
    ports:
      - 80:80
      - 81:81
      - 443:443
    volumes:
      - "/opt/npmplus:/data"
    environment:
      - "TZ=Europe/Berlin"
      - "[email protected]"
      - "IPV4_BINDING=0.0.0.0"
      - "NPM_IPV4_BINDING=0.0.0.0"
    networks:
      - network

  komga:
    image: gotson/komga:latest
    container_name: komga
    volumes:
      - /opt/komga:/config
      - /mnt/box:/data
    ports:
      - 127.0.0.1:25600:25600
    user: 1001:1001
    environment:
      - TZ=Europe/Berlin
    restart: unless-stopped
    networks:
      - network

One problem that remains (but is maybe unrelated to this issue) is that I can set proxies to all other containers but not for npm+'s admin UI. When setting the network_mode to host it does not work at all, when set to bridge and the relevant ports are exposed, I can access the admin panel but only with the correct external IP address, not with the hostname (CNAME in the DNS set to the A with the IP address). Otherwise it results in an error (Error code: [MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT]) and curl auth.domain.com:81 results in a "301 moved permanently". I have no idea why npm is not proxying correctly or not serving the correct SSL certificate. The logs do not show anything unusual. Can the logs somehow be set to debug mode?

[Zoey2936]

screenshot of the config which isnnot weorking?

[Cantello]

screenshot of the config which isnnot weorking?

[Zoey2936]

scheme need to be https not http

[Cantello]

scheme need to be https not http

Works, thanks!