Unable to connect to Metabase postgres DB. After updating (V0.43)

The metabase docker image was working normally on Azure app service (V0.42.4) .. after updating to latest version 0.43 it didnt work and its showing below issue)

2022-05-19T16:21:55.247086749Z 2022-05-19 16:21:55,246 WARN postgresql.Driver :: JDBC URL must contain a / at the end of the host or port: jdbc:postgresql://metabaseComp&password=&ssl=true&sslmode=require
2022-05-19T16:21:55.331198449Z 2022-05-19 16:21:55,239 ERROR metabase.core :: Metabase Initialization FAILED
2022-05-19T16:21:55.331265856Z clojure.lang.ExceptionInfo: Unable to connect to Metabase postgres DB. {}
2022-05-19T16:21:55.331279557Z at metabase.db.setup$fn__34861$verify_db_connection__34866$fn__34867$fn__34868.invoke(setup.clj:101)
2022-05-19T16:21:55.331290759Z at metabase.db.setup$fn__34861$verify_db_connection__34866$fn__34867.invoke(setup.clj:99)
2022-05-19T16:21:55.331300860Z at metabase.db.setup$fn__34861$verify_db_connection__34866.invoke(setup.clj:91)
2022-05-19T16:21:55.331310861Z at metabase.db.setup$fn__34943$setup_db_BANG___34948$fn__34949$fn__34952$fn__34953.invoke(setup.clj:146)
2022-05-19T16:21:55.331320862Z at metabase.util$do_with_us_locale.invokeStatic(util.clj:715)
2022-05-19T16:21:55.331346364Z at metabase.util$do_with_us_locale.invoke(util.clj:701)
2022-05-19T16:21:55.331357365Z at metabase.db.setup$fn__34943$setup_db_BANG___34948$fn__34949$fn__34952.invoke(setup.clj:145)
2022-05-19T16:21:55.331367166Z at metabase.db.setup$fn__34943$setup_db_BANG___34948$fn__34949.invoke(setup.clj:144)
2022-05-19T16:21:55.331376867Z at metabase.db.setup$fn__34943$setup_db_BANG___34948.invoke(setup.clj:138)
2022-05-19T16:21:55.331386568Z at metabase.db$setup_db_BANG_$fn__34978.invoke(db.clj:65)
2022-05-19T16:21:55.331396169Z at metabase.db$setup_db_BANG_.invokeStatic(db.clj:60)
2022-05-19T16:21:55.331405670Z at metabase.db$setup_db_BANG_.invoke(db.clj:51)
2022-05-19T16:21:55.331415471Z at metabase.core$init_BANG__STAR_.invokeStatic(core.clj:98)
2022-05-19T16:21:55.331424972Z at metabase.core$init_BANG__STAR_.invoke(core.clj:81)
2022-05-19T16:21:55.331434573Z at metabase.core$init_BANG_.invokeStatic(core.clj:138)
2022-05-19T16:21:55.331444174Z at metabase.core$init_BANG_.invoke(core.clj:133)
2022-05-19T16:21:55.331453675Z at metabase.core$start_normally.invokeStatic(core.clj:150)
2022-05-19T16:21:55.331463376Z at metabase.core$start_normally.invoke(core.clj:144)
2022-05-19T16:21:55.331472877Z at metabase.core$main.invokeStatic(core.clj:183)
2022-05-19T16:21:55.331482478Z at metabase.core$main.doInvoke(core.clj:177)
2022-05-19T16:21:55.331492079Z at clojure.lang.RestFn.invoke(RestFn.java:397)
2022-05-19T16:21:55.331501680Z at clojure.lang.AFn.applyToHelper(AFn.java:152)
2022-05-19T16:21:55.331511181Z at clojure.lang.RestFn.applyTo(RestFn.java:132)
2022-05-19T16:21:55.331520582Z at metabase.core.main(Unknown Source)
2022-05-19T16:21:55.331529883Z Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
2022-05-19T16:21:55.331539484Z at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:118)
2022-05-19T16:21:55.331549185Z at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:692)
2022-05-19T16:21:55.331561287Z at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:140)
2022-05-19T16:21:55.331571988Z at clojure.java.jdbc$get_connection.invokeStatic(jdbc.clj:372)
2022-05-19T16:21:55.331581689Z at clojure.java.jdbc$get_connection.invoke(jdbc.clj:274)
2022-05-19T16:21:55.331591290Z at clojure.java.jdbc$db_query_with_resultset_STAR
.invokeStatic(jdbc.clj:1111)
2022-05-19T16:21:55.331601491Z at clojure.java.jdbc$db_query_with_resultset_STAR
.invoke(jdbc.clj:1093)
2022-05-19T16:21:55.331611292Z at clojure.java.jdbc$query.invokeStatic(jdbc.clj:1182)
2022-05-19T16:21:55.331620793Z at clojure.java.jdbc$query.invoke(jdbc.clj:1144)
2022-05-19T16:21:55.331630294Z at clojure.java.jdbc$query.invokeStatic(jdbc.clj:1160)
2022-05-19T16:21:55.331646395Z at clojure.java.jdbc$query.invoke(jdbc.clj:1144)
2022-05-19T16:21:55.331656596Z at metabase.driver.sql_jdbc.connection$can_connect_with_spec_QMARK_.invokeStatic(connection.clj:264)
2022-05-19T16:21:55.331666497Z at metabase.driver.sql_jdbc.connection$can_connect_with_spec_QMARK_.invoke(connection.clj:261)
2022-05-19T16:21:55.331676198Z at metabase.db.setup$fn__34861$verify_db_connection__34866$fn__34867$fn__34868.invoke(setup.clj:99)
2022-05-19T16:21:55.331685999Z ... 23 more
2022-05-19T16:21:55.331695400Z Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
2022-05-19T16:21:55.331705401Z at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1507)
2022-05-19T16:21:55.331715002Z at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:644)
2022-05-19T16:21:55.331724803Z at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:554)
2022-05-19T16:21:55.331734604Z at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutAndMarkConnectionInUse(C3P0PooledConnectionPool.java:758)
2022-05-19T16:21:55.331744405Z at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:685)
2022-05-19T16:21:55.331754106Z ... 35 more
2022-05-19T16:21:55.331763607Z Caused by: java.sql.SQLException: No suitable driver found for jdbc:postgresql://metabaseComp&password=&ssl=true&sslmode=require
2022-05-19T16:21:55.331773809Z at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
2022-05-19T16:21:55.331783510Z at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
2022-05-19T16:21:55.331793011Z at metabase.db.data_source.DataSource.getConnection(data_source.clj:25)
2022-05-19T16:21:55.331802612Z at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:161)
2022-05-19T16:21:55.331813313Z at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:147)
2022-05-19T16:21:55.331823714Z at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:202)
2022-05-19T16:21:55.331833715Z at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1176)
2022-05-19T16:21:55.331843416Z at com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPendingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1163)
2022-05-19T16:21:55.331853317Z at com.mchange.v2.resourcepool.BasicResourcePool.access$700(BasicResourcePool.java:44)
2022-05-19T16:21:55.331862918Z at com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.run(BasicResourcePool.java:1908)
2022-05-19T16:21:55.331872719Z at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)
2022-05-19T16:21:55.361368570Z 2022-05-19 16:21:55,340 INFO metabase.core :: Metabase Shutting Down ...
2022-05-19T16:21:55.361416075Z 2022-05-19 16:21:55,342 INFO metabase.server :: Shutting Down Embedded Jetty Webserver
2022-05-19T16:21:55.400986168Z 2022-05-19 16:21:55,400 INFO metabase.core :: Metabase Shutdown COMPLETE

Hi @HadiHasan
If your username or password contains special characters, then you need to URL encode them.
Example @ would be %40

The connection string is working normally in v0.42.4 .. by default the user from azure postgreSQL is < UserName >@< ServerName > and the password has (_) underscore in it .. how it will be encoded?

@HadiHasan The connection string was completely rewritten in 0.43.0 and all "smart" stuff was removed to fix several issues and allow a lot of other type of functionality.
https://github.com/metabase/metabase/pull/19970
https://github.com/metabase/metabase/pull/20135

If your user is db@user, then your connection string should look like this:
jdbc:postgresql://db.example.com:port/mydb?user=db%40user&password=dbpwd

You can use a tool like https://www.urlencoder.org/ to help you encode parameters, so they comply with the jdbc standard.