Giter VIP home page Giter VIP logo

Comments (6)

cs-network avatar cs-network commented on June 18, 2024 3

I ran into this issue and based on this and this, I was able to get an nginx proxy working by adding the following directives to the proxy configuration:

chunked_transfer_encoding off;
proxy_buffering off;
proxy_cache off;
proxy_set_header Connection keep-alive;
proxy_connect_timeout 3600;
proxy_send_timeout 3600;
proxy_read_timeout 3600;
keepalive_timeout 3600;

As indicated by the above links, this is an issue with how the default nginx proxy configuration handles server side events--I don't think it's an issue with webproc itself.

Can u share the file with whole information to be able to reverse proxy?

Just saw that u guys used traefik, im not using it :(

Thanks

Here is my section running like described above:

server {
    server_name dns.dev.local;

    listen 80;
    location / {
        proxy_set_header Host dns.dev.local;
        proxy_pass http://<ip>:<port>/;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        chunked_transfer_encoding off;
        proxy_buffering off;
        proxy_cache off;
        proxy_set_header Connection keep-alive;
        proxy_connect_timeout 3600;
        proxy_send_timeout 3600;
        proxy_read_timeout 3600;
        keepalive_timeout 3600;
    }
}

from webproc.

Fifty-Nine avatar Fifty-Nine commented on June 18, 2024 1

I ran into this issue and based on this and this, I was able to get an nginx proxy working by adding the following directives to the proxy configuration:

chunked_transfer_encoding off;
proxy_buffering off;
proxy_cache off;
proxy_set_header Connection keep-alive;
proxy_connect_timeout 3600;
proxy_send_timeout 3600;
proxy_read_timeout 3600;
keepalive_timeout 3600;

As indicated by the above links, this is an issue with how the default nginx proxy configuration handles server side events--I don't think it's an issue with webproc itself.

from webproc.

THernandez03 avatar THernandez03 commented on June 18, 2024

Same issue here, but instead of using nginx, im using Traefik as a proxy.

I exposed the port 8080 and enter with the IP 127.0.0.1 it works, but using the proxy shows the webproc page with no connection.

image

from webproc.

kebertxela avatar kebertxela commented on June 18, 2024

@THernandez03 I am also using Traefik and had odd problems with a few things including browser caching and non exposed ports- I added this line to the end of the Dockerfile

EXPOSE 53/udp 8080/tcp

and I'm getting a proper display now

  dnsmasq:
    build:
      context: jpillora/docker-dnsmasq
    container_name: dnsmasq
    ports:
     - 53:53/udp
    restart: always
    volumes:
     - ./dnsmasq.conf:/etc/dnsmasq.conf
     - ./tftpboot:/tftproot
    cap_add:
     - NET_ADMIN
    labels:
      - "traefik.enable=true"
      - "traefik.port=8080"
      - "traefik.backend=dnsmasq"
      - "traefik.frontend.rule=Host:dnsmasq.example.com"
      - "traefik.frontend.headers.SSLRedirect=true"
      - "traefik.frontend.headers.STSSeconds=315360000"
      - "traefik.frontend.headers.browserXSSFilter=true"
      - "traefik.frontend.headers.contentTypeNosniff=true"
      - "traefik.frontend.headers.forceSTSHeader=true"
      - "traefik.frontend.headers.STSIncludeSubdomains=true"
      - "traefik.frontend.headers.STSPreload=true"
      - "traefik.frontend.headers.frameDeny=true"

from webproc.

THernandez03 avatar THernandez03 commented on June 18, 2024

@THernandez03 I am also using Traefik and had odd problems with a few things including browser caching and non exposed ports- I added this line to the end of the Dockerfile

EXPOSE 53/udp 8080/tcp

and I'm getting a proper display now

  dnsmasq:
    build:
      context: jpillora/docker-dnsmasq
    container_name: dnsmasq
    ports:
     - 53:53/udp
    restart: always
    volumes:
     - ./dnsmasq.conf:/etc/dnsmasq.conf
     - ./tftpboot:/tftproot
    cap_add:
     - NET_ADMIN
    labels:
      - "traefik.enable=true"
      - "traefik.port=8080"
      - "traefik.backend=dnsmasq"
      - "traefik.frontend.rule=Host:dnsmasq.example.com"
      - "traefik.frontend.headers.SSLRedirect=true"
      - "traefik.frontend.headers.STSSeconds=315360000"
      - "traefik.frontend.headers.browserXSSFilter=true"
      - "traefik.frontend.headers.contentTypeNosniff=true"
      - "traefik.frontend.headers.forceSTSHeader=true"
      - "traefik.frontend.headers.STSIncludeSubdomains=true"
      - "traefik.frontend.headers.STSPreload=true"
      - "traefik.frontend.headers.frameDeny=true"

For some reason i didn't work for me... i don't know what i'm missing.

This is my docker-compose

  dns:
    container_name: dns
    build: ./containers/dns
    restart: on-failure
    networks:
      - main
    ports:
      - 53:53/udp
    env_file:
      - ./.env.docker
    labels:
      - traefik.enable=true
      - traefik.port=8080
      - traefik.backend=dns
      - traefik.frontend.rule=Host:dns.dev.example.com
      - traefik.frontend.headers.SSLRedirect=true
      - traefik.frontend.headers.STSSeconds=315360000
      - traefik.frontend.headers.browserXSSFilter=true
      - traefik.frontend.headers.contentTypeNosniff=true
      - traefik.frontend.headers.forceSTSHeader=true
      - traefik.frontend.headers.STSIncludeSubdomains=true
      - traefik.frontend.headers.STSPreload=true
      - traefik.frontend.headers.frameDeny=true

and this is my Dockerfile

FROM jpillora/dnsmasq
COPY dnsmasq.conf /etc/dnsmasq.conf
EXPOSE 53/udp 8080/tcp

PD: i considered changing traefik.frontend.rule value

from webproc.

vinanrra avatar vinanrra commented on June 18, 2024

I ran into this issue and based on this and this, I was able to get an nginx proxy working by adding the following directives to the proxy configuration:

chunked_transfer_encoding off;
proxy_buffering off;
proxy_cache off;
proxy_set_header Connection keep-alive;
proxy_connect_timeout 3600;
proxy_send_timeout 3600;
proxy_read_timeout 3600;
keepalive_timeout 3600;

As indicated by the above links, this is an issue with how the default nginx proxy configuration handles server side events--I don't think it's an issue with webproc itself.

Can u share the file with whole information to be able to reverse proxy?

Just saw that u guys used traefik, im not using it :(

Thanks

from webproc.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.