Context
Hi.
I'm in the process of switching the web access to https using a reverse proxy on the host on which the dockers are instantiated.
The reverse proxy, using nginx, is configured to map the host public ip address (for now) as follows:
location /opencve {
include proxy_params;
proxy_pass http://localhost:8000;
}
The opencve.cfg file is modified so that the server_name variable is the ip.ad.dr.es/opencve and set use_reverse_proxy to True. I didn't change the Dockerfile nor the docker-compose.yml file regarding to the launch of the web server command.
Expected Behavior
I expected the service would be usable over https.
Actual Behavior
A 404 error page is displayed. Changing the server_name to that of the public address and port makes opencve reachable but without being proxyfied.
Steps to Reproduce the Problem
- install opencve using dockers with the mentioned configuration
- configure nginx on the host to be a reverse proxy for opencve
- try and access the https port on the host.
Specifications
- OpenCVE version: 1.2.3
- Platform: debian 11
- Docker version: 20.10.5+dfsg1-1+b5
- Docker-compose version: 1.25.0-1
Screenshots (optional)

Context
Hi.
I'm in the process of switching the web access to https using a reverse proxy on the host on which the dockers are instantiated.
The reverse proxy, using nginx, is configured to map the host public ip address (for now) as follows:
The
opencve.cfgfile is modified so that theserver_namevariable is theip.ad.dr.es/opencveand setuse_reverse_proxytoTrue. I didn't change the Dockerfile nor thedocker-compose.ymlfile regarding to the launch of the web server command.Expected Behavior
I expected the service would be usable over https.
Actual Behavior
A 404 error page is displayed. Changing the
server_nameto that of the public address and port makes opencve reachable but without being proxyfied.Steps to Reproduce the Problem
Specifications
Screenshots (optional)