-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error unmarshalling JSON #114
Comments
Hello, I need to investigate again the go.xtream-code package again..etc |
do you think you can try to get some JSON data from your API provider? We should write unit tests on the xtream package to try to cover all the test...etc |
So this provider uses HTTPS for it's XC endpoints...Assuming that the XC back end is the same across providers, I can wireshark a non-https set of calls and then try them against this provider. What's the best way to get the logs to you? |
The best way, it's to add a debug mode here: to trace easily the JSON payload...etc (TLS or not) I'll make a docker image with dev tag to try it on your side...etc |
Thank you! docker.pkg.github.com/pierre-emmanuelj/iptv-proxy/iptv-proxy:latest-amd64 What would be the dev one, as all of ones listed here: https://github.com/pierre-emmanuelJ/iptv-proxy/releases Seem to be production ones? |
Could this be of help? Just started using iptv-proxy today for xtream so I can't say if it was working before but mainly the client gives a very generic error when trying to view TV shows/series while live seems to work. |
So in an attempt to give you a little more to go on, I pulled the JSON from the player_api.php from some of the services I use. 'interestingly' the two that fail are HTTPS, but I think that could just be coincidence at this point. I've removed the URLs, username/password and subscription dates (they're just unixtime integers):
|
Any news on this? Any way I can help? :) |
Some |
BTW: I think I'll fork the repo |
Also getting this in a different spot:
|
Hi! |
I'm having the same issue. Error #1: error unmarshaling json: json: invalid use of ,string struct tag, trying to unmarshal unquoted value into xtreamcodes.FlexInt Is there any update on the fix for this? |
I've got the same issue know. I thought it was coming from my attempts with nginx and 3 backends, but even in the original variant without nginx it doesn't work now. |
Seems like its a handful issues that's all related to this, like #111, 114 & 137. |
I’m getting this error now. Error #1: error unmarshaling json: json: invalid use of ,string struct tag, trying to unmarshal unquoted value into xtreamcodes.FlexInt Did the debug docker image get created? What does anyone need, happy to provide data. |
Le jeu. 8 déc. 2022, 11:43, Conny Ankargren ***@***.***> a
écrit :
… Seems like its a handful issues that's all related to this, like #111
<#111>, 114 & 137.
—
Reply to this email directly, view it on GitHub
<#114 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFKESUY2FWPHZUPFSGZKZXTWMG3WZANCNFSM5PUTI5CA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi all, Same issue here, been happening for a few weeks now.
Seems to be throwing this when getting categories (live/movie/tv). Happy to provide any further logs or try a new version of the proxy, already tried rolling back to a previous version but no joy. |
Seeing this in the Feb 7th Docker build:
2022/03/01 16:51:47 [iptv-proxy] 2022/03/01 - 16:51:47 | 10.0.5.55 | xtream cache API m3u file
[GIN] 2022/03/01 - 16:51:48 | 500 | 568.289666ms | 10.0.5.55 | GET "/get.php?username=test&password=test&type=m3u_plus&output=ts"
Error #1: error unmarshaling json: json: invalid use of ,string struct tag, trying to unmarshal unquoted value into xtreamcodes.FlexInt
[GIN] 2022/03/01 - 16:53:26 | 500 | 538.754145ms | 10.0.5.55 | GET "/xmltv.php?username=test&password=test"
Error #1: error unmarshaling json: json: invalid use of ,string struct tag, trying to unmarshal unquoted value into xtreamcodes.FlexInt
Happens with both the XMLTV and the get.php calls from clients - anything I can do / look at?
99% sure the authentication/endpoint details are correct
The text was updated successfully, but these errors were encountered: