search

erkexzcx / stalkerhek

Stalker portal proxy server that allows sharing account on multiple STB boxes and play on VLC.
GNU General Public License v3.0
82 stars 52 forks source link

got error installation channels.go:101: #17

Open ezyfst opened 3 years ago

ezyfst commented 3 years ago

when installing go i got this error after this the script exited how do i solve this issue

erkexzcx commented 3 years ago

More information is needed

ezyfst commented 3 years ago

When i run the script it say the following " go channel:101' after that the script stopped. I put the mac address and URL in the yml file. The other information that is required did not show op in whireshark because i use stbemu. I use ott-navigator without any problem. What kind of information do you need?

dstanchev commented 3 years ago

Hello, I have the same problem with some portal. Last message is "go channel:101: " then application exit. In configuration I have working MAC and URL.

Ro-Den commented 3 years ago

Possible reasons:

  1. You've failed to provide the valid token in your configuration file.
  2. Your STB/Emu reconnects/disconnects for some reason making the provided token invalid.
  3. Someone else connects using the same credentials making the provided token invalid.

By the way, can we get the token automatically? Or is it too much of the hekking?

erkexzcx commented 3 years ago

By the way, can we get the token automatically? Or is it too much of the hekking?

Do not specify anythink in token field so stalkerhek would generate a random one.

Ro-Den commented 3 years ago

Do not specify anythink in token field so stalkerhek would generate a random one.

Looks like, a random token is not working when authenticating without a username & a password because a server generated token serves as the credentials in this case.

UPDATE: Actually, a random token works! But only with a number of portals.

akavoukis commented 3 years ago

I had a similar problem but I solved it.

When you receive the response from the handshake, you expect the token to be in "Token" but in my case it was "token" so the code would to use it next time as a Bearer.

I think the reading of the "token" should be case insensitive.

Edit: sorry i just realised it was also discussed on an other issue

Ro-Den commented 3 years ago

When you receive the response from the handshake, you expect the token to be in "Token" but in my case it was "token" so the code would to use it next time as a Bearer.

1st thing I've fixed for myself. Also checked a dozen of portals. It's always "token" and never "Token". So, that's an error obviously.