Problems with the IP address local versus global : how to make cerbot working?

Help
41

Your certbot must run on your server, not on another client.

And your server doesn't answer, so http-01 validation can't work ( https://check-your-website.server-daten.de/?q=ggc.world ):

Domainname Http-Status redirect Sec. G
• http://ggc.world/
37.116.214.189 -14 10.030 T
Timeout - The operation has timed out
• http://www.ggc.world/
37.116.214.189 -14 10.026 T
Timeout - The operation has timed out
• https://ggc.world/
37.116.214.189 -14 10.026 T
Timeout - The operation has timed out
• https://www.ggc.world/
37.116.214.189 -14 10.030 T
Timeout - The operation has timed out
• http://ggc.world/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
37.116.214.189 -14 10.027 T
Timeout - The operation has timed out
Visible Content:
• http://www.ggc.world/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
37.116.214.189 -14 10.027 T
Timeout - The operation has timed out
Visible Content:

Only timeouts, your domain is invisible, so Letsencrypt can't check your domain name.

Please read

42

I realized that the public IP address given by my Internet Service Provider changed:


I then updated it in the NameCheap’s domain account:

Then, ran the webpage in the server:

and then r-ran the test in the Server:

marco@pc01:~/go/src/MyPage$ sudo certbot certonly --webroot -w /home/marco/go/src/MyPage/ -d ggc.world -d www.ggc.world
[sudo] password for marco:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for ggc.world
http-01 challenge for www.ggc.world
Using the webroot path /home/marco/go/src/MyPage for all unmatched domains.
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. ggc.world (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://ggc.world/.well-known/acme-challenge/qPHQ8Q2nVBf8PX1qmhlN29f6SOxGiTPlb_gsbdtDaLw [109.116.160.164]: “\r\n504 Gateway Time-out\r\n\r\n

504 Gateway Time-out

\r\n
ng”, www.ggc.world (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.ggc.world/.well-known/acme-challenge/_W5X5h9Bqv-3ygnf9NqqHb6-KbSchnPNJTMCawUe84k [109.116.160.164]: “\r\n504 Gateway Time-out\r\n\r\n

504 Gateway Time-out

\r\n
ng”

IMPORTANT NOTES:

Please forgive me… what does it mean in practical terms “The client lacks sufficient authorization :: Invalid response from http://ggc.world/.well-known/acme-challenge” ?

43

You use a proxy configuration, that doesn't work -> timeout.

http://www.ggc.world/.well-known/acme-challenge/_W5X5h9Bqv-3ygnf9NqqHb6-KbSchnPNJTMCawUe84k

I'm not so firm with such proxy configurations: But that

looks bad: Looks like your / location is (internal redirected to)

/home/marco/go/src/MyPage/.well- known/acme-challenge

so

/.well-known/acme-challenge

would be

/home/marco/go/src/MyPage/.well- known/acme-challenge/.well- known/acme-challenge

Looks bad.

44

Now the /etc/nginx/conf.d/default.conf is this:

server {
    listen       80;
    server_name ggc.world www.ggc.world;
    location / {
        proxy_pass http://ggc.world:8080/home/marco/go/src/GraspGlobalChances/;
    }
}

But still when running acme testing: “The client lacks sufficient authorization”.
I’m stuck…

45

If your proxy config is buggy, you shouldn’t use a proxy configuration.

46

As far as I see in the available information online and in some books, proxy configuration within nginx’s default.conf is the only way to use NGINX as webserver for Beego (Golang’s framework):

47

Even in Nginx Cookbook , a 2017 book, a proxy configuration is used for Beego: https://drive.google.com/open?id=1xO0fNg9JOHz4vh94EHd4FTs_hBjJAiqb

Tomorrow I will deepen my knowledge about nginx configuration and nginx proxy configuration, in order to firmly grasp how to adapt it, and I will be back

48

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