And that indicates one of the following:
And regarding the last thing, then there’s a known error in my script, if username or password contains extended characters
(If so, grap a yet to be released version here: https://github.com/ukdtom/ClaimIt/blob/passencode-fix/linux/claimpms.sh)
If it’s not password or script related, is this when the user is supposed to set QNAP to use Google DNS 8.8.8.8 and/or 8.8.4.4, or check for dns rebinding or VPN?
Any feelings on making http_status global and printing it out after an error?
It was very elegant. Thanks for working on that.
Yes, this is this kinda situation
Wouldn’t make sense, since the status code would reflect what the PMS returns to me, and not the actual timeout between PMS and plex.tv, sadly
I do however have a request towards Plex, to log DNS latency if possible
Thanks
dane22, thank you so much for your help. I am traveling for business this week, my responses are delayed.
I was having trouble copying your script into the directory (I am using an Ipad to vpn into my network) so I opted to change the password to a simpler one, 14 characters using upper, lower, and numbers only. No change.
I then went and changed the DNS of my main gateway (ubiquiti USG) to point to 8.8.8.8/8.8.4.4, re-ran the original script. No change.
Incidentally, I don’t live far from Los Gatos. You wouldn’t be based there?
If your QNAP has a static IP where you also supplied it with two DNS servers,
that’s where you set the 8.8.8.8 and 8.8.4.4.
hi nibbles, QNAP has DHCP, address is locked on the Unifi DHCP server so it doesn’t change. i find this method allows me a simple way to update systems.
and what does the QNAP list for it’s primary and secondary DNS?
192.168.16.1
So you don’t want to make it a static IP for testing, and
you trust that your gateway is better than google at DNS,
even though dane helped you learn that you have network,
or gateway, or password problems. okay gotcha.
Not quite. Today I am remote, I wasn’t able to test a proper VPN before i left this morning. Only the Ipad VPNs into the network and its usefulness as a debugging tool isn’t quite up there.
I wasn’t able to change QNAP’s DNS, and I didn’t want to mess with its internal virtual switch while i am traveling. changing the main DNS pointer was something I had neglected to do when I upgraded the network, and it was an easy fix.
I can make the other changes on Friday when I have access to a proper terminal.
I do appreciate the assistance you and dane have provided, and by no means do I want to second guess you.
Not really…
As my Nickname says, I’m Danish, and based in Copenhagen
I have traveled to Copenhagen for business twice, albeit both in February. I was impressed by the modern architecture in the suburbs, the vast open spaces, and a Nordic yet unique feel to the touristy parts of the city.
i quickly realized that Copenhagen in February is not a tourist friendly time in the calendar 
Dane22 and Nibbles,
As dane pointed out there was an issue with the DNS settings. However, it wasn’t settings on my internal network. Rather it was AT&T redirecting DNS inquiries to their own DNS server. I followed instructions on this page:
Once I changed the settings, the script worked perfectly and I now have access to my server.
I really appreciate your help and patience here. Its still a mystery why this happened.
Cheers, Henry.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
