Issue #81 resolved
> gradle setupDecompWorkspace FAILURE: Build failed with an exception. * Where: Build file '/home/fabian/Programming/Minecraft/Mods/mobtalker2/build.gradle' line: 94 * What went wrong: A problem occurred evaluating root project 'mobtalker2'. > Could not resolve all dependencies for configuration ':shade'. > Could not resolve net.mobtalker:MobTalkerScript:3.0.3-beta. Required by: project : > Could not resolve net.mobtalker:MobTalkerScript:3.0.3-beta. > Could not get resource 'http://www.mobtalker.net/repo/net.mobtalker/MobTalkerScript/3.0.3-beta/ivy-3.0.3-beta.xml'. > Could not GET 'http://www.mobtalker.net/repo/net.mobtalker/MobTalkerScript/3.0.3-beta/ivy-3.0.3-beta.xml'. > java.lang.RuntimeException: Could not generate DH keypair * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total time: 3.994 secs
Just cloned the repo and followed the ReadMe. It seems to be that the dependency fails because the repo isn't avaiable at mobtalker2.net.
I'm still not too familiar with gradle, so how would I set up a development environment for both MobTalker2 and MobTalkerScript so it works?
Looks like that's what the
repofolder of the backup was used for. Eh. I'll take a look at it this weekend. Should be as easy as copying files and making them accessible from the outside. No guarantees, though.
I uploaded and made the
repodirectory on the web server accessible. The issue shouldn't persist anymore. Can you confirm that?
No, it still doesn't work. However, I can confirm with my browser that the file indeed does exist.
is a problem?
@mezzodrinker Its something regarding MobTalker's SSL certificate. Try moving mobtalker.net to LetsEncrypt's certificate system or move the ivy repo to a subdomain like repo.mobtalker.net with SSL disabled. I did some tests on my end and it seems to work on obtaining files if you use LetsEncrypt's Certs.
@100chilly It has nothing to do with the SSL certificate (which is, by the way, from LetsEncrypt already).
Caused by: java.security.InvalidAlgorithmParameterException: DH key size must be multiple of 64, and can only range from 512 to 2048 (inclusive). The specific key size 4096 is not supportedApparently, Java can't deal with 4096 bit Diffie-Hellmann key pairs. So I have two options. Either loosen the security of the whole site by adding a 2048 bit Diffie-Hellman key pair or I use a subdomain which is not encrypted via SSL. I guess I'll take the second.
@mezzodrinker Weird... I'm using LetsEncrypt on my sites and it worked fine so i'm confused, but regardless thanks :)
Again, as I said, it's not an issue with the SSL certificate. It has to do with the way the web server is set up.
Okay. One minor headache and some webserver restarts later, I set up the following:
http://[www.]mobtalker.net/repo/*to the respective sub-URI at
https://[www.]mobtalker.net/repo/*to the respective sub-URI at
https://repo.mobtalker.netso that Java stops complaining if it was to connect to the URL directly (which is the plan, gotta create an issue for this)
@DarkShadow44 So, now, finally, the Gradle script should work fine again. Can you confirm?
Indeed, works fine now, thank you.
Request for Gradle repository on the webserver was redirected to the HTTPS version, which uses a 4096 bit dhparams. A permanent redirect was set up that points at a new subdomain (
repo.mobtalker.net) which can both be accessed through HTTP and HTTPS. The dhparams of the HTTPS version are 2048 bit.
The issue has been resolved.