504 Gateway Timeout error without configuration changes (ref#1RBRTM)

[Omar_Chaudhry]

Hi! What’s not quite right with Roon?

· Can’t reach my Server, remotes or ARC

Can’t connect to my Server, remotes or ARC

· Other ARC issues

Tell us what's going on

· Looks like I’m suddenly getting a 504 Gateway Timeout error despite not making any changes to my configuration.

Tell us about your home network

· My setup at home is the FiOS ONT to EdgeRouter 5 POE to Netgear Orbi RBR20. Again I haven’t changed anything in months.

[benjamin]

Hey @Omar_Chaudhry,

Thanks for writing in and for sharing your report! From your error code, it looks like the protocols that configure port forwarding automatically are either not available or have failed. UPnP and NATPMP are not functioning in your router as Roon expects. 

See if any of the below help:

• Turn on UPnP on your router and try to run Roon's port forwarding test again.
• Try to set up manual port forwarding in your router.
  • Make sure the IP/Port matches in any port forwarding rule you create.
• Double-check to make sure you don't have any VPNs, Firewalls, or other network filtering software blocking Roon.
• Check if your modem is in Bridge mode.
• Restart your network hardware and update firmware.

Thank you!

[Omar_Chaudhry]

I think I’m set up correctly. Again, no changes on my part.

[Omar_Chaudhry]

@benjamin Any ideas?

[vadim]

Hi @Omar_Chaudhry,

Looking at your screenshots, your two routers appear to be on different subnets (192.168.1.x and 192.168.2.x), which suggests a double NAT situation. Before we advise on a fix, could you confirm the following IP addresses?

1. EdgeRouter WAN IP — the IP assigned to its WAN interface (eth0)
2. EdgeRouter LAN IP — its own LAN address (usually the gateway for the 192.168.2.x subnet)
3. Orbi WAN IP — the IP assigned to its WAN/Internet port
4. Orbi LAN IP — its own LAN address (gateway for the 192.168.1.x subnet)
5. Roon Server IP — the actual IP of the machine running Roon Server

Your Orbi is forwarding port 55002 to 192.168.1.195, but your EdgeRouter is forwarding to 192.168.2.135. These are different subnets — traffic arriving at the Orbi gets forwarded to the EdgeRouter, but then the EdgeRouter needs to forward it again to the actual Roon Server machine.

** Missing destination port on EdgeRouter** — The “Forward to port” field on your EdgeRouter rule appears to be empty. Make sure it’s set to 55002.

This will help us map out the full path traffic takes from the internet to your Roon Server and pinpoint exactly where the forwarding is breaking.

[Omar_Chaudhry]

So I added 55002 to the destination port on the EdgeRouter, but I don’t see anything forwarding to x.x.1.195. The traffic should go:

• EdgeRouter
  • to Orbi - 192.168.2.135:55002
• Orbi
  • to Mac mini - 192.168.1.105:55002

[Omar_Chaudhry]

Don’t know why this worked, but I changed the port top 55003 everywhere and…voila! It’s working.

[vadim]

Hi @Omar_Chaudhry,

Glad it’s working! The reason port 55003 worked is that something else on your Mac mini was already occupying port 55002, preventing Roon from binding.

Happy listening!