I downloaded thevscg-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
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.
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.
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.
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.
Resolution: Check Client Configuration: Ensure the client is correctly configured to present an SSL certificate when making requests to the server. This often involves setting up the client with the necessary certificate files (certificate and private key) and configuring it to use them in requests.
To do this, you must open your Nginx configuration file, which is generally located in /etc/nginx/sites-available/default or similar pathways, and alter the ssl_certificate and ssl_certificate_key directives to reflect the pathway where you saved your new files.
A 400 bad request error occurs when a browser sends a request to a web server that the server cannot understand or process correctly. This is an HTTP response status code in the 4XX range. HTTP status codes starting with 4XX typically indicate an error on the client side—meaning the issue is on your end.
And the 405 Method Not Allowed error code means that your browser has sent an HTTP request (GET, POST, PUT, etc.)that isn't allowed for that specific resource, or URL. In many cases, this is triggered by something the user does. The most common cause is inputting the wrong URL.
This error message is typically returned due to a bad request, or as a result of an issue with the request headers or cookies. This article is not intended to be exhaustive as there are a wide variety of causes, however some possible issues are covered.
Introduction: My name is Dan Stracke, I am a homely, gleaming, glamorous, inquisitive, homely, gorgeous, light person who loves writing and wants to share my knowledge and understanding with you.
We notice you're using an ad blocker
Without advertising income, we can't keep making this site awesome for you.
