SOLVED: Fast Reverse Proxy Rejects Connection

SOLVED: Fast Reverse Proxy Rejects Connection - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Fast Reverse Proxy Rejects Connection (/t-solved-fast-reverse-proxy-rejects-connection)

Fast Reverse Proxy Rejects Connection - Delta - 2024-11-12

I read the documentation, and there’s a section about using a Reverse Proxy for remote access. I’d like to use FRP (Fast Reverse Proxy). In other projects, TCP works properly.
My problem is that the connection was rejected. I tried to rule out FRPC/FRPS errors:

Jellyfin is accessible on the local network
Jellyfin is accessible from the FRPC container
Remote connections are enabled in Jellyfin’s network settings
According to FRPS, the HTTP proxy status is "Online"
I haven’t found any error-related logs

Here’s what the frpc.toml file looks like:

Code:
serverAddr = "serverIPAddress"

serverPort = 7000

[[proxies]]

name = "jellyfin-http"

type = "http"

localIP = "192.168...."

localPort = 8096

subdomain = "jellyfin"

customDomains = ["mydomain.com"]

Do you have any suggestions? Thank you in advance!

RE: Fast Reverse Proxy Rejects Connection - TheDreadPirate - 2024-11-12

Their documentation doesn't make clear what port FRP will use when you don't define a remote port. Does it just use port 80/443?

RE: Fast Reverse Proxy Rejects Connection - Delta - 2024-11-12

(2024-11-12, 10:18 PM)TheDreadPirate Wrote: Their documentation doesn't make clear what port FRP will use when you don't define a remote port. Does it just use port 80/443?

Yes. In FRPS, you need to set the vhostHTTPPort (80, 443) so that FRPC can use the HTTP type.

RE: Fast Reverse Proxy Rejects Connection - Delta - 2024-11-13

(2024-11-12, 10:40 PM)Delta Wrote:
(2024-11-12, 10:18 PM)TheDreadPirate Wrote: Their documentation doesn't make clear what port FRP will use when you don't define a remote port. Does it just use port 80/443?

Yes. In FRPS, you need to set the vhostHTTPPort (80, 443) so that FRPC can use the HTTP type.

UPDATE: As a test, I tried

set the vhost address to port 8096: the request is still being rejected
set Jellyfin InternalHttpPort and PublicHttpPort to 80: it doesn’t load even locally, so I had to revert to the original port in the network.xml file

RE: Fast Reverse Proxy Rejects Connection - Delta - 2024-11-15

UPDATE 2: I configured the TCP protocol alongside HTTP in FRPC.toml. On the FRPS interface, it is displayed as 'Online'.
I also set the JELLYFIN_PublishedServerUrl Docker environment variable to the following: http://jellyfin.domain.com.

However, I cannot connect to it either via the web interface or through the application. If anyone has any suggestions, I would greatly appreciate it. Thank you!

RE: Fast Reverse Proxy Rejects Connection - Delta - 2024-11-16

I solved the problem. I forgot to configure the necessary ports in the FRPS container...

By the way, I noticed on forums that many people use a TCP proxy. Does anyone have an idea why?

RE: Fast Reverse Proxy Rejects Connection - TheDreadPirate - 2024-11-16

TCP is the primary protocol that Jellyfin uses.

BTW, could you share the final configuration for FRPS? I think you are the only person I've seen try to use Jellyfin with it. This is also the first time I've heard of it, period.

Regarding TCP proxies, I don't recall anyone using a TCP proxy with Jellyfin. Only HTTP proxies like Nginx, Apache, Caddy, and Traefik.

RE: Fast Reverse Proxy Rejects Connection - AshipaEkO - 2024-12-24

Hello. could you please help me. trying to set this up

i think the server aspect is working. i can access the VPS ip:7500 to show me some sort of dashboard

but nothing else works

i'm running it with systemd

could you share your server and client config files with me (redacted of course)