Some users can't connect to hub

[metzeral]

We've been hosting JoinFS for our community for a little while. Seems like everything works nicely, as expected.
However, some users just can't connect for some reason. Plus, when connecting to an open hub, we can see that this specific user that could not connect to our own server had a kinda weird port such as "51XXX" or "61XXX".
We tried everything from uninstalling JoinFS and reinstalling it, re-hosting a new hub with different settings, but yet nothing.

Would appreciate the help,
Best regards.

[Peter]

Hi. It sounds very much as though they would benefit from enabling port forwarding on whatever routing hardware they have at their location. There are some link in the manual on how to set this up. Basically they need to configure the router that is actually connected to the internet to always use a specified port which links to their PC. By default JoinFS uses port 6112, which can be changed in the JoinFS settings. So you need to make sure the router is forwarding 6112 to the PC running JoinFS.

Peter

[Scage]

Hello,

Our JoinFS hub is hosted on a VPS. Is it possible that one of our members can't see it? if it is the router port is not good?

Our member sees all other hubs, but not ours.

We spent a lot of time looking for a solution yesterday.

Are we unable to configure anything on our side?
as I see that it manages to join other hubs...

Thank you again for your help.

[Peter]

In order for the hub to be seen there needs to be a valid internet IP address with a port that is somehow routed to the PC running JoinFS. Normally with a home router this happens automatically when connecting outwards, but will need some configuration to allow people connecting inwards. Not sure if a VPS will make any difference as long as traffic has a way of going both ways on a UDP port.

When testing a new hub it is best to ignore the hub list for the moment and just see if you can get other people connecting to the IP address where the hub is located. If that doesn't work then they won't be able to join via the hub list. Using command line tools like 'ping' can help to see if an address is visible to others.

Peter

[metzeral]

In order for the hub to be seen there needs to be a valid internet IP address with a port that is somehow routed to the PC running JoinFS. Normally with a home router this happens automatically when connecting outwards, but will need some configuration to allow people connecting inwards. Not sure if a VPS will make any difference as long as traffic has a way of going both ways on a UDP port.

When testing a new hub it is best to ignore the hub list for the moment and just see if you can get other people connecting to the IP address where the hub is located. If that doesn't work then they won't be able to join via the hub list. Using command line tools like 'ping' can help to see if an address is visible to others.

Peter

All right, will ask the user to do a 'ping' to the IP.
Tho when testing, he couldn't even join the Hub by using directly the IP instead of trying to find it in the hub list.
I would believe that this issue is more of a client-side than a server-side issue, as the VPS authorizes connection for all JoinFS common ports (6112-6114).

Thank you again for the help,
In hope that we'll resolve the issue somehow.

Metzeral.

[metzeral]

In order for the hub to be seen there needs to be a valid internet IP address with a port that is somehow routed to the PC running JoinFS. Normally with a home router this happens automatically when connecting outwards, but will need some configuration to allow people connecting inwards. Not sure if a VPS will make any difference as long as traffic has a way of going both ways on a UDP port.

When testing a new hub it is best to ignore the hub list for the moment and just see if you can get other people connecting to the IP address where the hub is located. If that doesn't work then they won't be able to join via the hub list. Using command line tools like 'ping' can help to see if an address is visible to others.

Peter

All right, will ask the user to do a 'ping' to the IP.
Tho when testing, he couldn't even join the Hub by using directly the IP instead of trying to find it in the hub list.
I would believe that this issue is more of a client-side than a server-side issue, as the VPS authorizes connection for all JoinFS common ports (6112-6114).

Thank you again for the help,
In hope that we'll resolve the issue somehow.

Metzeral.

Using the 'ping' command, we were able to confirm the user can communicate to the VPS.
I would then assume that the issue is indeed port-related and that the user would need to forward the port.
Too bad we cannot access the source code, this would have helped us a lot to understand how exactly JoinFS works.

Anyhow, thanks for taking the time to help us!

Metzeral