Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
SVN enlistment failed five mounth ago
SVN enlistment failed five mounth ago. In current time, all new enlistment added and download successfully, please, restart all other again.
cray:
When I try and run this command:
svn co https://code.dreambot.ru/svn/ng.base.form/trunk
It gives me:
Error validating server certificate for 'https://code.dreambot.ru:443':
- The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually!
- The certificate hostname does not match.
Certificate information:
- Hostname: 80.84.114.154
- Valid: from Sat, 12 Jun 2010 15:50:08 GMT until Sun, 12 Jun 2011 15:50:08 GMT
- Issuer: DreamBot, Moscow, Moscow, RU
- Fingerprint: 14:49:0b:86:70:1d:a5:f6:43:c9:d8:4c:e8:31:19:db:4d:ad:72:d6 (R)eject, accept (t)emporarily or accept (p)ermanently?
I think ohloh is being confused due to this.
As a test, I removed the https enlistment from Dream Bot Releases and added the http enlistment.
It correctly updated.
There are two things you can do to fix this:
- Change all the https enlistments to be http instead or
- Fix the certificate for the https version and after it's fixed, reply here and I will re-start the failed jobs.
Oh, Ok. But how you explain two enlistments added and loaded succesfully via https two days ago:
https://code.dreambot.ru/svn/ng.skin.js.gallery/trunk
Subversion
Ohloh update completed 12 minutes ago.
https://code.dreambot.ru/svn/ng.skin.js.skinpaint/trunk
Subversion
Ohloh update completed 11 minutes ago.
And, As I can see, reloaded sucessfully just now? I think, ohloh is rigid to sertificate errors you wrote. I think (and I know) there was more seriously sertificate error 5 month ago, and that softmare don't to try reload 5 month. All new enlistment load via https successfully.
But I done as you want and delete / add all faulted enlistments with http. Let it be so.
But three (only three) enlistment :
http://code.dreambot.ru/svn/adapterchain/trunk
http://code.dreambot.ru/svn/ng.app.rubricator/trunk
http://code.dreambot.ru/svn/ng.app.smartbanner/trunk
(Failed 19 minutes ago.)
Fault again. That reason is now?
Please, restart them, and, please, restart this enlistmnent:
http://code.dreambot.ru/svn/ng.app.xmlrpcsync/trunk
Subversion
Ohloh update completed over 3 years ago.
And restart a few other enlistment doesn't updated last three year: As Far As I Remember, three year ago there was some mysterious error, and I enter with enlistment as https... Ohloh is so vindictive ...
cray:
We are going to look into enhancing ohloh so it isn't so strict and allow it to deal better with self signed certificates. I've created an issue on our side to track this.
We are busy with server migration right now so I don't have an estimated time for completion.
As for the enlistments you mentioned, for some reason I'm unable load the page I need to load in order to investigate why they are broken (it is just timing out for me).
We might not be able to fix the broken enlistments until after we have migrated the servers from Chicago to Boston.
I'll reply here once I know more.