Trying to fix my certificate after changing domain names

Help
21

First: Now you use betatest.lospec.com, not beta.

Second: This

doesn't work ( https://check-your-website.server-daten.de/?q=betatest.lospec.com ):

Domainname Http-Status redirect Sec. G
• http://betatest.lospec.com/
142.93.77.70 200 0.214 H
• http://www.betatest.lospec.com/
142.93.77.70 200 0.210 H
• https://betatest.lospec.com/
142.93.77.70 502 2.720 N
Bad Gateway
Certificate error: RemoteCertificateNameMismatch
• https://www.betatest.lospec.com/
142.93.77.70 502 2.593 N
Bad Gateway
Certificate error: RemoteCertificateNameMismatch
• http://betatest.lospec.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
142.93.77.70 404 0.213 A
Not Found
• http://www.betatest.lospec.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
142.93.77.70 404 0.210 A
Not Found

http isn't redirected, so it looks that these definitions are not used.

Third: If you want to use webroot, your server definition should have a DocumentRoot / root - definition.

So add

root /home/site/htdocs

to your http and your https block.

22

and doing this may fail too:

because:
http >301> https
https >proxy_pass> http://betatest.lospec
where "betatest.lospec" is defined as:

But we have yet to see the vhost config that covers "127.0.0.1:3000"
It is there where the document root can be found and must be matched by the (correct) --webroot -w path.

Please show that file or block.
and also show this file:

23

Here is the proxy config:

proxy_buffers 16 32k;
proxy_buffer_size 64k;
proxy_busy_buffers_size 128k;
proxy_cache_bypass $http_pragma $http_authorization;
proxy_connect_timeout 59s;
proxy_hide_header X-Powered-By;
proxy_http_version 1.1;
proxy_ignore_headers Cache-Control Expires;
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
proxy_no_cache $http_pragma $http_authorization;
proxy_pass_header Set-Cookie;
proxy_read_timeout 600;
proxy_redirect off;
proxy_send_timeout 600;
proxy_set_header Accept-Encoding '';
proxy_set_header Cookie $http_cookie;
proxy_set_header Host $host;
proxy_set_header Referer $http_referer;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_temp_file_write_size 64k;
proxy_set_header X-Original-Request $request_uri;

The only other file I can find (though I’m not really sure what I’m looking for) is _.conf:

server
{
    listen 80 default_server;
    listen [::]:80;
    server_name _;

    root /home/nginx/htdocs/public;

    location /
    {
        try_files $uri $uri/ =404;
    }
}
24

Please show:
netstat -pant | grep 3000

25

When I do it on my actual server i get this:

tcp        0      0 127.0.0.1:3972          127.0.0.1:3000          TIME_WAIT   -
tcp        0      0 127.0.0.1:3970          127.0.0.1:3000          TIME_WAIT   -
tcp        0      0 127.0.0.1:3974          127.0.0.1:3000          TIME_WAIT   -
tcp        0      0 127.0.0.1:3978          127.0.0.1:3000          TIME_WAIT   -
tcp        0      0 127.0.0.1:3964          127.0.0.1:3000          TIME_WAIT   -
tcp        0      0 127.0.0.1:3968          127.0.0.1:3000          TIME_WAIT   -
tcp        0      0 127.0.0.1:3976          127.0.0.1:3000          TIME_WAIT   -
tcp        0      0 127.0.0.1:3980          127.0.0.1:3000          TIME_WAIT   -
tcp6       0      0 :::3000                 :::*                    LISTEN      23496/www
tcp6       0      0 127.0.0.1:3000          127.0.0.1:3962          TIME_WAIT   -
tcp6       0      0 127.0.0.1:3000          127.0.0.1:3966          TIME_WAIT   -

but when i do it on the copy ive been trying to use, the one ive already run letsencrypt on for the new domain, nothing prints out.

26

This seems to be root of the problem.
The "instructions" are to use "127.0.0.1:3000"; but that only exists on the other server.

27

What does that mean?
Sometimes the main server only gives one line:
netstat -pant | grep 3000

But i made another exact copy of it, and it still returns blank, before even running certbot.

28

Oops, meant this:

tcp6 0 0 :::3000 :::* LISTEN 23496/www

29

tcp6 0 0 :::3000 ::: LISTEN 23496/www*
This means there is a service “www” that is listening on all IPs (IPv4 & IPv6) at port 3000.

30

Unfortunately despite all the above help I could not figure out how to fix this no matter what I tried. In the end I had to pay someone $90 to fix it for me. I wish it could have been easier, seems like changing the domain for a certificate should be a simple task.

31

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.