Issue to load HiFi content


#21

Thanks @AlphaVersionD, I’m almost involving all the hifi community thanks to you, LOL
in any case, all the machines, no matter the network, run Windows 10 (64bit)


#22

No problem. It’s why we’re here.


#23

so should I run the domain “Open” and reveal the log to search for my machine?


#24

Not exactly.

Here is how I would tackle the problem:

  1. Begin on a interface.exe machine that is physically on the same network as Venture (you described this as possible)
  2. Open your log on that machine.
  3. Search the log just like I did to find the “remapping”.
  4. Copy and paste that into a notepad.
  5. Close Interface.
  6. Boot the “other” machine that is “new” and on a “different network router”
  7. Repeat steps 2 thru 5.
  8. Compare the logs you have. They should be different.

If they are different than I just described the problem you have. You have bandwidth restrictions on your machine.

Good Luck ZULU!


#25

I did mention that:
“The rock bottom bandwidth is around 2Mb/sec just for your avatar and a non-local domain with a few items in it. The practical minimum bandwidth is 10Mb/sec DL and 2Mb/sec UL.”

But, because he was saying nothing was loading, it seemed something else is going in. Anyway, glad more eyes are on the problem to help Zulu out.


#26

Hello,
here again…it seems like an internet connection problem to me, because here follows the new log:

http://pastebin.com/NvHZVkvr

here there are the code lines mentioned by @AlphaVersionD method:

[07/21 13:16:04] [DEBUG] Added “Avatar Mixer” (W) {2f00eee9-2cf4-428d-baff-4d69f5c1108a} 162.243.159.219:35882 / 162.243.159.219:35882
[07/21 13:16:04] [DEBUG] Added “Audio Mixer” (M) {a1b41588-db78-427c-b9ef-d7c358f38c92} 162.243.159.219:43024 / 162.243.159.219:43024
[07/21 13:16:04] [DEBUG] Added “Entity Server” (o) {cac1c76f-e524-4d04-99d0-6aaee82c00ac} 162.243.159.219:43603 / 162.243.159.219:43603
[07/21 13:16:04] [DEBUG] Added “Asset Server” (A) {4ef68aec-044a-446a-bb85-e6731afeb04c} 162.243.159.219:44294 / 162.243.159.219:44294
[07/21 13:16:04] [DEBUG] Added “Messages Mixer” (m) {be8a314c-33ef-4326-a78a-3b84ed0f3334} 162.243.159.219:59833 / 162.243.159.219:59833

Instead on my working machines they are:

[07/19 14:55:39] [DEBUG] Added “Avatar Mixer” (W) {2f00eee9-2cf4-428d-baff-4d69f5c1108a} 162.243.159.219:35882 / 162.243.159.219:35882
[07/19 14:55:39] [DEBUG] Added “Audio Mixer” (M) {a1b41588-db78-427c-b9ef-d7c358f38c92} 162.243.159.219:43024 / 162.243.159.219:43024
[07/19 14:55:39] [DEBUG] Added “Entity Server” (o) {cac1c76f-e524-4d04-99d0-6aaee82c00ac} 162.243.159.219:43603 / 162.243.159.219:43603
[07/19 14:55:39] [DEBUG] Added “Asset Server” (A) {4ef68aec-044a-446a-bb85-e6731afeb04c} 162.243.159.219:44294 / 162.243.159.219:44294
[07/19 14:55:39] [DEBUG] Added “Messages Mixer” (m) {be8a314c-33ef-4326-a78a-3b84ed0f3334} 162.243.159.219:59833 / 162.243.159.219:59833

So do you confirm is a network issue? How can I solve it?

Thanks.


#27

No. Almost, but not quite.

Look inside the logs on the machine running Interface.

You’ll be searching for this:

"52.53.199.81"
[07/21 09:45:24] [DEBUG] Received network peer object for domain - "ec142348-6b6d-490f-8ce9-f3895910c66d" - public: 74.215.56.35:40102 - local: 192.168.0.127:40102
[07/21 09:45:24] [DEBUG] Sending ping packets to establish connectivity with domain-server with ID "ec142348-6b6d-490f-8ce9-f3895910c66d"
[07/21 09:45:24] [DEBUG] Received reply from domain-server on 192.168.0.127:40102
[07/21 09:45:24] [DEBUG] Connecting to domain using local socket
[07/21 09:45:24] [DEBUG] Sending connect request to domain-server at "192.168.0.127"

This is where the public IP converts over to a LAN IP. My instructions indicate you will have different results in the different logs.

You might want to also consider including a diagram with IP roots of your local lan.

Uncomfortable with that? Send your findings directly to @b. He is a HiFi network engineer. He’ll get your problem sorted.


#28

Hello @b thanks for this help. So, according to instructions, here my code lines, coming from the working PC:

[07/19 14:55:35] [DEBUG] Received network peer object for domain - “f4b21cbf-9bc4-4479-8487-4b247ef9611c” - public: 162.243.159.219:40102 - local: 162.243.159.219:40102
[07/19 14:55:35] [DEBUG] Sending ping packets to establish connectivity with domain-server with ID “f4b21cbf-9bc4-4479-8487-4b247ef9611c”
[07/19 14:55:35] [DEBUG] Received reply from domain-server on 162.243.159.219:40102
[07/19 14:55:35] [DEBUG] Connecting to domain using local socket
[07/19 14:55:36] [DEBUG] Sending connect request to domain-server at “162.243.159.219”

here the code lines coming from PC which can’t load content properly:

[07/21 13:16:04] [DEBUG] Received network peer object for domain - “f4b21cbf-9bc4-4479-8487-4b247ef9611c” - public: 162.243.159.219:40102 - local: 162.243.159.219:40102
[07/21 13:16:04] [DEBUG] Received reply from domain-server on 162.243.159.219:40102
[07/21 13:16:04] [DEBUG] Connecting to domain using local socket
[07/21 13:16:04] [DEBUG] Sending connect request to domain-server at “162.243.159.219”

They look the same…is that normal?
Thanks.


#29

Just to be precise the working PC is not that one of the stack manager, I don’t know if this info can help. It’s just a PC I use to connect to HiFi which has no problems.


#30

That looks like a self-assigned IP. Do you have multiple active network interfaces, like a virtualbox adapter or something like that?


#31

Digital Ocean SF - - -


#32

Hello,
it seems I solved the problem! the PC which was not working had a restriction on the network. In fact, the gates 80 and 443 were closed by the firewall in entrance. So now the connection is actually opened. I am now able to load the content.
Thanks for your support and sorry for let waste your time. If everything happens in the next days, I will reply here but I don’t think so.
Have a nice day!


#33

Excellent! It reminds me that a good thing HF can add to interface is some port testing. If required ports test out as closed, interface should inform the user of the problem, even offer some remedy guidance. Similar testing on bandwidth should take place.