Nginx代理传递不。。。没有什么？

使用Ubuntu服务器20.04，nginx/1.18.0（Ubuntu）

值得一提的是，我正在尝试使用远程访问设置Jellyfin。我也在使用动态域名。我有一个nextcloud服务，它使用类似的ish设置完全启动并运行。我还希望服务器可以远程访问

当我访问我的域名时，它只会将我带到NGINX欢迎页面。我已将其从site enabled中删除，并已禁用default.conf listen标记（并重命名文件default.conf.bak）

本质上，当我输入域名时，它应该自动重定向到正确的端口。没有

我可以使用ip地址和jellyfin的端口访问服务器。但使用域名或ip地址只会让我进入欢迎屏幕。我使用域名主要是因为我有其他服务也使用端口80

我可以在本地ip上访问Jellyfin站点，而无需端口

我尝试过其他地方的一些技巧，包括编辑hosts文件以确保域名链接到127.0.0.1，但我有点不知所措

访问或错误日志中没有任何内容

我还检查了nginx.conf中是否有任何服务器块，没有。这是我正在使用的文件。。。（这实际上是来自Jellyfin站点的复制粘贴）

---

好的，关键是这涉及到两台机器。所以转发没有按预期工作。我相信它需要重定向，而不是简单的传递，并且在端口80上侦听不会发生。路由器不知道应该将信息发送到哪里

安装了Jellyfin的一个关键问题是，主机上似乎不需要conf文件，因为它当前应该在8080上侦听，但Jellyfin在8096上侦听

如果有人愿意提供专家意见来填补空白，我们将不胜感激。谢谢大家的帮助

无论如何，下面是我的反向代理配置文件

# Reverse proxy on forwarding machine.                                               
server {
        server_name domainname.eu;

        # Not sure if this is required, it's purpose was to see where /
        # the nginx page was being served from it wasn't the client as thought.
        root /usr/share/nginx/test; 

        location / {
                proxy_pass http://192.168.1.2:8096$request_uri;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header Host $host;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_redirect http://192.168.1.2:8096$request_uri http://domainname.eu;
        }

    # The certbot action has to be done on the forwarding machine not \
    # the hosting machine. Any attempt to run it on the host fails. \
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/domainname.eu/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/domainname.eu/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot


    add_header Strict-Transport-Security "max-age=31536000" always; # managed by Certbot


    ssl_trusted_certificate /etc/letsencrypt/live/domainname.eu/chain.pem; # managed by Certbot
    ssl_stapling on; # managed by Certbot
    ssl_stapling_verify on; # managed by Certbot

}
server {
    if ($host = domainname.eu) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


        listen 80;
        server_name domainname.eu;
        root /usr/share/nginx/test;

        location / {
                proxy_pass http://192.168.1.2:8096$request_uri;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header Host $host;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_redirect http://192.168.1.2:8096$request_uri http://domainname.eu;
        }
}

---

这里希望它能在将来帮助一些人。

端点是否按预期工作？代理是否将我带到端口8096？没有，nginx正在运行吗？sudo nginx-s reload的输出是什么

# Reverse proxy on forwarding machine.                                               
server {
        server_name domainname.eu;

        # Not sure if this is required, it's purpose was to see where /
        # the nginx page was being served from it wasn't the client as thought.
        root /usr/share/nginx/test; 

        location / {
                proxy_pass http://192.168.1.2:8096$request_uri;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header Host $host;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_redirect http://192.168.1.2:8096$request_uri http://domainname.eu;
        }

    # The certbot action has to be done on the forwarding machine not \
    # the hosting machine. Any attempt to run it on the host fails. \
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/domainname.eu/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/domainname.eu/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot


    add_header Strict-Transport-Security "max-age=31536000" always; # managed by Certbot


    ssl_trusted_certificate /etc/letsencrypt/live/domainname.eu/chain.pem; # managed by Certbot
    ssl_stapling on; # managed by Certbot
    ssl_stapling_verify on; # managed by Certbot

}
server {
    if ($host = domainname.eu) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


        listen 80;
        server_name domainname.eu;
        root /usr/share/nginx/test;

        location / {
                proxy_pass http://192.168.1.2:8096$request_uri;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header Host $host;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_redirect http://192.168.1.2:8096$request_uri http://domainname.eu;
        }
}