Installing package [forgebox:testbox-be]
Verifying package ‘testbox-be’ in ForgeBox, please wait…
Aww man, ForgeBox isn’t feeling well.
Uh-oh, ForgeBox returned something other than JSON. Run “system-log | open” to
see the full response. GET https://www.forgebox.io/api/v1/entry/testbox-be
Unknown host: sun.security.validator.ValidatorException: PKIX path building fail
ed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find v
alid certification path to requested target
Connection Failure. Status code unavailable.
We’re going to look in your local artifacts cache and see if one of those versio
ns will work.
No satisfying version found for [stable]. Well, we tried as hard as we can. For
geBox is unreachable and you don’t have a usable version in your local artifacts
cache. Please try another version.
CommandBox:commandbox-jre-win64-3.5.0>
That error message sounds like your version of Java, your OS, or possibly a networking application/proxy at your org is incompatible with the SSL cert in use by Cloudflare. Can you try the same operation from another computer or at your house?
That said, when I run the same command I get the message “The ForgeBox entry [TestBox BDD/xUnit Bleeding Edge] is inactive.” which is true. The proper way to install the bleeding edge version of TestBox is:
install testbox@be
And that command works fine for me. If you still get the same error, can you check what version of Java CommandBox is running on. This shows up when you run the “info” command. You may have and old version and/or an outdated list of trusted certs.
For some reason, it seems the root cert is not installed then. I don’t know why though. That error is all over the internet, but everyone says it happens when using a self-signed cert which we’re not doing and your version of Java should be new enough to include any recent root cert additions.
When you said you installed a cert earlier, where and how did you install it?
*> I added this certification in commandbox folder.*
Can you be more specific? What commandbox folder did you add it to?
Firstly, where is your java home? If you don't know, run this command from
CommandBox to find out:
I have added the proxy settings https://ortus.gitbooks.io/commandbox-documentation/content/config_settings/proxy_settings.html from this referal link.
And tried to install testbox.
Then I ll receive the error as,
CommandBox:test> install testbox@be
Installing package [forgebox:testbox@be]
Verifying package ‘testbox’ in ForgeBox, please wait…
Aww man, ForgeBox isn’t feeling well.
Uh-oh, ForgeBox returned something other than JSON. Run “system-log | open” to
see the full response. GET https://www.forgebox.io/api/v1/entry/testbox
408 Request Time-out
We’re going to look in your local artifacts cache and see if one of those versio
ns will work.
No satisfying version found for [be]. Well, we tried as hard as we can. ForgeBo
x is unreachable and you don’t have a usable version in your local artifacts cac
he. Please try another version.
CommandBox:test>
Wait, you imported the cert into the wrong java home! You need to import the cert into the actual version of Java used by CommandBox. I don’t know why you’re doing it in your CF11’s Java installation.
The fact that you placed the pem files in the commandbox folder prior to importing them is irrelevant. They could be in a temp folder for all Java cares-- your commands specifies the cacerts file to import them into and it needs to be the cacerts file in the Java home used by CommandBox. Note, CommandBox is its own Java app internally that runs as a completely separate and unrelated process to any Adobe CF servers you may be using.
I would remove the proxy settings. I don’t know what you added, but I’m guess they were wrong. Did you ask your network administrator if a proxy was actually necessary to access the internet?