nginx-proxy / nginx-proxy/nginx-proxy

Infinite Redirects

Open
#805 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
19.9k
Forks
3k
Avg merge
2d 11h
Merged PRs (30d)
1

Description

Trying to use the base httpd (apache)

  image: httpd
  expose:
    - 80
    - 443
nginx-proxy:
  env_file:
    - .env
  image: jwilder/nginx-proxy
  container_name: nginx
  restart: always
  environment:
    - DEFAULT_HOST
  links:
    - httpd
  volumes:
    - ./certs:/etc/nginx/certs:ro
    - /etc/nginx/vhost.d
    - /usr/share/nginx/html
    - /var/run/docker.sock:/tmp/docker.sock:ro
  ports:
    - 80:80
    - 443:443
letsencrypt:
  env_file:
    - .env
  image: jrcs/letsencrypt-nginx-proxy-companion
  container_name: letsencrypt
  restart: always
  links:
    - nginx-proxy
  volumes:
    - ./certs:/etc/nginx/certs:rw
    - /var/run/docker.sock:/var/run/docker.sock:ro
  volumes_from:
    - nginx-proxy

In the .env, I defined

VIRTUAL_HOST=domain.com
LETSENCRYPT_HOST=domain.com
LETSENCRYPT_EMAIL=mail@domain.com

When curling to domain.com , I get errors (in the logs I get redirect errors).

In fact curl https://domain.com -i Shows that the redirects is to https://domain.com!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the compose configuration shown in the issue, including the httpd, nginx-proxy, and letsencrypt services and the .env values. Run curl https://domain.com -i and inspect the proxy and companion logs to trace the self-redirect. Done means the configured domain serves the expected httpd content over HTTPS without redirecting to itself.

Written by the indexing model from the issue text.

Assessment

Tech stack
apache, docker, nginx
Domain
devops, infrastructure, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.