# Certbot gives certificate to my domain registrar and not me

**URL:** <https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211>\
**Category:** Help\
**Created:** [March 21, 2018, 12:22am UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211 "2018-03-21T00:22:39Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![OriginMayo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/originmayo/32/25686_2.png) [@OriginMayo](https://community.letsencrypt.org/u/OriginMayo)\
**Post date:** [March 21, 2018, 12:22am UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/1 "2018-03-21T00:22:39Z")

</div>

so i used certbot, i tried to make it use my domain - for simplicity \> certbot xxxxx -d mydomain.se  
and then when i get into the website it wont let me in at all since the certificate came out to be on my registrar (egensajt.se)

(error msg. : NET::ERR\_CERT\_COMMON\_NAME\_INVALID)

i think this happened because i turned of my 80 port since certbot wants to use that when it does the stuff that does the stuff and thus when i ping mydomain.se it will ping the registrar and not me…

how can i go about my way to solve this issue?

my setup is like this  
VPS with Ubuntu 17.10 + LAMP + HTTPS/HSTS + TLS (443/80)  
Registrar with my domain (egensajt.se)  
Certbot

i started this project to learn my way into the web stuff and now im kind of stuck for the 3rd time after learning about A Records and Cnames and stuffs

Any sort of help is appreciated really thanks!

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [March 21, 2018, 12:48am UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/2 "2018-03-21T00:48:32Z")

</div>

> [@OriginMayo](#):
>
> how can i go about my way to solve this issue?

By telling us the _exact_ certbot command you ran and _exactly_ the output of that command.  
We can't just go and guess what happened, crystall globes don't actually work you know.

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [March 21, 2018, 5:50am UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/3 "2018-03-21T05:50:20Z")

</div>

We also need your domain name. Not masked.version.

Aside from command line problems, which @Osiris already requested , have you checked your DNS records? (Make sure no redirect, park page are in place)

Thank you

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [March 21, 2018, 12:49pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/5 "2018-03-21T12:49:28Z")

</div>

Okay.

The issue is you are using a certificate which only contain common name of gridux.se, the error message appears when you are using www.gridux.se (you didn’t have that as a alt. name)  
That’s why you see the error message.

You would need to run `sudo certbot certonly --standalone --preferred-challenges http -d gridux.se -d www.gridux.se` to include all your websites.

Thank you  
@OriginMayo

---

<div class="post-metadata">

**Author:** ![OriginMayo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/originmayo/32/25686_2.png) [@OriginMayo](https://community.letsencrypt.org/u/OriginMayo)\
**Post date:** [March 21, 2018, 12:53pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/6 "2018-03-21T12:53:31Z")

</div>

> 0 0,12 \* \* \* python -c 'import random; import time; time.sleep(random.random() \* 3600)' && ./path/to/certbot-auto renew

is my cron job.

what can i do to fix the caching issue?

update : @stevenzhu  
**tried with the command you gave me**

> sudo certbot certonly --standalone --preferred-challenges http -d gridux.se -d www.gridux.se

i cant do it, it gives me an error that it cant access port 80 so i shut down the apache2 server but then if i ping my domain it pings to egensajt.se and not my VPS so it will still give the certificate to egensajt.se and not me...

---

<div class="post-metadata">

**Author:** ![bytecamp](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bytecamp](https://community.letsencrypt.org/u/bytecamp)\
**Post date:** [March 21, 2018, 1:02pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/7 "2018-03-21T13:02:12Z")

</div>

> [@OriginMayo](#):
>
> so it will still give the certificate to egensajt.se and not me…

Certbot does not **give** anything out. If your domain name is not delegated to your VPS (via A record), you can only use dns-01 authorization. I also would not use the standalone method if you actually have a webserver software running on that system.

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [March 21, 2018, 1:02pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/8 "2018-03-21T13:02:14Z")

</div>

You also need to add `www.gridux.se` and point to your `gridux.se` ip.  
(Which if you don’t, you will need to remove www redirection to avoid any certificate error appeared on www site and not use your www site)

Thank you

---

<div class="post-metadata">

**Author:** ![OriginMayo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/originmayo/32/25686_2.png) [@OriginMayo](https://community.letsencrypt.org/u/OriginMayo)\
**Post date:** [March 21, 2018, 1:05pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/9 "2018-03-21T13:05:50Z")

</div>

then what should i do @bytecamp i am new to this whole ssl thing

@stevenzhu i guess i would add that in my 000-default-something.conf in system-available yes?

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [March 21, 2018, 1:07pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/10 "2018-03-21T13:07:12Z")

</div>

You will need to add the www domain to your http and https conf in your file.

add ip for www site to your dns provider.

Then rerun the command i showed you.

Thank you

---

<div class="post-metadata">

**Author:** ![bytecamp](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bytecamp](https://community.letsencrypt.org/u/bytecamp)\
**Post date:** [March 21, 2018, 1:08pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/11 "2018-03-21T13:08:23Z")

</div>

> [@OriginMayo](#):
>
> then what should i do @bytecamp i am new to this whole ssl thing

First of all, fix your DNS settings as stevenzhu already described.  
gridux.se and www.gridux.se must point to the ip address of your VPS.

---

<div class="post-metadata">

**Author:** ![OriginMayo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/originmayo/32/25686_2.png) [@OriginMayo](https://community.letsencrypt.org/u/OriginMayo)\
**Post date:** [March 21, 2018, 1:16pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/12 "2018-03-21T13:16:52Z")

</div>

ok the a record is set to www by standard in the dns settings and its pointing to my ip since the beginning  
@bytecamp @stevenzhu

> @  
> Subdomän  
> 103.105.48.228  
> Adress  
> 3600  
> TTL

> www  
> Subdomän  
> 103.105.48.228  
> Adress  
> 3600  
> TTL

**i have this in my virtual host file**

> Redirect permanent "/" "[https://gridux.se/](https://gridux.se/)"  
> im assuming i need to add another line like this  
> Redirect ~~"/" "[https://www.~~](https://www.~~)"  
> am i correct?

---

<div class="post-metadata">

**Author:** ![bytecamp](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bytecamp](https://community.letsencrypt.org/u/bytecamp)\
**Post date:** [March 21, 2018, 1:21pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/13 "2018-03-21T13:21:20Z")

</div>

I currently see no problem with your certificate. It is valid for gridux.se and www.gridux.se, no warnings or error messages in Firefox.

---

<div class="post-metadata">

**Author:** ![OriginMayo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/originmayo/32/25686_2.png) [@OriginMayo](https://community.letsencrypt.org/u/OriginMayo)\
**Post date:** [March 21, 2018, 1:23pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/14 "2018-03-21T13:23:16Z")

</div>

im getting “Your connection is not private” in chrome and when i click the lock icon it tells me the certificate is for egensajt.se 😕 @bytecamp

update : it seems im having problems with chrome. i download firefox and its working?!?

---

<div class="post-metadata">

**Author:** ![bytecamp](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bytecamp](https://community.letsencrypt.org/u/bytecamp)\
**Post date:** [March 21, 2018, 1:25pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/15 "2018-03-21T13:25:26Z")

</div>

The dns records are most likely cached on your side. Either flush any dns cache or wait a day. Or you did not close all instances of Chrome and it did not reload your website correctly.

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [March 21, 2018, 1:28pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/16 "2018-03-21T13:28:48Z")

</div>

Hi,

The IP address is not correct for me

For my DNS queries, it still show your registrar’s IP.

P.S. However it seems your domain records need some time to update. Please wait for that to update. (Since your SOA shows the IP are correct now)

Thank you

---

<div class="post-metadata">

**Author:** ![OriginMayo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/originmayo/32/25686_2.png) [@OriginMayo](https://community.letsencrypt.org/u/OriginMayo)\
**Post date:** [March 21, 2018, 1:34pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/17 "2018-03-21T13:34:32Z")

</div>

@bytecamp i tried to clear the dns host cache but it didnt work

> went to chrome://net-internals/#dns and pressed the clear cache button

@stevenzhu ok i will relax for a bit lets see how this works out

---

<div class="post-metadata">

**Author:** ![OriginMayo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/originmayo/32/25686_2.png) [@OriginMayo](https://community.letsencrypt.org/u/OriginMayo)\
**Post date:** [March 21, 2018, 1:43pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/18 "2018-03-21T13:43:09Z")

</div>

@bytecamp @stevenzhu

do i have to add anything to my nameservers? atm they are all on the registrars own names (egensajt.se)

---

<div class="post-metadata">

**Author:** ![bytecamp](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bytecamp](https://community.letsencrypt.org/u/bytecamp)\
**Post date:** [March 21, 2018, 1:45pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/19 "2018-03-21T13:45:51Z")

</div>

> [@OriginMayo](#):
>
> do i have to add anything to my nameservers?

You don't need to do anything:

[https://unboundtest.com/m/A/gridux.se/RKYXL45K](https://unboundtest.com/m/A/gridux.se/RKYXL45K)  
[https://unboundtest.com/m/A/www.gridux.se/NXXU7ISP](https://unboundtest.com/m/A/www.gridux.se/NXXU7ISP)

Both domains point to the correct location.

Besides: unless you know what you are doing, don't mess with DNS at all.

---

<div class="post-metadata">

**Author:** ![OriginMayo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/originmayo/32/25686_2.png) [@OriginMayo](https://community.letsencrypt.org/u/OriginMayo)\
**Post date:** [March 21, 2018, 1:49pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/20 "2018-03-21T13:49:18Z")

</div>

ah good to know, starting to get a hang of things here now 😃  
also - im doing this so that i can learn something. how am i supposed to learn if i am not doing anything?

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [March 21, 2018, 2:26pm UTC](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211/21 "2018-03-21T14:26:52Z")

</div>

This process is barely hard (confusing) if you saw those “helpful” tutorials.

However it’s not hard at all.

So… I can’t think anything that’s actually hard.

[Next page](https://community.letsencrypt.org/t/certbot-gives-certificate-to-my-domain-registrar-and-not-me/57211.md?page=2)
