csr | Generate CSR | TLS library

Vue is primarily client side framework - rendering is done by JS running in the client's browser. Your app has (usually) only one index.html. That html file contains almost NO html. It only loads tons of JS...

This brings (at least) 2 challenges:

1. Crawlers (Google, but also Twitter/FB etc. for sharing) do not execute JS (or if they do, there is a big "wait in queue" penalty before your site is indexed) so they do not see any content. This is problem...
2. When the page being loaded is non-trivial (using lots of components/components rendering huge amount of HTML/components which needs some additional data from API), the initial render can still take a considerable amount of time. This is bad user experience - page loads, user sees nothing and after some time, content appears...

To solve this problems, SSR is introduced. 1st page request is pre-rendered on the server so the client (be it crawler or user) receives something meaningful to index/see and after that, Vue takes the control and everything else happens only on the client again...

By default the Spartacus siteContext will always default to the SSR transfer state if it is present before running the browser language logic.

I can see two solutions you could try:

1. You can remove the SSR transfer state. This way Spartacus will run your logic in browser every time. You can do it with:

The problem is that your intermediate CA ica.crt is no CA at all. It is missing basicConstraints=critical,CA:TRUE as extension. This means ica.crt is only a leaf certificate which should not be used to sign other certificates.

While openssl does not complain when using a certificate without such extension for signing, it will not be able to build the trust chain because ica.crt is not a valid issuer of server.crt due to the missing CA:TRUE constraint.

Adding the constraints make everything work, i.e.

You can use self-signed certificates for backend services. You cannot use self-signed certificates for frontend services.

Google Cloud HTTP Load Balancers only accept SSL certificates that are Domain Validated or higher.

Do not confuse Self Managed and Self Signed certificates.

Self-managed and Google-managed SSL certificates

The error message in your question means you are importing the wrong private key. You also have another error VALIDITY=3650. Public facing SSL certificates cannot be longer than 825 days (I think the practice is 398 days now), almost all vendors will not issue one longer than 365 days. For certificates valid longer than 365 days require even more details attached to the certificate.

For this matrix:

In your config file you have:

I had the same issue. Instead of using summary(reg_q1), try using rqpd::summary.rqpd(reg_q1). This solved it for me.

Here is one way with NearestNeighbors.

You must ensure that the following line will be there in your proguard rules. This will tell your application to ensure that the SpongyCastle encryption libraries can be used.