Mendix Console JDBC connection failed

0
Hi, i'm trying to deploy On-Prem using Mendix Console with sql server installed in the same server , but i get error " failed with SQLState: 08S01 Error code: 0 Message: ""encrypt" property is set to "true" and "trustServerCertificate" property is set to "false"" i tried DatabaseUseSsl: false in settings.yaml for the application but didn't work i tried to put DatabaseJdbcUrl , but it didn't work , i tried to disabled and enabled the DB encryption and it didn't work. another point , if i use the following DatabaseJdbcUrl it didn't overide the other values as per mendix Doc. DatabaseJdbcUrl: jdbc:sqlserver://localhost:1433;databaseName=DBName;integratedSecurity=false;encrypt=true;trustServerCertificate=true; i tried many combiations but all give the same error.   can any one share the DB YAML settings part so we can see how it suppose to be .  
asked
4 answers
1

Hello Hamed,

I had the same problem as you when upgrading an app version.

Since version 9.24.25, the version of the JDBC driver has changed.

To run our apps locally, you need to configure it in custom as follows:

DatabaseJdbcUrl jdbc:sqlserver://{urlbdd:1733};databaseName={namedatabase};integratedSecurity=false;encrypt=true;trustServerCertificate=true

 

Maybe this can help you

answered
0

Hi Eddy,

thank you for your answer , my issue was in the server i'm trying to install mendix on.

 

the resolution is to add DatabaseJdbcUrl =false in the advanced options in the app configuration

answered
0

Hi Jasper,

i think as i remember you need to put the DatabaseJdbcUrl in 

Configuration -> Advanced -> Custom Mendix Settings

answered
0

As a best practice, this is actually how it should be done, although implementing it properly requires some initial research. So, you might need to have enough time to implement the following:

 

For dev, test, and QA environments, creating separate YAML configuration files is a clean and maintainable solution. For example, you can define settings-dev.yaml, settings-test.yaml, and settings-qa.yaml, and keep only environment-specific settings in these files, such as the JDBC URL, trustServerCertificate, log level, feature flags, and endpoints. Then, during your CI/CD pipeline or Kubernetes deployment, you mount the appropriate file as settings.yaml or configure the runtime to read it based on the target environment. This approach removes the need for manual changes, reduces the risk of configuration mistakes between environments, and helps ensure safer settings are preserved in production.

answered