ncdns windows installer error creating bit.key files.

[samurai321]

That is quite interesting. So, to verify that I understand you correctly, there's a file at "%LOCALAPPDATA%\Google\Chrome\User Data\Default\Profile1\TransportSecurity", and at "%LOCALAPPDATA%\Google\Chrome\User Data\Default\Profile2\TransportSecurity", but not at "%LOCALAPPDATA%\Google\Chrome\User Data\Default\TransportSecurity"?

No.

Exactly at C:\Users\user\AppData\Local\Google\Chrome\User Data\Profile 1

and Profile 2

[biolizard89]

Hmm, I see. It looks like Chromium-based browsers support multiple profiles per user, and each of them gets a different folder. The documentation for this is at https://chromium.googlesource.com/chrom ... ata_dir.md . Looks like we've got some tinkering to do.

[biolizard89]

That is quite interesting. So, to verify that I understand you correctly, there's a file at "%LOCALAPPDATA%\Google\Chrome\User Data\Default\Profile1\TransportSecurity", and at "%LOCALAPPDATA%\Google\Chrome\User Data\Default\Profile2\TransportSecurity", but not at "%LOCALAPPDATA%\Google\Chrome\User Data\Default\TransportSecurity"?

That's right.

Err, hang on, are "Profile1" and "Profile2" subfolders of "%LOCALAPPDATA%\Google\Chrome\User Data\Default\" or subfolders of "%LOCALAPPDATA%\Google\Chrome\User Data\"? The Chromium docs I just found seem to imply that if there are extra profiles, they shouldn't be subfolders of "Default", they'd be subfolders of "User Data".

[biolizard89]

Ah, I see you edited your post while I was replying. Okay, so your observations seem consistent with the Chromium documentation I found. We should be able to get that working.

[samurai321]

wait, is at

C:\Users\user\AppData\Local\Google\Chrome\User Data\Profile 1

and Profile 2

if i input %LOCALAPPDATA%\Google\Chrome\User Data\Default\Profile2\

or %LOCALAPPDATA%\Google\Chrome\User Data\Profile1

it doesn't work... so yes. i edited it.

%LOCALAPPDATA%\Google\Chrome\User Data\Profile 1\

is the correct one.

Cheers.

[biolizard89]

I've filed a few GitHub issues (and a PR) about the issues discussed in this thread:

https://github.com/namecoin/ncdns-nsis/issues/14
https://github.com/namecoin/ncdns-nsis/issues/15
https://github.com/namecoin/namecoin.org/pull/191
https://github.com/namecoin/ncdns/issues/36
https://github.com/namecoin/ncdns-nsis/issues/17
https://github.com/namecoin/ncdns-nsis/issues/18

Thanks for helping me track down the issues, we'll work on getting them fixed soon.