Port ... is not reachable from the internet

[Gert-Vanhaerents]

Hi,
I have the following error when i try to set dayon assestent to listen (play icon).

Port 8080 is not reachable from the internet.
Connections with peers outsite your netwerk rely on their ability to forward the port 8080.
This option is only available if the peer connects using a token.
OK

The port 8080 is linked to my computer, it's forwarded to my IP adres.
When i don't forward the port 8080 to my computer i don't have this error.
When i do a online port check, the say that port 8080 is not open.

What do i wrong? Or how can i resolf it?

Br
Gert

[RetGal]

Hi, on which OS the assistant running? And is UPnP enabled on the router or not?

For the connection check, the assistant opens a server socket and tries to connect to it using its public IP address.
Is it possible that a firewall is blocking access? Have you tried using a different port?

[Gert-Vanhaerents]

Hi, thanks for the answer, TCP and UPnP are enabled on the router.
The os i am working is Linux Mint 22.2
No firewall

[Gert-Vanhaerents]

I see it's not UPnP but UDP that's enabled. No sign of UPnP seen in the router.
When i start Dayon assistent and click on the play buttom:
Port 8485 is not reachable from the internet.
Connections with peers outside your network rely on their ability to forward the port 8485.
This option is only available if the peer connects using a token.

On the assisted side:
two geen dots; but : Connection was refused by (my internet ip adres).

And now, after 3 times try: it works fine.
But what will be the problem? So the ports are good (also because i have the error when i start), but the most times it can not connect.

[RetGal]

Ok, that's a pretty odd behaviour indeed!

I refactored the request token method a bit and created a snapshot version for you.
If you got the time, you could either rename the file to dayon.jar or run it directly with:
java -jar dayon.jar.txt assistant
(runs the Assistant side)

dayon.jar.txt

[Gert-Vanhaerents]

Sorry for the delay, i was on vacation. So i have tested with this snapshot. The first time it was working, (but the mouse cursor moves slow). The second time it wasn't working anymore. "Connections refused by ... the assistant" but don't have a change to click accept or OK to accept it.

[RetGal]

Ok, that's still rather odd:

• If UPnP is not activated and the Assistant detects that its port is not reachable from the outside, it should display ''Detecting the peer status" on the bottom left corner after you click the "Start" button.
  The Assisted should display two red dots and "Connecting to..." after the token has been entered. If on the network of the Assisted side UPnP is also disabled, a connection will not be possible. (this may change in future versions, but right now it's not possible)
• If UPnP is activated or the port is forwarded to the Assistant private IPv4 address, then both dots of the Assistant should turn green after clicking the "Start" button. And no warning should be displayed of course.

Under 'Settings > Network' there is an option 'Auto accept connections'. Once activated, you no longer need to manually accept incoming connections - but this alone won't solve this particular problem..

[Gert-Vanhaerents]

I have tested again and again, but it's not working. With the snapshot version i can see (on the assistant side) Dayon! server [port:8485] .... Accepting ... but nothing is hapening. I have set the option 'Auto accept connections'.

I've used Dayon extensively in the past, but it's currently just not good. How can I troubleshoot this? Or can you help me identify and fix it?
I can also give screenshots of the settings in my router, but i don't want to place it public for security reasons. So can i mail you with the screenshots or dayon log files?

[RetGal]

As the behavior observed behavior is really odd: Have you already tried to "reboot" your router? Maybe it is in some kind of weird limbo state?

Another thing to try would be to connect without using a token:
Start the Assistant directly with the "play" button without prior click on the "Create and copy a new access token".
Let the Assisted enter the public IP and the port of the Assistant. Described in detail under https://retgal.github.io/Dayon/quickstart.html#assistant-setup - Section "Alternative: connect without token"

To enable the (extensive) debugging, the string debug can be appended to the command:

• Assisted: java -jar dayon.jar debug
• Assistant: java -jar dayon.jar assistant debug

The log files are located in the ~/.dayon directory. Feel free to directly send them to reto at galante dot ch for further analysis.

[Uffi64]

Hallo all together,

I know it's some time later now, but I faced the same behaviour and found (at least for my setup) a solution.

Th DayOn Assistand is running here on a Windows 2022 Terminalserver. The firewall which has to handle the port forwarding (natting) is a pfSense 8.1.
I configured the normal natting ther as I am used to it from forwarding 443 for HTTPS or 22 for SSH. But the Port for DayOn wouldn't work.
I always got the message "Port not reachable from the internet" and the client always got the message "Connection declined by xxx.xxx.xxx.xxx"

I was struggling a lot to find out where the problem is. Finally I found out, that I could do something on the natting configuration on the pfSense to make it work constantly:

At the Natting-Rule I set the Option "NAT reflection" from Use system default to Enable (NAT + Proxy)

From then on it works like a charm.