Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:depotrace.com
I ran this command:
It produced this output:SSL_PROTOCOL_ERROR
My web server is (include version):React js
The operating system my web server runs on is (include version):Google Cloud
My hosting provider, if applicable, is:GoDaddy
I can login to a root shell on my machine (yes or no, or I don't know):Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):Yes
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):V1.32.0
my react application which is running on port 3000 has rerouted to port 80 using nginx,
i have done this procedure during ssl certificate for my domain,now my domain which is using https is uanble to make calls to the backend which is running on port 9000
Well, that's not going to work obviously if there's a front end in front of the backend. It should try to connect to your website (using the hostname, not IP address) on port 443, not to some IP address on port 9000?
Also, unrelated, you might want to add a HTTP to HTTPS redirect on port 80 (HTTP).
Do you mean "from a browser"? Because if not, I'm puzzeling what you're meaning / trying to do..
Also, what's running on port 9000 and what's running on the earlier mentioned port 3000? Isn't this more of a "how to set up nginx as a reverse proxy" question? I'm still failing to see how this is Let's Encrypt related.
There's nothing listening on port 3000 from the public internet, but there is on port 443.
Due to the lack of understanding your exact setup in details, especially the situation before and after and how you got the certificate et cetera I cannot answer this question completely.
Also, as mentioned before, your website works perfectly on https://depotrace.com/ except for the bogus login form destination. So whatever it is you're dealing with, please provide way more information than "it doesn't work". That's not something we can work with.