topic Re: 400 bad request, No required SSL certificate was sent, nginx in SmartZone and Virtual SmartZone

400 bad request, No required SSL certificate was sent, nginx

stephen_garwick — Thu, 23 Apr 2020 21:26:01 GMT

I downloaded the vscg-5.2.0.0.699.ova, and followed the install docs for my ESXi, 6.7.0 cluster. I'm setting the Smartzone up as an essentials profile with only 1 NIC. The setup goes fine without any problems. I can ping the vSmartzone appliance from my workstation just fine, and it can ping me. When I go the WEB interface to finish the install, I received the following message:

400 bad reques
No required SSL certificate was sent
nginx

Would you please help with the problem.

Re: 400 bad request, No required SSL certificate was sent, nginx

Ankush_Chandan — Thu, 23 Apr 2020 22:06:09 GMT

Hi Stephan,

While logging into the Web please use following format https:// IP>:8443.

Regards,
-Ankush

Re: 400 bad request, No required SSL certificate was sent, nginx

stephen_garwick — Thu, 23 Apr 2020 22:43:50 GMT

Hi Akush,

Thanks. I just found this out from the .PDF file. The video and HTLM docs didn't say anything about a port number.

I do have another problem, if you are willing to help...

When I do login to continue with the setup, i'm pushed to the Cluster Information section. I'm not able to go back to make any changes to the following:

Language
Profile

I fill in the cluster information and click NEXT, i'm then taken to the Management IP Address area. I complete that section and click NEXT, but it just bring me back to the Cluster Information area again. I'm stuck in a loop. Any thoughts?

Thanks.

Re: 400 bad request, No required SSL certificate was sent, nginx

diego_garcia_de — Fri, 24 Apr 2020 01:36:48 GMT

I remember seeing something similar in the past. Are you assigning your IP using DHCP or static? I think I was using DHCP and I still had to manually assign the DNS servers and/or the default gateway. If possible, configure all IP parameters manually and make sure to provision all those values.

Re: 400 bad request, No required SSL certificate was sent, nginx

diego_garcia_de — Fri, 24 Apr 2020 01:41:25 GMT

Otherwise, if at all possible, you could try to complete the installation using the console of the virtual machine? On ESXi you should be able to access the virtual "screen" of the VM and complete the installation like that.

Re: 400 bad request, No required SSL certificate was sent, nginx

diego_garcia_de — Fri, 24 Apr 2020 01:43:13 GMT

Also, the problem I was having was actually the opposite, I couldn't assign a DNS server when using static IP configuration. With no DNS the next step, which was NTP was failing if trying to use NTP with "name based" servers (like "pool.ntp.org"). I had to point the configuration to an IP based NTP and after NTP syncs, it would let me continue.

Re: 400 bad request, No required SSL certificate was sent, nginx

stephen_garwick — Fri, 24 Apr 2020 17:13:47 GMT

Thanks all for the information. I was able to get through the install. It turns out that I fat fingered the IP address for the NAT. Once I fixed that, all went well. Again thanks.

Re: 400 bad request, No required SSL certificate was sent, nginx

romankris — Mon, 01 May 2023 06:30:54 GMT

This issue typically happens for a 2-Way TLS, when the certificate sent by the client is expired. In a 2-way TLS, both client and server exchange their public certificates to accomplish the handshake. The client validates the server certificate and the server validates the client certificate. During the TLS handshake if it is found that the client certificate is expired, then the server will send 400 Bad request with the message “The SSL certificate error”. The solution for this problem is that procure a new certificate and upload the certificate.