There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

[solved] Nginx proxy server - strange behavior

Hello fellow selfhosters! I changed my server OS from fedora server to alma linux as I wanted a more stable base with less frequent updates for my docker containers, so I backed everything up and installed almalinux. It all went smoothly, and now all the containers seem to work as before except for nginx proxy manager: on fedora, I set all the proxy hosts like this (using jellyfin for instance): jellyfin.mydomain.duckdns.org > http://myserverhostname:8096now, for some strange reasons, it does not work anymore, and I get a bad gateway error. I tried with and without SSL (that I had from the previous installation, do I need to regenerate them? but without it should work anyway…), pointing to localhost:8096, to myserverhostname:8096, to jellyfin:8096, but nothing. The only way I could make it work was with the resolved IP address of my server:


<span style="font-style:italic;color:#969896;"># host myserverhostname
</span><span style="color:#323232;">myserverhostname.station has address 192.168.1.13
</span>

pointing nginx to 192.168.1.13:8096 correctly shows the website. why does this happens? am I doing something wrong?

EDIT: the only one that’s working with localhost is nginx itself (http://localhost:81)

======

SOLUTION: instead of myserverhostname, in nginx proxy host configuration (in the gui) I had to set myserverhostname.station to get it working. I don’t know why, in the previous installation only the hostname was enough…

Oisteink ,

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

tubbadu OP ,

how can I find out more about this?

Oisteink ,

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 ,

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:


<span style="color:#323232;">[root@docker-11e3869f946f:/app]# host tserver
</span><span style="color:#323232;">Host tserver not found: 3(NXDOMAIN)
</span>

(I had to install dnsutils before)

it seems a nginx issue then

Oisteink ,

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 ,

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 ,

here’s the configuration file for jellyfin:


<span style="color:#323232;"># ------------------------------------------------------------
</span><span style="color:#323232;"># jellyfin.tubbadu.duckdns.org
</span><span style="color:#323232;"># ------------------------------------------------------------
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">map $scheme $hsts_header {
</span><span style="color:#323232;">https   "max-age=63072000; preload";
</span><span style="color:#323232;">}
</span><span style="color:#323232;">
</span><span style="color:#323232;">server {
</span><span style="color:#323232;">set $forward_scheme http;
</span><span style="color:#323232;">set $server         "192.168.1.13";
</span><span style="color:#323232;">set $port           8096;
</span><span style="color:#323232;">
</span><span style="color:#323232;">listen 80;
</span><span style="color:#323232;">listen [::]:80;
</span><span style="color:#323232;">
</span><span style="color:#323232;">listen 443 ssl;
</span><span style="color:#323232;">listen [::]:443 ssl;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">server_name jellyfin.tubbadu.duckdns.org;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;"># Let's Encrypt SSL
</span><span style="color:#323232;">include conf.d/include/letsencrypt-acme-challenge.conf;
</span><span style="color:#323232;">include conf.d/include/ssl-ciphers.conf;
</span><span style="color:#323232;">ssl_certificate /etc/letsencrypt/live/npm-18/fullchain.pem;
</span><span style="color:#323232;">ssl_certificate_key /etc/letsencrypt/live/npm-18/privkey.pem;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;"># Block Exploits
</span><span style="color:#323232;">include conf.d/include/block-exploits.conf;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">proxy_set_header Upgrade $http_upgrade;
</span><span style="color:#323232;">proxy_set_header Connection $http_connection;
</span><span style="color:#323232;">proxy_http_version 1.1;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">access_log /data/logs/proxy-host-5_access.log proxy;
</span><span style="color:#323232;">error_log /data/logs/proxy-host-5_error.log warn;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">location / {
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">proxy_set_header Upgrade $http_upgrade;
</span><span style="color:#323232;">proxy_set_header Connection $http_connection;
</span><span style="color:#323232;">proxy_http_version 1.1;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;"># Proxy!
</span><span style="color:#323232;">include conf.d/include/proxy.conf;
</span><span style="color:#323232;">}
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;"># Custom
</span><span style="color:#323232;">include /data/nginx/custom/server_proxy[.]conf;
</span><span style="color:#323232;">}
</span>
Decronym Bot , (edited )

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 for this sub, first seen 28th Jan 2024, 18:55] [FAQ] [Full list] [Contact] [Source code]

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •