No Incoming Connections! Are your ports open?

[Deelux]

What is the bug?
I don't think it's a bug but I have tried all I could find online all without success. So I'm here asking the community if they have any idea how to fix this challenge:
After installing the bubble app and running the farcaster node, everything is working but the Inbound Sync Attempts.

I have double checked and when I run "sudo ufw allow 2283/tcp" it says: "Skipping adding existing rule. Skipping adding existing rule (v6)."

Does anyone have any idea how to fix this?

How can it be reproduced? (optional)
I'm running a VPS on Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-105-generic x86_64)

Any help is greatly appreciated.

Additional context (optional)
Add any other context about the problem here.

[hfyr7vbnusdjk]

I have the same message most of the time, but sometimes I see there 1 like now

[Deelux]

I thought to check when I saw your reply and I have the same currently. I'm also at 1.

Not sure if this is the "normal" amount or if it should be much higher... Either way thanks so much for taking time to reply. <3

[sds]

Hey @Deelux, without more context about the environment you're running it's difficult to help.

It's important to note that inbound sync attempts don't prevent your hub from operating correctly—it just prevents your hub from being able to share data with other hubs on the global network, but it can still find other hubs and get data from them.

A common issue is that Hubble requires BOTH ports 2282 and 2283 exposed in order to receive inbound traffic. Just one or the other is not enough.

Exposing via IP tables (like you do in sudo ufw allow 2283/tcp) may not be enough. You need to make sure that the VPS itself allows traffic from the public internet to ports 2282 and 2283 (cloud providers refer to this concept as security groups, ingress rules, etc.)

I'm going to close this issue for now. There are other issues you can consult, e.g.

• bug (hubble):No peers or incoming gossip connections #2041
• Port 2283 error #2061

For context on why this warning was introduced in the first place:

• bug(hubble): hubs can start with unreachable ports #1157