Postgresql app not receive data from client

Hey, I am having an issue interacting with instance of postgres fly.

I have deployed an app on Fly that is suppose to connect to posgres instance using the user and password.

The details of the app is shown in Deploy FusionAuth docker images is not Working

Each time the app try to interact/ send data to the postgres instance it failed.
If i check the postgres instance log on Fly i saw this logs

2-08-26T10:15:58.374 app[f99c15f8] fra [info] keeper | 2022-08-26 10:15:58.372 UTC [28094] LOG: could not receive data from client: Connection reset by peer

2022-08-26T10:31:15.318 app[f99c15f8] fra [info] keeper | 2022-08-26 10:31:15.316 UTC [1030] LOG: could not receive data from client: Connection reset by peer

2022-08-26T10:31:15.444 app[f99c15f8] fra [info] keeper | 2022-08-26 10:31:15.442 UTC [1032] LOG: could not receive data from client: Connection reset by peer

2022-08-26T10:33:38.657 app[f99c15f8] fra [info] keeper | 2022-08-26 10:33:38.656 UTC [1878] LOG: could not receive data from client: Connection reset by peer

2022-08-26T11:05:49.525 app[f99c15f8] fra [info] keeper | 2022-08-26 11:05:49.523 UTC [13080] LOG: could not receive data from client: Connection reset by peer

Am not sure what is the cause, @kurt any suggestions ?

That error is saying the app is dropping the connection before it sends data. I would guess the FusionApp logs have some corresponding info, but that’s almost definitely a problem with the FusionAuth app itself.

For some reason the deployed FusionAuth is not logging anything at all which makes debugging hard.

For example, if i use a wrong connection url, no error will appear on Fly but when i run the container
on my pc i can see the error.

Also when i start the app on Fly i get only this log

2022-08-24T10:48:29Z app[0cfdfb1b] fra [info]Starting fusionauth-app...
2022-08-24T10:48:29Z app[0cfdfb1b] fra [info]  --> Logging to /usr/local/fusionauth/logs/fusionauth-app.log

But when i am on my pc more details log is shown in the terminal

Starting fusionauth-app...
  --> Logging to /usr/local/fusionauth/logs/fusionauth-app.log
---------truncate 
---------------------------------------------------------------------------------------------------------
--------------------------------------- Entering Maintenance Mode ---------------------------------------
---------------------------------------------------------------------------------------------------------

2022-08-24 10:22:48.681 AM INFO  io.fusionauth.api.configuration.DefaultFusionAuthConfiguration - Loading FusionAuth configuration file [/usr/local/fusionauth/config/fusionauth.properties]
2022-08-24 10:22:48.682 AM INFO  io.fusionauth.api.configuration.DefaultFusionAuthConfiguration - Set property [fusionauth-app.url] set to [http://0.0.0.0:9011] using configured value.
2022-08-24 10:22:48.682 AM INFO  com.inversoft.configuration.BasePropertiesFileInversoftConfiguration - 
  - Overriding default value of property [database.mysql.enforce-utf8mb4] with value [true]
  - Overriding default value of property [fusionauth-app.runtime-mode] with value [development]
  - Overriding default value of property [search.type] with value [database]

2022-08-24 10:22:48.682 AM INFO  com.inversoft.maintenance.MaintenanceModePoller - Poller started to Wait for configuration to be completed.
2022-08-24 10:22:48.683 AM INFO  io.fusionauth.app.primeframework.FusionHTTPContextAuthSetup - Initializing the FusionAuth HTTP Context.
2022-08-24 10:22:48.728 AM INFO  org.primeframework.mvc.netty.PrimeHTTPServer - Starting FusionAuth HTTP server on port [9011]
2022-08-24 10:22:48.765 AM INFO  org.primeframework.mvc.netty.PrimeHTTPServer - Starting FusionAuth HTTP loopback server on port [9012]
^C2022-08-24 10:27:10.896 AM INFO  org.primeframework.mvc.netty.PrimeHTTPServer - Shutting down the Prime HTTP server [/0.0.0.0:9011]
2022-08-24 10:27:10.897 AM INFO  org.primeframework.mvc.netty.PrimeHTTPServer - Shutting down the Prime HTTP server [/0.0.0.0:9012]

So is there a way to log more error level on fly ?
maybe that will help to debug the error