It seems there is a misunderstanding. To be clear, this is what I mean:

┌───────────────────────┐    
│ Browser               │    
└───────────────────────┘    
     ▲                       
     │ port 443 open         
     │                       
     │                       
┌────┼──────────────────┐    
│ Proxy (traefik)       │    
└───────────────────────┘    
     ▲                       
     │                       
     │ web port open to proxy
     │                       
     │                       
┌────┼──────────────────┐    
│ DBgate (in docker)    │    
└───────────────────────┘    
     ▲                       
     │                       
     │                       
     │                       
┌────┼──────────────────┐    
│ Database              │    
└───────────────────────┘    

This way DBgate serves the web app to the browser, but also acts as a ‘backend’ which connects to the database. This way my databases are not exposed to the web, only the proxy is, which handles domain name routing and http traffic.

Are you sure? Because thats how dbgate works, and I thought this was similar.

Well, I assume there is a backend which takes care of securely connecting to the databases. That way I can connect the backend to the internal network where I can connect to the database, and without exposing the database port still use this from the browser.

Deterministic DDL Export - Replaced AI-based export with native SQL generation

Much better. Now it works for my case, which it didn’t before.

If anyone got this running in docker for example, I like to hear from you ;)

Strange, I’m pretty sure I did fill in the url. Or does attaching a picture change the post type so the url is not taken into account?