You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue presents itself as a redirect to port 443 since it is using the default nginx.conf that is present within the nginx:latest container. That file is not set to import from /etc/nginx/conf.d so the file created via compose is never used. Manually editing the nginx.conf file and restarting nginx allows it to work.
Expected behavior
The expectation was for docker-compose to bring everything up and not require manual edits within the containers.
Observed behavior
The default.conf file is placed in the nginx container, but Nginx does not automatically load that configuration
The text was updated successfully, but these errors were encountered:
Hi @Dark-Helmet1, thanks for reporting, could you provide output of the following command extracting contents of /etc/nginx/conf.d/default.conf to help us triage further?
Diode version
v0.6.0
Deployment type
docker compose
Deployment type version
docker compose
Diode SDK type
diode-sdk-python
Diode SDK version
v0.4.0
Diode NetBox Plugin version
v0.6.0
NetBox version
v4.1.1
Steps to reproduce
When deploying the docker diode server the nginx container does not actually apply the configuration as expected.
Step 1: Get compose file
curl -o docker-compose.yml https://raw.githubusercontent.com/netboxlabs/diode/develop/diode-server/docker/docker-compose.yaml
Step 2: Edit .env file
Step 3: docker-compose up -d
The issue presents itself as a redirect to port 443 since it is using the default nginx.conf that is present within the nginx:latest container. That file is not set to import from /etc/nginx/conf.d so the file created via compose is never used. Manually editing the nginx.conf file and restarting nginx allows it to work.
Expected behavior
The expectation was for docker-compose to bring everything up and not require manual edits within the containers.
Observed behavior
The default.conf file is placed in the nginx container, but Nginx does not automatically load that configuration
The text was updated successfully, but these errors were encountered: