Forum

Post a new question

Categories:

Tags:

IPv6 wmsauth hash match not found

Paul 2018-07-04 15:07:36 UTC in Paywall: WMSAuth and beyond
Eb14adce38c982e3c5ddb32b31369f68

I'm not sure why users on IPv6 cannot view my protected streams..

Their IP does not look correct. My website is behind Cloudflare and I really don't want to disable CF protection.

eu-central-6: we cannot find hash match for ::ffff:81.39.205.3, signature=[12345]
eu-central-6: we cannot find hash match for ::ffff:185.246.103.34, signature=[12345]
origin-eu-1: we cannot find hash match for ::ffff:206.231.121.124, signature=[12345]

Does anybody know what is happening? I am using
code such as:
$ip = $_SERVER['REMOTE_ADDR'];
if (!empty($_SERVER["HTTP_CF_CONNECTING_IP"])) {
$ip = $_SERVER['HTTP_CF_CONNECTING_IP'];
} elseif (!empty($_SERVER['HTTP_X_REAL_IP'])) {
$ip = $_SERVER['HTTP_X_REAL_IP'];
} elseif (!empty($_SERVER['HTTP_CLIENT_IP'])) {
$ip = $_SERVER['HTTP_CLIENT_IP'];
} elseif (!empty($_SERVER['HTTP_X_FORWARDED_FOR'])) {
$ip = $_SERVER['HTTP_X_FORWARDED_FOR'];
$commapos = strrpos($ip, ',');
$ip = trim( substr($ip, $commapos ? $commapos + 1 : 0) );
}

I did enable ipv6 in nimble.conf on all my servers.

Thank you

Max 2018-07-04 15:41:09 UTC
Ba425406063261ec184229ed0d5a200d

Hello Paul,

Please try to set "listen_interfaces" option to nimble.conf specifying exact IPv4 and IPv6 interfaces that Nimble have to use instead of a default "*" value, IPv4 clients will have "normal" addresses in this case.

Thank you.

Paul 2018-07-23 18:05:27 UTC
Eb14adce38c982e3c5ddb32b31369f68

OK thank you. Something like this?

listen_interfaces = 123.235.72.123, 3764:180:3:f4f::e968

I am having problems now testing, the viewer has ipv6 address and also ipv4.

My website shows IP of viewer of ipv6
but Nimble complains of no IP match and wmsauth log shows the viewer's IPv4 address!

Thank you

Paul 2018-07-23 20:41:08 UTC
Eb14adce38c982e3c5ddb32b31369f68

More info. I am testing from somewhere with ipv6 and ipv4.

I can ping the Nimble server via ipv6 - e.g., ping6 2604:3104:3:f4f::2604 works

listen_interfaces = 1.1.1.1, 2604:3104:3:f4f::2604
enable_ipv6 = true

the TV website is accessed by ipv6, I can see with php echo connecting_IP address on a test page.

but Nimble edge server still showing "we cannot find hash match for 4.4.4.4"

Do you have any ideas please?

Thank you

Paul 2018-09-17 18:25:35 UTC
7e39057ef6707d749c37ea8a0b89840a

any help with this please?

my website is on a separate server, and has both ipv4 and ipv6.

my edge servers have ipv4 and ipv6.

I access website and see my ipv6 address being used, but streams fail (403) error and log shows "cannot find hash match for 4.4.4.4".

Any idea how to force ipv6 if exists?

Paul 2018-09-18 13:01:05 UTC
7e39057ef6707d749c37ea8a0b89840a

Nothing?

I know it might not be a core Nimble issue but please somebody must have some idea why/how this is happening?

One server (web) using ipv6 by default and other server (Nimble) using ipv4 by default....and messing up the wmsauth.... any ideas on how I can proceed please?

Denis Slobodskoy 2018-09-19 02:11:04 UTC
C723b4e32e1909d3d1b5519f98b586fe

What stream URL are you using - probably Nimble's hostname resolves to IPv4 only?
Please submit your issue via https://wmspanel.com/help , we will try to find the solution.

Post a reply



This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the Privacy Policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the Privacy Policy.
By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies.