Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[docles]

Hi to all,
I run my JRiver MC 32 on an homelab.
Locally it works flawlessly.

I put a reverse proxy in front of the internal server.
I have a specific domain name music.xxxx.com to address the music from outside, let's encrypt certificate and the reverse proxy set up.

From outside, I can reach the server through music.xxxx.com. This reaches the MCWS pages and music can be read.

Unfortunalty no client (JRiver on a PC or Jremote3) can connect. I use the key of the server. The issue is that it searches by ip address (my access) and not the domain music.xxxx.com. Therefore the reverse proxy is blocking.
Do you have any advice?

Thanks for the support.

Docles

[JimH]

Your firewall needs to allow port 52199.

[docles]

Hi

Thanks for your reply.

I set up ufw allowing port 52125 on the jriver server.

Doesn't work.

Anything to do on the reverse proxy ?

[mwillems]

Hi

Thanks for your reply.

I set up ufw allowing port 52125 on the jriver server.

Doesn't work.

Anything to do on the reverse proxy ?

Have you tried not using the access key and just entering your domain name into the client instead of the access key?

[docles]

Hi thanks for your advice.
This is not working.

[mwillems]

Hi thanks for your advice.
This is not working.

Can you provide a little more information about what's not working?  Did you try adding the correct port after the domain name?

[zybex]

I don't think you need or should have a reverse proxy. The proxy expects incoming HTTP connections containing a header which describes the URL used to get there (the domain name). This works fine for MCWS, however a regular MC connection via the access key does NOT contain the domain name, it's a direct connection to your IP address - the proxy will just drop it if you have it configured to expect a domain name/virtual host.

You just need to set up NAT on your router to forward port 52199 or 52200 to your MC machine. A reverse proxy is needed for load balancing or to handle hosting multiple domains on the same machine, which is not the case.

Your firewall needs to allow port 52125.

Isn't that just for the Engen server?

[JimH]

Isn't that just for the Engen server?

My mistake.  It should have been 52199.  Corrected above.

[docles]

I don't think you need or should have a reverse proxy. The proxy expects incoming HTTP connections containing a header which describes the URL used to get there (the domain name). This works fine for MCWS, however a regular MC connection via the access key does NOT contain the domain name, it's a direct connection to your IP address - the proxy will just drop it if you have it configured to expect a domain name/virtual host.

You just need to set up NAT on your router to forward port 52199 or 52200 to your MC machine. A reverse proxy is needed for load balancing or to handle hosting multiple domains on the same machine, which is not the case.
Isn't that just for the Engen server?

I need a reverse proxy because I host several services aka subdomains. There is no way I can only count on port forwarding.

[docles]

Can you provide a little more information about what's not working?  Did you try adding the correct port after the domain name?

Yes, on the reverse proxy, I send to 52200 port on https.
I tried on 52199 on http too

The clients (JRiver on PC or JRemote on android) don't succeed to connect from outside.
I see that the JRiver is looking to the WAN IP address and not the subdomain.
I tried to enter the subdomain in the media library field. Does not accept.

[mwillems]

So previously there was a plan to support fully qualified domain names (FQDN) in the apps because you can't use SSL without using a FQDN, see Hendrik's comment in this thread:  https://yabb.jriver.com/interact/index.php/topic,110982.msg767049.html#msg767049

I thought it had been implemented, but maybe that never actually happened, in which case apologies for the wild goose chase.

It would be good if the clients could actually use HTTPS.

[Scobie]

Yeah RP needs the FQDN, but you could stand up a VPN between client and host? It could completely traverse the RP.

[docles]

so as far as I understand, FQDN is not implemented.
Any other suggestion to sort out ?

How to request the feature for future version?