[GH-ISSUE #3017] Peer's port 80 and 443 blocked #6289

Open
opened 2026-08-05 01:07:37 -04:00 by saavagebueno · 9 comments
Owner

Originally created by @pinionless on GitHub (Dec 10, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3017

Originally assigned to: @nazarewk on GitHub.

This issue is closed, but was not fixed.
https://github.com/netbirdio/netbird/issues/2701
The ports are still blocked.

I route this network 192.168.1.0/24 via netbird.

I can not access 80 and 443 on the machine with netbird installed on 192.168.1.10
But I can access 80 and 443 on other machines inside this network.

Downgraded to 0.29.4 for now.

Originally created by @pinionless on GitHub (Dec 10, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3017 Originally assigned to: @nazarewk on GitHub. This issue is closed, but was not fixed. https://github.com/netbirdio/netbird/issues/2701 **The ports are still blocked.** I route this network 192.168.1.0/24 via netbird. I can not access 80 and 443 on the machine with netbird installed on 192.168.1.10 But I can access 80 and 443 on other machines inside this network. Downgraded to 0.29.4 for now.
saavagebueno added the triage-needed label 2026-08-05 01:07:37 -04:00
Author
Owner

@nimdasx commented on GitHub (Jan 16, 2025):

Confirmed: This issue persists in version 0.35.2, any docker external port can't accessible

<!-- gh-comment-id:2594964599 --> @nimdasx commented on GitHub (Jan 16, 2025): Confirmed: This issue persists in version 0.35.2, any docker external port can't accessible
Author
Owner

@lixmal commented on GitHub (Jan 17, 2025):

Hey folks,

Can you try the binary (on the bottom) from this PR: https://github.com/netbirdio/netbird/actions/runs/12832923467, to see if it fixes the issue for you?

<!-- gh-comment-id:2598743863 --> @lixmal commented on GitHub (Jan 17, 2025): Hey folks, Can you try the binary (on the bottom) from this PR: https://github.com/netbirdio/netbird/actions/runs/12832923467, to see if it fixes the issue for you?
Author
Owner

@nimdasx commented on GitHub (Jan 20, 2025):

Hi, I've tested version 0.36.2-SNAPSHOT-b0c8124a and 0.36.5. Docker container ports are still blocked.

<!-- gh-comment-id:2601504379 --> @nimdasx commented on GitHub (Jan 20, 2025): Hi, I've tested version 0.36.2-SNAPSHOT-b0c8124a and 0.36.5. Docker container ports are still blocked.
Author
Owner

@nimdasx commented on GitHub (Feb 24, 2025):

The problem still exists in version 0.37.1

<!-- gh-comment-id:2680085490 --> @nimdasx commented on GitHub (Feb 24, 2025): The problem still exists in version 0.37.1
Author
Owner

@artivis commented on GitHub (Mar 14, 2025):

This seems to still be a problem 0.38.0

<!-- gh-comment-id:2725418279 --> @artivis commented on GitHub (Mar 14, 2025): This seems to still be a problem 0.38.0
Author
Owner

@nazarewk commented on GitHub (Mar 17, 2025):

Could you give us more details on the issue?

  1. What operating system are you running on client and the forwarder?
  2. Do you have IP forwarding enabled? see https://docs.netbird.io/how-to/troubleshooting-client#can-a-routing-peer-peer-b-forward-traffic-to-srv-c
  3. Did you try different client machines?
  4. Are you sure your operating system's firewall is not interfering with packet forwarding?
  5. Do you have a bidirectional ACL policy? see https://docs.netbird.io/how-to/configuring-routes-with-access-control#behavior-changes-in-version-0-30-0
  6. Is it possible to replicate the issue on a fresh setup? Can you share the steps?
<!-- gh-comment-id:2729154299 --> @nazarewk commented on GitHub (Mar 17, 2025): Could you give us more details on the issue? 1. What operating system are you running on client and the forwarder? 2. Do you have IP forwarding enabled? see https://docs.netbird.io/how-to/troubleshooting-client#can-a-routing-peer-peer-b-forward-traffic-to-srv-c 2. Did you try different client machines? 3. Are you sure your operating system's firewall is not interfering with packet forwarding? 4. Do you have a bidirectional ACL policy? see https://docs.netbird.io/how-to/configuring-routes-with-access-control#behavior-changes-in-version-0-30-0 5. Is it possible to replicate the issue on a fresh setup? Can you share the steps?
Author
Owner

@artivis commented on GitHub (Apr 2, 2025):

Sorry for the late reply,

  1. Ubuntu (22.04/24.04)
    2/3/4. yes
  2. There was the default all to all . I did try to add a network route and associated ACL but not luck.
  3. Nop I can't share that specific setup at the moment. But it is somewhat similar to those described in other issues: a containerized reverse proxy listen to port 80 and forwards to different service in a k8s subnet.

It is definitely related to the changes introduced in 0.30.x, and setting up a network route + acl doesn't fix it.
Similarly to others, I reverted to 0.29.x which works just fine.

<!-- gh-comment-id:2771967225 --> @artivis commented on GitHub (Apr 2, 2025): Sorry for the late reply, 1. Ubuntu (22.04/24.04) 2/3/4. yes 5. There was the default all to all . I did try to add a network route and associated ACL but not luck. 6. Nop I can't share that specific setup at the moment. But it is somewhat similar to those described in other issues: a containerized reverse proxy listen to port 80 and forwards to different service in a k8s subnet. It is definitely related to the changes introduced in 0.30.x, and setting up a network route + acl doesn't fix it. Similarly to others, I reverted to 0.29.x which works just fine.
Author
Owner

@nazarewk commented on GitHub (Apr 2, 2025):

Could you try setting the same up with a Network Resource instead of the Network Route?

<!-- gh-comment-id:2773471505 --> @nazarewk commented on GitHub (Apr 2, 2025): Could you try setting the same up with a Network Resource instead of the Network Route?
Author
Owner

@nimdasx commented on GitHub (Apr 23, 2025):

tested in version 0.41.3 its worked! thanks

<!-- gh-comment-id:2823682507 --> @nimdasx commented on GitHub (Apr 23, 2025): tested in version 0.41.3 its worked! thanks
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#6289