External Connection Issues

[Radtech81951 2]

@Luke

So after using chatgpt extensively, it came to the following conclusion..

Port forwarding is configured correctly with a reserved IP. canyouseeme.org can connect to the forwarded port, TCP sessions establish, but HTTP traffic never completes. The same server works immediately when the GFiber router is placed in bridge mode and the Netgear R9000 performs NAT and port forwarding instead.

I messaged Gfiber support and got this response. Once I receive the new router next week, then I'll update if the issue has been solved.

The behavior you are describing—where a TCP handshake completes successfully but the application-layer HTTP traffic stalls or drops—is a known issue that typically points to how the GFiber router's built-in firewall or security firmware handles specific packet inspection, or a potential issue with the Maximum Transmission Unit (MTU) size stripping HTTP headers.

Agent 4:06:26 PM

Since you are on a 3Gbps plan, a firmware glitch on the GR6EXX0C model shouldn't throttle your setup. I can initiate an exchange for your current router. - We can swap your Wi-Fi 6E router for our newer Wi-Fi 7 Multi-Gig Router. - This will completely bypass the specific firmware bug present on your current device, handle your 3Gbps speeds natively, and allow you to manage your port forwarding cleanly without relying on your legacy Netgear R9000.

 

[Luke 42745]

On 7/10/2026 at 5:29 PM, Radtech81951 said:

@Luke

So after using chatgpt extensively, it came to the following conclusion..

Port forwarding is configured correctly with a reserved IP. canyouseeme.org can connect to the forwarded port, TCP sessions establish, but HTTP traffic never completes. The same server works immediately when the GFiber router is placed in bridge mode and the Netgear R9000 performs NAT and port forwarding instead.

I messaged Gfiber support and got this response. Once I receive the new router next week, then I'll update if the issue has been solved.

The behavior you are describing—where a TCP handshake completes successfully but the application-layer HTTP traffic stalls or drops—is a known issue that typically points to how the GFiber router's built-in firewall or security firmware handles specific packet inspection, or a potential issue with the Maximum Transmission Unit (MTU) size stripping HTTP headers.

Agent 4:06:26 PM

Since you are on a 3Gbps plan, a firmware glitch on the GR6EXX0C model shouldn't throttle your setup. I can initiate an exchange for your current router. - We can swap your Wi-Fi 6E router for our newer Wi-Fi 7 Multi-Gig Router. - This will completely bypass the specific firmware bug present on your current device, handle your 3Gbps speeds natively, and allow you to manage your port forwarding cleanly without relying on your legacy Netgear R9000.

 

OK please keep us posted. Thanks !

[Radtech81951 2]

@Luke , it didn't work. Now canyouseeme.org can't see the open port after setting up port forwarding rules on the new router. I have an escalation case with GFiber. I've seen some posts about cloudflare or wireguard tunnels. Would these help bypass the issues I'm having? If so, is there a post on the forum on how to set these up? I'd like to use something that is low cost for me, and my invited emby users don't have to pay for or download anything.

 

[tedfroop21 99]

2 hours ago, Radtech81951 said:

I've seen some posts about cloudflare or wireguard tunnels

......or Tailscale. Quick and easy.  Set it up on your devices, connect to Tailscale ip address for your emby server, done. 

Edited 1 hour ago by tedfroop21