Deployment SSL Error [ERR_TLS_CERT_ALTNAME_INVALID]

[miguelb]

Getting this error when trying out a new deployment, I’m using Let’s Encrypt/Ubuntu installation.

Production server is: fms.lenunu .com (Rapid SSL)
Dev Server is: fms.lenunu .com (Let’sEncrypt)

Any ideas? kinda stuck for the moment.

DeploymentError: FETCH_FAILED - Error pushing build: Error uploading file. This is likely a network issue. Please check your connection and try again. Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate’s altnames: Host: fms.lenunu.net. is not in the cert’s altnames: DNS:fms.lenunu.com, DNS:www.fms.lenunu.com

[toddgeist]

Hi Miguel

Welcome to the community.

When I try to verify your cert at that url, it does not show a Let’s encypt cert

SSL Checker

are you sure it is using Let’s encrypt?

Todd

[miguelb]

Todd thank for the reply. You can check the link now and you’ll it pass all the checks for the production server fms.lenunu .com
I think the failure happens at the dev server fms.lenunu .net

[miguelb]

This is the error in the dev server. (.net)

[miguelb]

Just in case you would like to see what the source production server ssl looks like (.com)

[toddgeist]

Your Dev Server (.net) can’t talk to Production (.com ).

You might be able to get away with switching from a Push to a Pull in your OttoDeploy. Turn on Advanced Options under the 3 dots.

It looks like your cert may still be the default fms cert on your .com server. Either way there is something wrong with that cert. You may want to reinstall it.

Todd

[miguelb]

Thanks Todd, I tried this. When I try to test the connection, this is the response. In this image I’m attaching which server is the one with the issue? Production or Destination?

[miguelb]

Todd thanks for the help. I’m just confused as to which is the server that’s having the issue. Is it the production or the dev? It seems that the deployment works up to a certain point and then when trying to communicate back to the production (source server) it fails. In my test, I’m trying to copy my files from the production to the dev server.

Thanks, this is my final question before I completely pivot I promise

[toddgeist]

Destination according to that test. Your source server is unable to contact destination.

Turn of “Push Build” as I mentioned before and it might just work fine.

But in that case you are moving files from Source ( .com ) to Destination (.net )

Is that what you want to do?

Todd

[miguelb]

Hey Todd yes that was exactly what I what I was trying to understand.

I fixed the issue by purchasing a new SSL certificate (wildcard), changing the domain and removing the Let’s Encrypt Cert.

I tried reinstalling the LE cert multiple times, even destroying the server image and rebuilding it from scratch with no luck. I don’t know, maybe some compatibility issues with OttoFMS and LetsEncrypt, something to keep an eye out.

Gonna start playing with it now!

Thanks again, and btw - Your livestreams with RC have been absolutely terrific my friend, great job!

[toddgeist]

Glad that worked.

Let’s Encrypt should work fine, though. We have lot’s of people using it.

Todd