iprima.cz doesnt work

Please, could you modify a new version of the iprima plugin to connect primarily to port 80, not 1935 (or add it as a user choice in the preferences)?

Port 1935 is blocked on my network at ISP level, so I cannot download anything.

Thank you very much.

ifox wrote:
-------------------------------------------------------
> Please, could you modify a new version of the
> iprima plugin to connect primarily to port 80,

Hi

During the tests I conducted earlier in the month, I did state that:

> but the main video uses RTMP. However:
> 1. it does not use default port 1935, but port 80 instead.

so it is my belief tong2shot (the dev responsible for the plugin)
took that under consideration when updating/modifying the
iprima.cz FRD plugin...

Are you in the Czech Republic?
If not, maybe you're trying to DL a geo-blocked programme
If indeed inside the Czech Republic, please wait for clarification
from the dev - if port 80 is the default/only port the plugin uses,
maybe another (network?) issue in your setup is messing up with
iprima.cz downloads...

Regards

@TVjunkie:

Yes, I am in the CZ.

The plugin version 1.2.3 connects only to remote port 1935 (verified in my firewall), shows "Downloading", but no data transfer, because port 1935 is blocked by my ISP.

If I try it from another, unblocked network, the video download through FRD is ok, connected to ip-160-218-1-184.eurotel.cz:1935, verified by netstat command. But I need it from home, using port 80.

If I start the video playback directly from Prima Play website, the embedded Flash video player tries to connect to port 1935 too, but when unsuccessful, it switches to port 80 automatically.



Edited 2 time(s). Last edit at 05/30/2015 08:05AM by ifox.

iPrima plugin v1.3.0 supports RTMP port selection.

It does not work ... tried ports 80 and 443.

Port 80 also didn't work when I tried with rtmpdump : [wordrider.net]. But works if I use port 1935, the same with our RTMP+iPrima plugins.

Based on posts in this topic, it seems they use port 80 as fallback, not RTMP but HLS. I haven't analyzed it yet, I maybe wrong.

Wouldn't it be more reasonable to ask your ISP to open the blocking? I am wondering what are their justifications to block port 1935?

ifox wrote:
-------------------------------------------------------
> It does not work ... tried ports 80 and 443.

tong2shot wrote:
-------------------------------------------------------
> Port 80 also didn't work when
> I tried with rtmpdump

However here (Northern Greece), port 80
(with latest plugin 1.3.0 of course) and a
programme link available worldwide DOES WORK,
as per the attached screengrabs (???)

FWIW, WinVista SP2 32bit, FRD 0.9u4, JRE 7u80 (now EOL'd )

Hm.. that's interesting. Port 80 still doesn't work for me. However when I tried it with VPN's Netherlands node, it worked. Not sure what's happening.

tong2shot wrote:
-------------------------------------------------------
> Hm.. that's interesting. Port 80 still doesn't work for me.
> However, when I tried it with VPN's Netherlands node,
> it worked. Not sure what's happening.

Hi...
Maybe they are implementing some form of
rtmp port management for different IP address ranges...(),
but this would be a novelty...
However, this is a separate issue since @ifox said
that in his home LAN port 80 appears to be working
in the Adobe Flash Player plugin (in a browser).

Perhaps he should provide (debug?) logs
that would help you better to assess
what's going wrong in his setup...

Cheers



Edited 1 time(s). Last edit at 06/01/2015 10:05PM by TVjunkie.

Port 80 also works in my browser. It's actually RTMPT (RTMP encapsulated in HTTP), not HLS, verified with wireshark. Rtmpdump also failed to download it, as I said earlier.

In FRD:
NL http proxy with port 80, doesn't work. But works fine with port 1935.
NL node of VPN with port 80, works fine.
US node of VPN with port 80, works fine.