Skip to content

Releases: nginx-proxy/nginx-proxy

1.0.2

01 Dec 11:55
14ccabf
Compare
Choose a tag to compare

nginx 1.23.2

What's Changed

  • chore(deps): bump golang from 1.18.0 to 1.18.1 by @dependabot in #1960
  • chore: indent location, upstream in template by @ntnj in #1939
  • chore(deps): bump pytest from 7.1.1 to 7.1.2 in /test/requirements by @dependabot in #1971
  • chore(deps): bump nginx from 1.21.6 to 1.23.2 by @dependabot in #2072

New Contributors

Full Changelog: 1.0.1...1.0.2

1.0.1

10 Apr 11:51
2f82265
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.0.0...1.0.1

1.0.0

07 Mar 13:23
3257177
Compare
Choose a tag to compare

What's Changed

Contributors

Many thanks to the following people for their work and/or feedback on the path based routing feature.
@AlexanderLieret @junderw @warren-ru @JMLX42 @OliverRhyme @trowj @WolfspiritM @rodrigoaguilera @RafaelKr @gregsymons

Full Changelog: 0.10.1...1.0.0

0.10.1

25 Feb 17:28
0.10.1
9cdb804
Compare
Choose a tag to compare

nginx 1.21.6

What's Changed

  • Add and display nginx-proxy version by @buchdag in #1865
  • chore(deps): bump nginx from 1.21.5 to 1.21.6 by @dependabot in #1875
  • chore(deps): bump pytest from 6.2.5 to 7.0.0 in /test/requirements by @dependabot in #1882
  • chore(deps): bump pytest from 7.0.0 to 7.0.1 in /test/requirements by @dependabot in #1886
  • Fix path to default.conf in README.md by @nathanweeks in #1888
  • Add container logs in case testcontainer exited unexpectedly by @R0Wi in #1895

New Contributors

Full Changelog: 0.10.0...0.10.1

0.10.0

06 Jan 15:37
ed7b17d
Compare
Choose a tag to compare

This is a minor release.

Bugs fixed:

  • #1769 the DockerHub images had world writable files in /app (fixed by #1770)

Changes since 0.9.3:

  • the DH group generation at startup has been removed and replaced by the use of pre-generated RFC 7919 DH groups (#1797 #1848)

Dependencies:

  • nginx -> 1.21.5

Other changes:

  • the container based test method (as opposed to running tests directly on the host) was fixed in #1856.
  • various code style (#1807) and docs update (#1775 #1819).

Thanks to @crazy-max, @kevinnls, @polarathene, @ucyang and @HPPinata for their contributions to this release.

0.9.3

01 Sep 07:14
52d208d
Compare
Choose a tag to compare

This is a patch release.

Changes since 0.9.2:

  • the upstream names where reverted to the legacy (pre 0.9.1) behaviour to avoid breaking existing setups that rely on them. A new optional SHA1_UPSTREAM_NAME environment variable enable 0.9.2 behaviour if needed. See #1736 for more information.

Default behaviour:

# example.com
upstream example.com {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://example.com;
  }
}

With SHA1_UPSTREAM_NAME set to true:

# example.com
upstream 0caaf24ab1a0c33440c06afe99df986365b0781f {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://0caaf24ab1a0c33440c06afe99df986365b0781f;
  }
}

Plus some CI and docs updates.

0.9.2

11 Aug 15:58
0e3844a
Compare
Choose a tag to compare

This is a patch release.

Bugs fixed:

  • correctly redirect HTTP to custom HTTPS port using when using HTTPS_PORT (fixed by #1662)
  • use a single server 127.0.0.1 down entry in upstream blocks, and only when required (fixed by #1667, #1679)

Changes since 0.9.1:

  • nginx 1.19.10 -> 1.21.1
  • docker-gen 0.7.6 -> 0.7.7
  • golang 1.16.5 -> 1.16.7

Various CI and docs updates.

Note:

  • in 0.9.1, the upstream names where changed and "-upstream" was appended to the bare reverse proxied hostname.
  • in 0.9.2, they were changed again to an sha1 hash of the hostname to prevent further issues with incorrect upstream names.

If you relied on those upstream names in your custom configuration(s), please be aware that you'll have to update them if you use version 0.9.1 or higher.

0.9.0 and prior:

# example.com
upstream example.com {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://example.com;
  }
}

0.9.1:

# example.com
upstream example.com-upstream {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://example.com-upstream;
  }
}

0.9.2+:

# example.com
upstream 0caaf24ab1a0c33440c06afe99df986365b0781f {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://0caaf24ab1a0c33440c06afe99df986365b0781f;
  }
}

0.9.1

14 Jun 11:46
eb00b06
Compare
Choose a tag to compare

This is a patch release.

Bugs fixed:

  • #1162 upstream naming pre-empts proxy-passing to other load-balanced services (fixed by #1163)
  • #1361, #1407 and #1512 bad parsing of the arguments passed to the DH parameters generation script (fixed by #1263)
  • #1424 nginx config load broken by resolver's IPv6 link local interface scoped address (fixed by #1557)
  • X-Forwarded-Ssl header was improperly set in SSL-terminated setups (fixed by #1185)
  • create_server_certificate.sh script in tests was broken (fixed by #1619)
  • #1132 upstream server was incorrectly marked as down when using internal networks (fixed by #1609)

Changes since 0.9.0:

  • new SERVER_TOKENS per proxied container variable to control the server_tokens directive (#1620)
  • additional debug information on the rendered template with the DEBUG variable (#1609)
  • $upstream_addr added to nginx access logs (#1659)
  • switch to a Go module compatible version of forego (#1603)
  • golang 1.15.10 -> 1.16.5

Various doc updates.

0.9.0

28 Apr 20:31
35df872
Compare
Choose a tag to compare

This is a minor release.

Bugs fixed:

  • #1548 #1586 empty upstream blocks caused by docker-gen being unable to get its own container ID on some updated systems
  • the aforementioned bug(s) had the same root cause that the one preventing docker-gen from working correctly on Amazon ECS, so this might be fixed too, waiting for eventual confirmation from an AWS ECS user

Changes since 0.8.0:

  • nginx 1.19.3 -> 1.19.10 (#1590)
  • docker-gen 0.7.4 -> 0.7.6 (#1601)
  • switch to a multi stage Dockerfile (#1470)
  • nginx's worker_connections upped from the default 1024 to 10240 (#973)
  • brought ACME no redirection inline with nginx-proxy/acme-companion (#1409)
  • documentation updates (#1145 #1184 #1332 #1505 #1583 #1599)

The test suite has been updated and the CI now runs correctly again after moving from Travis CI to GitHub Actions (#1572)

We're now building multiarch (amd64, arm64, armv7) images on GitHub Actions and pushing them to Dockerhub (3a8b49f 4a1d5bf).

The images are also now available under the org's registry (nginxproxy/nginx-proxy) in addition to the legacy registry (jwilder/nginx-proxy).