Great, thanks a lot for your timely support! On Friday, July 1, 2016 at 9:03:28 PM UTC+8, Wilfried Gösgens wrote: > > Hi, > yes it is. > Find it as: > > https://www.arangodb.com/repositories/Windows7/x86_64/ArangoDB-3.0.1-win64+x.exe > or > > https://www.arangodb.com/repositories/Windows7/x86_64/ArangoDB-3.0.1-win64+x.zip > > which will contain Jan's fix which weren't in time for 3.0.1 ;-) > > Cheers, > Willi > > On Friday, July 1, 2016 at 11:07:15 AM UTC+2, Thomas Weiss wrote: >> >> OK got it, thanks. >> Would it be possible that you guys provide a patched binary version >> (Windows) in the meantime? It's kind of a show-stopper for me as I was in >> the middle of migrating our staging to continue the tests. >> >> On Friday, July 1, 2016 at 4:54:20 PM UTC+8, Jan wrote: >>> >>> It does not have anything to do with the self-signedness of the server's >>> certificate, as arangosh, arangoimp and arangodump work fine with >>> self-signed certificates. >>> The reason was simply that arangorestore had not SSL support compiled >>> in, so it cannot connect to an SSL endpoint at all. >>> The following patch fixes that: >>> >>> diff --git a/arangosh/Restore/arangorestore.cpp >>> b/arangosh/Restore/arangorestore.cpp >>> index 116fa53..eec4638 100644 >>> --- a/arangosh/Restore/arangorestore.cpp >>> +++ b/arangosh/Restore/arangorestore.cpp >>> @@ -33,6 +33,7 @@ >>> #include "Random/RandomFeature.h" >>> #include "Restore/RestoreFeature.h" >>> #include "Shell/ClientFeature.h" >>> +#include "Ssl/SslFeature.h" >>> >>> using namespace arangodb; >>> using namespace arangodb::application_features; >>> @@ -54,6 +55,7 @@ int main(int argc, char* argv[]) { >>> server.addFeature(new RandomFeature(&server)); >>> server.addFeature(new RestoreFeature(&server, &ret)); >>> server.addFeature(new ShutdownFeature(&server, {"Restore"})); >>> + server.addFeature(new SslFeature(&server)); >>> server.addFeature(new TempFeature(&server, "arangorestore")); >>> server.addFeature(new VersionFeature(&server)); >>> >>> So it was simply an oversight, but it took me quite a while to find out. >>> I have pushed the fix into the 3.0 and devel branches, and it will land in >>> 3.0.2. >>> Best regards >>> Jan >>> >>> Am Freitag, 1. Juli 2016 09:40:54 UTC+2 schrieb Thomas Weiss: >>>> >>>> Hi again, >>>> >>>> Trying to restore a dump to a 3.0 server that has SSL enabled (I can >>>> connect on the web dashboard so it's working fine). >>>> When using *--server.endpoint ssl://...* it reports that it can't >>>> connect: ERROR Could not connect to endpoint http+ssl:// >>>> May that be because the server's certificate is self-signed? >>>> >>>> Thanks >>>> Thomas >>>> >>>
-- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
