Off Topic > Off Topic
Programming Megathread
Metario:
--- Quote from: Foxscotch on September 15, 2016, 10:48:15 PM ---
(it says issued to "bot.foxscotch.us" (for my telegram bot) but it is obviously valid for foxscotch.us too or your browser wouldn't accept it)
maybe it's because it just renewed today or something
whatevs
--- End quote ---
did you do bot.foxscotch.us and foxscotch.us for common names when getting the certificate?
Foxscotch:
--- Quote from: Metario on September 16, 2016, 03:53:01 PM ---did you do bot.foxscotch.us and foxscotch.us for common names when getting the certificate?
--- End quote ---
no idea what you mean by that lol. the certificate is for both foxscotch.us and bot.foxscotch.us
you can literally go to https://foxscotch.us/ and see that the certificate is, indeed, valid for foxscotch.us
it's possible that keybase just doesn't trust let's encrypt, for some wild, definitely unreasonable reason
Metario:
--- Quote from: Foxscotch on September 16, 2016, 08:16:47 PM ---no idea what you mean by that lol. the certificate is for both foxscotch.us and bot.foxscotch.us
you can literally go to https://foxscotch.us/ and see that the certificate is, indeed, valid for foxscotch.us
it's possible that keybase just doesn't trust let's encrypt, for some wild, definitely unreasonable reason
--- End quote ---
no my phone doesn't either and i've run websites with let's encrypt certs before, something's wrong
Pecon:
Barring actually finding out what is wrong with the ssl certificate, you could just use their DNS-based proof method instead of the file one.
Also, getting the site brown townyzed on ssllabs might reveal some info about what is wrong with the certificate.
Paperwork:
if you still have a key to provide i can take one.