getdown icon indicating copy to clipboard operation
getdown copied to clipboard

Failed to find proxy settings in Windows registry [error=java.lang.UnsatisfiedLinkError: no jRegistryKey in java.library.path]

Open austin-bowen-iss opened this issue 5 years ago • 8 comments

We've downloaded and are using the getdown-launcher-1.8.2.jar, but we noticed this error message in the launcher.log:

Failed to find proxy settings in Windows registry [error=java.lang.UnsatisfiedLinkError: no jRegistryKey in java.library.path]

This tells me that automatic proxy detection is broken? Or are we missing something? We've been able to get Getdown working with a proxy using the proxy popup screen, but our users will likely not know their proxy info.

austin-bowen-iss avatar Feb 22 '19 15:02 austin-bowen-iss

Hi! We've looking around with this error and find out the problem. Try copying jRegistryKey.dll file (https://github.com/threerings/getdown/tree/master/lib/jRegistryKey.dll) to a folder included in the windows path, like jdkFolder/bin or C:\Windows\System32. Besides this, we realized that it's working if you define a fixed proxy url and port but it's not working when a pac script is set (in windows).

Best regards.

jenriq avatar Feb 22 '19 17:02 jenriq

As per @jenriq 's recommendation, I copied the jRegistryKey.dll into one of my Windows path locations, and the error message changed:

Failed to find proxy settings in Windows registry [error=java.lang.UnsatisfiedLinkError: path\to\jRegistryKey.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform]

I am running a 64-bit JRE, and we do not have the option to run a 32-bit JRE. Unfortunately, it looks to me like the jRegistryKey project has not been updated to build 64-bit dlls.

Perhaps Getdown could be updated to use a different, 64-bit capable library to read the registry? This seems like a pretty important problem to me because this means Getdown will not be able to auto-detect proxy settings when using a 64-bit JRE (and starting with Java 11, there will be no more 32-bit JREs going forward).

austin-bowen-iss avatar Feb 25 '19 19:02 austin-bowen-iss

I think it would be better to replace ddl with some java implementation that detects proxy configuration, like https://github.com/MarkusBernhardt/proxy-vole

jenriq avatar Mar 11 '19 15:03 jenriq

@jenriq agree, Java now has more built-in support for detecting proxies.

austin-bowen-iss avatar Mar 11 '19 15:03 austin-bowen-iss

That looks great. I’ll file an issue to update the proxy detection to use proxy-vole, so it doesn’t fall through the cracks, and then try to tackle that in the near future. On Mon, Mar 11, 2019 at 8:51 AM austin-bowen-iss [email protected] wrote:

@jenriq https://github.com/jenriq agree, Java now has more built-in support for detecting proxies.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/threerings/getdown/issues/190#issuecomment-471599152, or mute the thread https://github.com/notifications/unsubscribe-auth/AAL-9D4UJHKcSpwsepQVrSr1zlAmu6Nkks5vVntzgaJpZM4bJ3ho .

-- -- [email protected]

samskivert avatar Mar 11 '19 16:03 samskivert

Any news on this problem? I have a user that is experiencing the same error message : 2020/01/24 16:42:37:004 INFO Failed to find proxy settings in Windows registry [error=java.lang.UnsatisfiedLinkError: no jRegistryKey in java.library.path]

I'm still using 1.8.2, should I update to 1.8.6?

WPCleaner avatar Jan 27 '20 14:01 WPCleaner

We're experiencing the same problem. I upgraded to 1.8.6, but still get the error.

We also can't get the proxy dialog to appear to enter proxy information. What are the specific conditions to get this dialog to appear?

robmilton avatar Jan 28 '20 21:01 robmilton

I wanted to follow up with more information on this issue. We have a client that uses a proxy that requires authentication and are experiencing the same problem described here. We were using GetDown v1.8.2, but after reading the CHANGELOG we upgraded to v1.8.6. However, the same error exists with this latest version.

I instructed the client to place a "proxy.txt" file with the host and port information in the expected format in the proper location for our application. After adding the "proxy.txt" file GetDown is now reporting HTTP response code 407 for every resource. This error indicates proxy authentication is required.

We cannot get GetDown's proxy dialog to appear in order to provide the proxy credentials. So I have a couple of questions:

  1. How can we get GetDown's proxy dialog to appear?
  2. If we can't get the proxy dialog to appear what other method can we use to provide proxy credentials?

Thanks for any help with this, Rob

robmilton avatar Jan 29 '20 15:01 robmilton