Closed enzanki-ars closed 1 year ago
Hey, thanks for reporting!
It actually doesn't have to do with F1MV but with the analytics of F1MV Lights Integration, so it shouldn't impact the F1MV connection.
I am currently investigating the analytics issue.
Hey,
I investigated a bit, and it turns out it's probably an issue with your DNS.
Since I can't reproduce this, I will close this issue.
Then it appears that I might have a related issue then. The app does not connect to Multiviewer. Multiviewer is configured with allow untrusted, firewall is allowed (not that it should matter for localhost), this app is configured in default mode for http://localhost:10101
, and other apps like Ultimate F1 viewer and my own code interfacing with the API connects fine. When I look at the both the logs for this app and also Wireshark on all interfaces, including localhost, I don't see any traffic to port 10101.
(The DNS could be AT&T being bad at IPv6, and I'll have to investigate that separately, as I thought I solved that before already....)
Hey, could you try "http://0.0.0.0:10101"?
It appears that this app is not connecting to F1MV due to an unrelated failure in the
getUniqueID
call, seemingly an IPv6 error, as this request does work properly in the browser.With full debug logs on: