Privacy error after changing nginx config
We have a website that was previously available under 3 addresses
report.example.com
www.live.example.com
live.example.com
all working with https and http and using letsencrypt certs.
It's been decided that the site will only be available under 1 address - live.example.com
The nginx config is setup as follows
server
listen 80;
server_name report.example.com www.live.example.com live.example.com;
return 301 https://$host$request_uri;
server
listen 443 ssl;
server_name report.example.com www.live.example.com live.example.com;
...
I have changed this to the following:-
server
listen 80;
listen 443 ssl;
server_name report.example.com www.live.example.com;
return 301 $scheme://live.example.com$request_uri;
server
listen 80;
server_name live.example.com;
return 301 https://$host$request_uri;
server
listen 443 ssl;
server_name live.example.com;
...
However when I try and navigate the site with the new config I get
Attackers might be trying to steal your information from www.live.example.com (for example, passwords, messages or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
The certificate is the same, so contains all the correct details.
nginx
asked Nov 15 '18 at 15:09
user2099762user2099762
3217
add a comment |
We have a website that was previously available under 3 addresses
report.example.com
www.live.example.com
live.example.com
all working with https and http and using letsencrypt certs.
It's been decided that the site will only be available under 1 address - live.example.com
The nginx config is setup as follows
server
listen 80;
server_name report.example.com www.live.example.com live.example.com;
return 301 https://$host$request_uri;
server
listen 443 ssl;
server_name report.example.com www.live.example.com live.example.com;
...
I have changed this to the following:-
server
listen 80;
listen 443 ssl;
server_name report.example.com www.live.example.com;
return 301 $scheme://live.example.com$request_uri;
server
listen 80;
server_name live.example.com;
return 301 https://$host$request_uri;
server
listen 443 ssl;
server_name live.example.com;
...
However when I try and navigate the site with the new config I get
Attackers might be trying to steal your information from www.live.example.com (for example, passwords, messages or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
The certificate is the same, so contains all the correct details.
nginx
asked Nov 15 '18 at 15:09
user2099762user2099762
3217
add a comment |
We have a website that was previously available under 3 addresses
report.example.com
www.live.example.com
live.example.com
all working with https and http and using letsencrypt certs.
It's been decided that the site will only be available under 1 address - live.example.com
The nginx config is setup as follows
server
listen 80;
server_name report.example.com www.live.example.com live.example.com;
return 301 https://$host$request_uri;
server
listen 443 ssl;
server_name report.example.com www.live.example.com live.example.com;
...
I have changed this to the following:-
server
listen 80;
listen 443 ssl;
server_name report.example.com www.live.example.com;
return 301 $scheme://live.example.com$request_uri;
server
listen 80;
server_name live.example.com;
return 301 https://$host$request_uri;
server
listen 443 ssl;
server_name live.example.com;
...
However when I try and navigate the site with the new config I get
Attackers might be trying to steal your information from www.live.example.com (for example, passwords, messages or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
The certificate is the same, so contains all the correct details.
nginx
asked Nov 15 '18 at 15:09
user2099762user2099762
3217
We have a website that was previously available under 3 addresses
report.example.com
www.live.example.com
live.example.com
all working with https and http and using letsencrypt certs.
It's been decided that the site will only be available under 1 address - live.example.com
The nginx config is setup as follows
server
listen 80;
server_name report.example.com www.live.example.com live.example.com;
return 301 https://$host$request_uri;
server
listen 443 ssl;
server_name report.example.com www.live.example.com live.example.com;
...
I have changed this to the following:-
server
listen 80;
listen 443 ssl;
server_name report.example.com www.live.example.com;
return 301 $scheme://live.example.com$request_uri;
server
listen 80;
server_name live.example.com;
return 301 https://$host$request_uri;
server
listen 443 ssl;
server_name live.example.com;
...
However when I try and navigate the site with the new config I get
Attackers might be trying to steal your information from www.live.example.com (for example, passwords, messages or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
The certificate is the same, so contains all the correct details.
nginx
nginx
asked Nov 15 '18 at 15:09
user2099762user2099762
3217
asked Nov 15 '18 at 15:09
user2099762user2099762
3217
asked Nov 15 '18 at 15:09
user2099762user2099762
3217
asked Nov 15 '18 at 15:09
user2099762user2099762
3217
asked Nov 15 '18 at 15:09
user2099762user2099762
3217
3217
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Turns out that as they're on the same server I had to include the certificate details in the old virtualhost as well as the new one
answered Nov 15 '18 at 15:28
user2099762user2099762
3217
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322407%2fprivacy-error-after-changing-nginx-config%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Turns out that as they're on the same server I had to include the certificate details in the old virtualhost as well as the new one
answered Nov 15 '18 at 15:28
user2099762user2099762
3217
add a comment |
Turns out that as they're on the same server I had to include the certificate details in the old virtualhost as well as the new one
answered Nov 15 '18 at 15:28
user2099762user2099762
3217
add a comment |
Turns out that as they're on the same server I had to include the certificate details in the old virtualhost as well as the new one
answered Nov 15 '18 at 15:28
user2099762user2099762
3217
Turns out that as they're on the same server I had to include the certificate details in the old virtualhost as well as the new one
answered Nov 15 '18 at 15:28
user2099762user2099762
3217
answered Nov 15 '18 at 15:28
user2099762user2099762
3217
answered Nov 15 '18 at 15:28
user2099762user2099762
3217
answered Nov 15 '18 at 15:28
user2099762user2099762
3217
3217
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322407%2fprivacy-error-after-changing-nginx-config%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
