[solved] Nginx proxy server - strange behavior

Decronym Bot , 5 months ago (edited 5 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters	More Letters
HTTP	Hypertext Transfer Protocol, the Web
SSL	Secure Sockets Layer, for transparent encryption
nginx	Popular HTTP server

---

2 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.

[Thread #459 for this sub, first seen 28th Jan 2024, 18:55]
[FAQ] [Full list] [Contact] [Source code]

Oisteink , 5 months ago

As you can forward by ip but not by name it sounds like resolver issue.

tubbadu OP , 5 months ago

how can I find out more about this?

Oisteink , 5 months ago

On the host of the nginx rev proxy or in nginx config files.
Something seems to block the lookup from name to ip, as ip works you know the proxy works.
Check dns config and nginx config on that host

tubbadu OP , 5 months ago

on the server host myserverhostname correctly resolves, but if I enter the container (docker exec -it nginx-app-1 bash) it does not work anymore:

[root@docker-11e3869f946f:/app]# host tserver
Host tserver not found: 3(NXDOMAIN)

(I had to install dnsutils before)

it seems a nginx issue then

Oisteink , 5 months ago

Could also be docker network-config.
Docker should by default use the hosts resolver config if there’s nothing in /etc/resolve.conf

You can also supply dns server on the docker command or in your compose file if you’re using compose.

As a last resort you can enter server and ip i the container’s /ets/host file if the ip is static. But that’s gone once you rebuild the image.

Or maybe there’s env on the container you use for dns

tubbadu OP , 5 months ago

I found a solution: use myserverhostname.station instead of just the hostname. I really have no idea why, on the previous installation it worked well with just the hostname... ahh, whatever.

thank you very much for the help!

tubbadu OP , 5 months ago

here's the configuration file for jellyfin:

# ------------------------------------------------------------
# jellyfin.tubbadu.duckdns.org
# ------------------------------------------------------------



map $scheme $hsts_header {
https   "max-age=63072000; preload";
}

server {
set $forward_scheme http;
set $server         "192.168.1.13";
set $port           8096;

listen 80;
listen [::]:80;

listen 443 ssl;
listen [::]:443 ssl;


server_name jellyfin.tubbadu.duckdns.org;


# Let's Encrypt SSL
include conf.d/include/letsencrypt-acme-challenge.conf;
include conf.d/include/ssl-ciphers.conf;
ssl_certificate /etc/letsencrypt/live/npm-18/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/npm-18/privkey.pem;






# Block Exploits
include conf.d/include/block-exploits.conf;








proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


access_log /data/logs/proxy-host-5_access.log proxy;
error_log /data/logs/proxy-host-5_error.log warn;







location / {








proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


# Proxy!
include conf.d/include/proxy.conf;
}


# Custom
include /data/nginx/custom/server_proxy[.]conf;
}