Problems with generate certificates for GitLab nginx server on VirtualBox

Help
1

Please fill out the fields below so we can help you better.

My domain is: intenso-gitlab.pl

I ran this command: sudo certbot certonly --webroot --webroot-path=/var/www/letsencrypt -d intenso-gitlab.pl

The operating system my web server runs on is (include version): ubuntu 16.04

Hi guys,
i had installed GitLab EE on my VirtualBox Ubuntu 16.04. Also, i bought domain intenso-gitlab.pl. Next in Virtualbox i had activated second with host only settings - this allow me to receive ip address and assign it to my domain. When i create self signed certificate everything is ok i can access to my domain by https but i would like to use let’s encrypt option. So i proceeded this tutorial:
https://www.digitalocean.com/community/tutorials/how-to-secure-gitlab-with-let-s-encrypt-on-ubuntu-16-04
but when i call this command:
sudo certbot certonly --webroot --webroot-path=/var/www/letsencrypt -d intenso-gitlab.pl
it throw me strange exception:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for intenso-gitlab.pl
Using the webroot path /var/www/letsencrypt for all unmatched domains.
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. intenso-gitlab.pl (http-01): urn:acme:error:unknownHost :: The server could not resolve a domain name :: No valid IP addresses found for intenso-gitlab.pl

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: intenso-gitlab.pl
    Type: unknownHost
    Detail: No valid IP addresses found for intenso-gitlab.pl

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address.

Maybe somebody will have any advice how to solve this problem?

2

The A record for this domain points to a local IP address (192.168.56.101). This is not accessible from the public internet, and is an invalid setup. Using HTTP-01 challenges, your server must be publicly accessible.

If you cannot modify this, then you are still able to use the DNS-01 challenge type, however the automation of that process is highly dependent on your DNS provider allowing programmatic access. Without that, you would need to manually intervene to create the required TXT entries every time you renew.

3

Ok so conslusion is that when I assign Public ip to this sever it solve my problem?

4

Yes, assigning a public IP address should solve your problem.

5

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