-
Notifications
You must be signed in to change notification settings - Fork 392
CloudBeaver and Nginx
dbeaver-devops edited this page Dec 4, 2024
·
8 revisions
By default CloudBeaver listens to plain http protocol, processes all static content via the Jetty server and is not load balanced.
All these issues can be resolved by putting a real web server in front of CloudBeaver.
We can use Nginx as the most popular web server.
sudo apt update
sudo apt install nginx
Open the Nginx configuration in your favorite text editor.
The default Nginx config file is /etc/nginx/sites-enabled/default
.
location / {
proxy_pass http://localhost:8978;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
To identify the information (real IP address) of client connected to the web server through NGINX, add the parameter forwardProxy:true
into your server configuration.
- Application overview
- Demo Server
- Administration
- Server configuration
- Create Connection
- Connection Templates Management
- Access Management
-
Authentication methods
- Local Access Authentication
- Anonymous Access Configuration
- Reverse proxy header authentication
- LDAP
- Single Sign On
- SAML
- OpenID
- AWS OpenID
- AWS SAML
- AWS IAM
- AWS OpenId via Okta
- Snowflake SSO
- Okta OpenId
- Cognito OpenId
- JWT authentication
- Kerberos authentication
- NTLM
- Microsoft Entra ID authentication
- Google authentication
- User credentials storage
- Cloud Explorer
- Cloud storage
- Query Manager
- Drivers Management
- Supported databases
- Accessibility
- Keyboard shortcuts
- Features
- Server configuration
- CloudBeaver and Nginx
- Domain manager
- Configuring HTTPS for Jetty server
- Product configuration parameters
- Command line parameters
- Local Preferences
- API
-
CloudBeaver Community
-
CloudBeaver AWS
-
CloudBeaver Enterprise
-
Deployment options
-
Development