Skip to content

Conversation

@bergi9
Copy link
Contributor

@bergi9 bergi9 commented Sep 7, 2021

I can only serve contents with IPv6 because I'm sitting behind CGN on IPv4. When enabling HTTP2 it still not serve contents with HTTP2 as there are missing arguments in the listen. But it still does the SSL encryption.
Previous to this commit it generates:

listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443;

Now it generates:

listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443 ssl http2;

I can only server contents with IPv6 because I'm sitting behind CGN on IPv4. When enabling HTTP2 it still not serve contents with HTTP2 as there are missing arguments in the `listen`. But it still does the SSL encryption.
Previous to this commit it generates:
```
listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443;
```
Now it generates:
```
listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443 ssl http2;
```
@jc21
Copy link
Member

jc21 commented Sep 8, 2021

Ah good catch :)

@jc21
Copy link
Member

jc21 commented Sep 8, 2021

This is an automated message from CI:

Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-1384

Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes.

@jc21 jc21 merged commit fb8f2c2 into NginxProxyManager:develop Sep 8, 2021
@bergi9 bergi9 deleted the patch-1 branch September 8, 2021 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants