Skip to content
This repository has been archived by the owner on Nov 27, 2021. It is now read-only.

got error installation channels.go:101: #17

Open
ezyfst opened this issue Jul 29, 2021 · 8 comments
Open

got error installation channels.go:101: #17

ezyfst opened this issue Jul 29, 2021 · 8 comments

Comments

@ezyfst
Copy link

ezyfst commented Jul 29, 2021

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

@erkexzcx
Copy link
Owner

More information is needed

@ezyfst
Copy link
Author

ezyfst commented Jul 31, 2021

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
Copy link

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
Copy link

Ro-Den commented Sep 3, 2021

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
Copy link
Owner

erkexzcx commented Sep 3, 2021

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
Copy link

Ro-Den commented Sep 3, 2021

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
Copy link

akavoukis commented Sep 9, 2021

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
Copy link

Ro-Den commented Sep 10, 2021

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants