Yatse android does not know how to work on vpn which is configured on the system where kodi is running

Support Solved
1

Kodi is installed on a system with a vpn server and I sometimes need yatse android running via vpn connected to the server with Kodi running.
When sending file from yatse android app to kodi with vpn connected. Yatse sends the wrong ip of the android device on which yatse is installed. I took this log from tcpdump.

172.16.0.20.49559 > 172.16.0.1.8080: Flags [P.], cksum 0xd636 (correct), seq 11421:12250, ack 11312, win 432, options 
[nop,nop,TS val 12291460 ecr 1698060520], length 829: HTTP, length: 829
POST /jsonrpc HTTP/1.1
Content-Type: application/json; charset=utf-8
Content-Length: 639
Host: 172.16.0.1:8080
Connection: Keep-Alive
Accept-Encoding: gzip
User-Agent: okhttp/4.9.1

{"id":253,"jsonrpc":"2.0","method":"Addons.ExecuteAddon","params":{"params":{"mime_type":"image/jpeg","thumbnail":"http%3A%2F%2F10.5.75.222%3A46178%2FC4A81F353271D807D5A7E076B8012C70%2F%252Fstorage%252FABDB-62E7%252FDCIM%252Fimage%252F%25D0%25A0%25D0%25B0%25D0%25B1%25D0%25BE%25D1%2582%25D0%25B0%252FDSCF1758.JPG%23FromYatse","title":"DSCF1758.JPG","play_action":"play","action":"stream","data":"http%3A%2F%2F10.5.75.222%3A46178%2FC4A81F353271D807D5A7E076B8012C70%2F%252Fstorage%252FABDB-62E7%252FDCIM%252Fimage%252F%25D0%25A0%25D0%25B0%25D0%25B1%25D0%25BE%25D1%2582%25D0%25B0%252FDSCF1758.JPG%23FromYatse"},"addonid":"script.yatse.kodi"}}[!http]

Kodi writes the following in its logs.

2021-03-14 14:59:31.072 T:140192665024256  NOTICE: ES: Client  from ::ffff:172.16.0.20 timed out
2021-03-14 15:04:01.344 T:140194560833280   ERROR: CCurlFile::Stat - Failed: Timeout was reached(28) for 
http://10.5.75.222:47403/C4A81F353271D807D5A7E076B8012C70/%2Fstorage%2FABDB- 
62E7%2FDCIM%2Fimage%2F%D0%A0%D0%B0%D0%B1%D0%BE%D1%82%D0%B0%2FDSCF1758.JPG#FromYatse
2021-03-14 15:04:31.378 T:140194560833280   ERROR: CCurlFile::FillBuffer - Failed: Timeout was reached(28)
2021-03-14 15:04:31.378 T:140194560833280   ERROR: CCurlFile::Open failed with code 0 for 
http://10.5.75.222:47403/C4A81F353271D807D5A7E076B8012C70/%2Fstorage%2FABDB- 
62E7%2FDCIM%2Fimage%2F%D0%A0%D0%B0%D0%B1%D0%BE%D1%82%D0%B0%2FDSCF1758.JPG#FromYatse:

Log from yatse.
debug-20210314_183452.zip (7.6 KB)

2

As said and the template says I need Yatse logs : https://yatse.tv/wiki/debug-yatse-kodi-remote

Be sure to force kill the process after enabling logs and reproducing.

3

Here are the logs generated by yatse.

https://community.yatse.tv/uploads/short-url/v3cGK2SZOBqmRUOU7f3hcuNEpNS.zip

4

I did ask that you forced killed Yatse you did not in those logs.

This is Sunday, please take time to read what I write :slight_smile:

5

I did everything according to the instructions to create a yatse log. And if the log seems large to you, then I indicated a specific problem above with logs from other programs. Sorry for any misunderstandings …

6

As I wrote:

If you do not kill Yatse, Yatse will keep using the same IP and won’t log the necessary part where it decide what IP to use.

So I have perfectly understood that Yatse does not use the proper IP, but without the logs showing the part where Yatse decide the one to use there’s nothing I can do.

7

debug-20210314_183452.zip (7.6 KB)

8

Thanks

2021-03-14 18:33:36.706 Verbose/CastUtils: Found IPs - Wifi: null / null, Mobile: 10.93.55.191, P2P: null
2021-03-14 18:33:36.707 Verbose/CastUtils: Selected IP: 10.93.55.191

The VPN should be logged in the P2P part seems Yatse does not properly identify it, is the mail related to your account here valid so I can send you a special build with more logs about the VPN interface names / types ?

10

The tracker is public I’ve removed your mail will send you a test build.

11

My vpn interface is ppp0.

12

debug-20210314_201204.zip (7.1 KB)

13

Thanks seems I filtered on a wrong interface attribute removing it.

Will fix for next release.

14

And thank you for the great app and great support.