Please note, that while getting this error iām still able to connect to the DB server using a DB admin tool like Navicat or DB Visualizer. The error ONLY occurs in Wappler
I have dont full re-installs of wappler, tried this on brand new projects, restarted docker. opened up all IPs on the DB server etc
How to reproduce
Create a new Wappler project
Use the default App template
Add a new DB connection to a Linode Managed DB
Try to connect
Test it it 5.8.x and it works. Upgrade to 6.2.1 and it WONT work.
I can provide logs and even DB credentials if required.
Thanks @George I will look at this tomorrow morning (iāve already started drinking tonightā¦so not a great headspace to troubleshoot)
What gets me though, why would it work fine if i roll back to Wappler 5.8 and then stop working when i upgrade to 6.2? Iāve deleted and reinstalled Wappler multiple times today.
Works in 5.8 doesnāt work in 6.2.1.
Iāve also had another Wappler user test on their Mac and it doesnāt work in 6.2 either
write EPROTO 2264064:error:1000012e:SSL routines:OPENSSL_internal:KEY_USAGE_BIT_INCORRECT:..\..\third_party\boringssl\src\ssl\ssl_cert.cc:605:
Iām not using SSH to connect to the DB, just SSL, but i do have SSH keys stored with Wappler. They certainly could be an issue and i have had to generate new SSH keys recently as i was trying to move from Sockets and Docker Machines over to Resource Manager.
There were some connections that couldnāt be imported, likely to SSH issues (although itās always been the same PC) so i had to generate new keys and create new Linode servers fresh using Resource Manager.
I did have some project keys generated by Wapplerā¦ Because of all the updates and roll-backs it s bit messy, but i added Linode back in through Resource Manager and imported the keys.
So now the keys stored here:
Are definitely in the Linode SSH keys manager along with the original personal SSH keys i created years ago that are still on my personal PC in Users/.SSH folder.
This did not fix anything, but hopefully gives you some more info
I realise this isnāt exactly a Wappler issue as its probably not able to be replicated by others (although i had another Wappler user try to connect to this same DB server on his Mac and he got the same error)
But somewhere along the way this last week+ something happened to break the access.
I logged a job with Linode but they said the server looks fine on their end.
It has a live production DB on it so i donāt particularly want to migrate to new DB, but that is my only option now.
Also, if a create a new Managed Database server on Linode then Wappler can connect as per normalā¦it is only this existing server that is the issue
But yes, i had also been to the Linode site, and checked the CA Cert. It was already installed in my Wappler project but i have re-downloaded and saved again to the certs folder. Same error:
Iām happy to share the full login details for you to test the connection yourself, Iāll change the passwords later and restrict IP addresses anyway so security is not an issue.
I would much rather fix this issue than to have to delete the DB and create a new one
After large investigation, Iāve discovered that your LInode managed database is using an old self signed SSL certificate. Those are no longer officially accepted and give errors.
So either issue a new certificate for SSL or switch SSL of but then you will need to add your ip for allowed access.