data-catalog-services/WebHosting_DMZ
0
0 Fork 0
forked from linux/WebHosting_DMZ
Code Pull Requests 1 Actions Activity

force hostanme resolution for scicat-rocrate services

Browse Source 
The traffic between prod and qa seems to be mixed up sometimes, from
what I read nginx only resolves hostnames at startup when using
literals.
This should force frequently resolving the hostnames
This commit is contained in:
fpotier authored and potier_f committed 2026-10-05 15:02:30 +02:00
1 parent 09336df51a
commit e27369cfa1
2 files changed
+8 -2
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

conf.d/scicat-rocrate-qa.conf
+4 -1
View File
@@ -13,8 +13,11 @@ server {
ssl_certificate /etc/nginx/certs/lx-docker-dmz-01.psi.ch.crt;
ssl_certificate_key /etc/nginx/private/lx-docker-dmz-01.psi.ch.key;
resolver 127.0.0.11 valid=10s ipv6=off;
location / {
proxy_pass http://scicat-rocrate-qa:8080;
set $backend http://scicat-rocrate-qa:8080;
proxy_pass $backend;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
conf.d/scicat-rocrate.conf
+4 -1
View File
@@ -13,8 +13,11 @@ server {
ssl_certificate /etc/nginx/certs/lx-docker-dmz-01.psi.ch.crt;
ssl_certificate_key /etc/nginx/private/lx-docker-dmz-01.psi.ch.key;
resolver 127.0.0.11 valid=10s ipv6=off;
location / {
proxy_pass http://scicat-rocrate:8080;
set $backend http://scicat-rocrate:8080;
proxy_pass $backend;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;