(0, 11:41 PM)pinnocchio Wrote: I updated to Beta 4 and installed HQ Player NAA and server but the server seems to refuse to startClick on the text 'Fail to start'.
I will run more tests and update this thread. It did however run fine as I've tested it and Windows version of HQ Player was able to see NAA running on RPi2. However, RPi 2 is not 64bit compatible so I cannot use the latest image. I used the 32bit image for RPi3 that worked fine for RPi2. Once we worked this out systematically, then we can rule out issues and nail down what the problem is (is it IPv6, is it version incompatibility? is it networking? etc).
Try and update the NAA to the latest version (see my previous post) and see if that works.Īlternatively, install HQPLayer on the Snakeoil PC as well as see if they can talk to each other. (0, 09:49 AM)agent_kith Wrote: What's running on the RPi? NAA or HQPlayer? deb package to 3.54x last night but it made no changes. PS: if not wrong, I think the MPD v19 uninstall is fixed in the next releast Blind Testing (I'd double check and confirm tonight if I can). Now try and see if you can see this machine from your other computer again. Next go to the music players page and restart the players (just to be safe). Download the latest deb file, and drop it into the install box on the Snakeoil WebApp.
Perhaps you do need to run 3.54x and above.
I could try to install the 3.54.x NAA?I've only tested NAA against the HQP that's installed on Snakeoil. Step 2: Change Value “State” to 146432 Decimal or 0x00023c00 Hexadecimal.Sudo NETWORKAUDIOD_IPV6=0 networkaudiod restart (0, 05:58 AM)pinnocchio Wrote: It does Illegal instruction as soon as I open the HQ Player Client and try to modify the NetworkAusioAdapter from IPv4 to IPv6 Turn on certificate revocation check in registry: Step 2: In the Security section => check the box for: Turn on certificate revocation check in Internet Explorer: Certificate revocation checking protects our clients against the use of invalid server authentication certificates either because they have expired or because they were revoked. However, disabling the revocation check in production environment is not recommended. This will disable the certificate revocation check & the rollup update will complete successfully. Step 2: Change Value “State” to 146944 Decimal or 0x00023e00 Hexadecimal Step 1: Open registry editor => Navigate to the following key: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionWinTrustTrust ProvidersSoftware Publishing Turn off certificate revocation check in registry: “Check for server certificate revocation” “Check for publisher’s certificate revocation” Step 2: In the Security section => uncheck or clear the box for: Step 1: In Internet Explorer => go to Tools =>Internet Options => Advanced tab Turn off certificate revocation check in Internet Explorer: There are two ways to turn of the certificate revocation while doing a rollup update.
Let’s see as how to disable the certificate revocation check in this article. One of the reasons for this issue is that the routine check of the certificate revocation list for. This problem is when the server has no internet access or when the server has limited internet access. There may be several scenarios where we may experience long wait time for the services or application to start.