Stuck at "Wating to resolve connection!"

[Snogard]

Describe the bug
Both client and host don't go beyond "Waiting to resolve connection!"

To Reproduce
Steps to reproduce the behavior:

1. Download on Archlinux (host)
2. Download on Winows 11 (client)
3. Setup easy connect server on Arch with podman and port 15000
4. connect using the easy connect server by static_ip:15000

Expected behavior
It's my first time using the program, i suppose the stream should start in a few seconds?

Screenshots
none

Desktop (please complete the following information):

• OS: Windows client

• Version 11

• OS: Archlinux host

• Version latest

Browser (please complete the following information):

• Device: My pc
• OS: Archlinux
• Browser chromium
• Version 143.0.7499.192

Additional context
The easy connect server properly received connections from client and host

[PiterWeb]

Hi @Snogard, thank you for opening this issue.

I need some more info:

• Are you on LAN? If yes, have you tried the LAN mode chechbox?
• Have you modified STUN/TURN servers? If yes, you have exactly the same servers in both?
• Any of the devices is using mobile/public/company network?

Setup easy connect server on Arch with podman and port 15000

If you want, you can use the easy connect server that is bundled in the host app, you can configure the port by CLI, if you use --help you can see all args, by default uses the port that is in the placeholder (I think it is 8081).

connect using the easy connect server by static_ip:15000

You can also use .local domains instead of a static ip, I think you can find it useful.

[Snogard]

The behaviour i described was tested either with LAN and WAN connection and both were tested either by having "lan mode" enabled and disabled.
Every test, i restarted the application on both client and host.
LAN testing was done through zerotier.
No modification was done to the TUN/STUN servers.
Client and Host are in two distinct home networks.

If you want, you can use the easy connect server that is bundled in the host app, you can configure the port by CLI, if you use --help you can see all args, by default uses the port that is in the placeholder (I think it is 8081).

I'll try this in a few days

[PiterWeb]

LAN testing was done through zerotier.

I think LAN trough services like zerotier might need some aditional configuration on firewalls for udp/tcp ports used by WebRTC.

Client and Host are in two distinct home networks.

Looks strange that can't connect between home networks, maybe if you open in another tab chrome://webrtc-internals when you try to connect as a client you can see some reason of why it fails.

You can also try to use the console of chrome developer tools, or the generated LibreRemotePlay.log file that is generated in the same folder where LibreRemotePlay is placed to get some log that can identify the problem.

[Snogard]

i'm sorry, but i'm not able to test for the time being, i don't know when i'll be able to.
I'll post the results here as soon as i get the chance.