Make Wappler's database manager connection to remote Docker use ssh tunneling

Wappler 5.5.3

Wappler’s database manager connection to remote Docker deployment is insecure:

  1. Wappler Docker deployment publishes DB port for the public:
services:
  db:
    ports:
      - '9906:5432'
  1. Wappler UI connects to DB through this public port
  2. The user is left to guess if this connection is actually encrypted or susceptible to MITM attacks
  3. The user can’t configure Wappler to use SSH tunneling, because it gives this complaint:

Proposal:

  1. Change docker-compose.yml to only publish DB port on 127.0.0.1:
services:
  db:
    ports:
      - '127.0.0.1:9906:5432'
  1. Change Wappler UI to use SSH tunneling to connect to the remote server and access DB on server’s 127.0.0.1
1 Like

I won’t consider it this a bug but more a feature request.

Shouldn’t there be more server configurations needed to use ssh tunneling ?

I think by default there isn’t any configuration to be made on the server

This has been added in Wappler 5.6.0

1 Like