ssl | Subtree split of the Acme PHP Ssl Component | TLS library

I had the same problem after upgrade to 8.0.27. Had no clue how to solve it.

I downgraded MySQL Workbench back to 8.0.19, and the 'No' and 'If Available' options came back.

Maybe they just want you to buy Navicat I guess.

I would propose to take a look in the RateLimiter direction. Maybe it does not work as expected, depending on the number of requests your application does over time. From the Javadoc for Ratelimiter: "It is important to note that the number of permits requested never affects the throttling of the request itself ... but it affects the throttling of the next request. I.e., if an expensive task arrives at an idle RateLimiter, it will be granted immediately, but it is the next request that will experience extra throttling, thus paying for the cost of the expensive task." Also helpful might be this discussion: github or github

I could imaginge there is some throttling adding up or other effect in the RateLimiter, i would try to play around with it and make sure this thing really works the way you want. Alternatively, consider using Spring @Scheduled to read from your queue. You might want to spice it up using embedded JMS for further goodies (message persistence etc).

Microsoft.Data.SqlClient 4.0 is using ENCRYPT=True by default. Either you put a certificate on the server (not a self signed one) or you put

TrustServerCertificate=Yes;

on the connection string.

Consider the following steps:

1. Open MySQL workbench
2. right-click on the particular MySQL instance and select "Edit Connection"
3. Select the "SSL" tab under Connection Method
4. Select the drop-down for the "Use SSL" and choose "If Available" instead of "Required".
5. Click the "Test Connection" button at the lower right connection to make sure you can now connect without errors.

You need to downgrade to a lower workbench version here in order to see more options in the drop-down from step 4.

This is because of a root CA Let’s Encrypt uses (and Mongo Atals uses Let's Encrypt) has expired on 2020-09-30 - namely the "IdentTrust DST Root CA X3" one.

The fix is to manually install in the Windows certificate store the "ISRG Root X1" and "ISRG Root X2" root certificates, and the "Let’s Encrypt R3" intermediate one - link to their official site - https://letsencrypt.org/certificates/

Copy from the comments: download the .der field from the 1st category, download, double click and follow the wizard to install it.

I don't know if it may be the right approach for you, but what I did is downgrade my version of MySQL Workbench to 6.3 and uninstalled the previous version and it will then give you the "if available" option for SSL. As you are right, it is not the case for previous versions, however you do lose a few more modern features in the process.

https://downloads.mysql.com/archives/workbench/

Another solution as well is to connect to connect to the database in 6.3 and since the configuration saves are in same location, upgrade to 8.0 where it will still have the old configuration file and won't use SSL due to backwards compatibility.

Using getFirestore from lite library will not work with onSnapshot. You are importing getFirestore from lite version:

Make sure you have the development packages of Open SSL installed. For example, libssl-dev on Ubuntu or openssl-devel on Fedora. If OpenSSL is already installed and the crate still had trouble finding it, you can set the OPENSSL_DIR environment variable to specify the path for your Open SSL installation. If you are using windows you can use the Win32/Win64 OpenSSL Installation Project to provide a simple installation of OpenSSL on windows.

My approach here would look like this: