Seger

Push, Same Situation.

14:08:27.0294074 HelloSupported::True 14:08:27.0463620 KCM::OpenStatus::NotFound 14:08:27.0463620 KCM::OpenFailed::RequestingCreate. 14:08:36.3408149 KeyRetrievalStatus::Success 14:08:41.4531682 GetAttestationStatus::Success 14:08:43.3594864 PublicKeySignStatus::Success 14:08:43.3594864 PublicKey::0710b8157d73857aeaaeb9b2912926f8c879656e7887bda900e5f804f9bb12f5e993f0f36dfc7254de99938bad2b3adc6e504d081002ba8f2767f9a41b61045781f62715b5a5f766523cecc4cfc17094f02ae8e085552d99f60f6f96dbb52b7ead48e36d7b714ffa7e1a38a2d245e17450b9e6ca05955f4ee533ac6dc6637d68f473406f560e22d869b0ec9fa31c984434df06640b4db379ddfe0eba424468b8ac461070bff447cc557fe3c237a14a3fcbfb173a966fb8e06a71c07ff346d6e93db5b90b6b97d08b8146f5a000b81b4b0dd810a7741d2792d4df166ba9c057888bf8b2cb286948aad5826ae7a18e020accbe5c7252545e65ede12afb5b695e12 My device is a Surface Laptop 2 (Microsoft) and I constantly get the ("ok" it's me field). Since the latest update, Enpass goes into a continuous loop after Windows restart, Windows Hello does not start cleanly. Only quitting Enpass and restarting helps.

Push, Same Situation.

the actually well described function does not work as specified. In the Chrome extension, the main domain is also suggested to me, so the autofill remains without function. you have to select the correct entry manually. example: maindomain.test.com subdomain.maindomain.test.com in each case without port specification. My system: Windows 10 Enpass Windows Store Browser: Chrome Thanks Seger

@Pratyush Sharma @Kashish Especially the support of wildcard domains would also be very welcome: test.domain.de newtest.domain.de

you can always contact me and I'll help you. can write me a by pn and we then do a teamviewer seasion. Best regards,

WebDav solution via Synology WIN / IOS Hello everybody, Since I was also facing the problem and did not really get help here, I'll tell you now, how it works under Synology to 100% !!! Before a small remark: The service on WebDav was really not good of you and constantly to refer to a demo account and then not even a normal WebDav connection over other WebDav programs made to get though everything is running very clearly shows that in the case just did not put your prio! It was so annoying that you almost lost me as a customer, but now yes !!! Changes to the previous version: Apparently what has changed in the resolution of the local folder paths and thus always comes the error that he can not access! Solution: Create a shared folder "Enpass". Then I created another folder per user, for example "Test" The internal path looks like this: \ Volume1 \ Enpass \ Test \ Now very important, now you put again a folder at the Enpass means: / Volume1 / Enpass / Test / Enpass / In the folder "Test" you put your tresor / file: vault.enpassdbsync The final path for the user "test" will look like this: /volume1/Enpass/Test/Enpass/vault.enpassdbsync Respite ... ;-) In order for access to work on Enpass then the https must look like this (here it gets exciting and the actual error is visible): https: // example. DYNDNS.net:5001/Enpass/Test/ important here is the specification of the port. If you have specified an individual port, of course, just enter this port there ;-). Of course, in DSM the user who defines it will give the read / write permission to the shared folder and also the WebDav right under programs. That's it, it works! Either the team picks up the hint and corrects their faq or corrects the procedure. no matter what you do, please inform us about it so that we do not face the problem again that it will not work! Small note: Thus, you can create multiple safes / users and synonymous synonymous via WebDav Syncronieren. I have always created the user folder and the folder underneath if I already had a vault. I then put the vault in the Enpass folder as described above. I apologize for the bad translation, my english is cruel. If you have any questions I will try to answer them in English, but in German it would be much easier :). many Greetings Seger --------------------------------------------------------------------------------------------------- WebDav Lösung per Synology WIN/IOS Hallo zusammen, da ich auch vor dem Problem stand und hier nicht wirklich hilfe bekommen habe, teil ich euch nun mit, wie es unter Synology zu 100% funktioniert!!! Vorher noch eine kleine Bemerkung: Der Service zum Thema WebDav war echt nicht gut von euch und ständig auf ein DemoKonto zu verweisen und dann noch nicht einmal eine normale WebDav Verbindung über andere WebDav Programme hergestellt zu bekommen obwohl alles läuft zeigt sehr deutlich, dass ihr in dem Fall einfach nicht eure Prio gelegt habt! Das war so nervig das ihr mich fast als Kunden verloren habt, aber nun ja!!! Änderungen zur Vorversion: Anscheinend hat sich was an der Auflösung der lokalen Ordnerpfade geändert und somit kommt immer der Fehler das er nicht zugreifen kann! Lösung: Gemeinsamer Ordner "Enpass" erstellen. Dann habe ich pro User einen weiteren Ordner erstellt zum Beispiel "Test" Der interne Pfad sieht dann so aus: \Volumen1\Enpass\Test\ Jetzt ganz wichtig, jetzt legt Ihr nochmal einen Ordner an der Enpass heißt: /volume1/Enpass/Test/Enpass/ In den Ordner "Test" legt ihr eure tresor / file: vault.enpassdbsync Der finale Pfad für den Benutzer "Test" sieht dann wie folgt aus: /volume1/Enpass/Test/Enpass/vault.enpassdbsync Atempause ... ;-) Damit der Zugriff dann bei euch über Enpass funktioniert muss die https wie folgt aussehen (hier wird es spannend und der eigentliche Fehler wird sichtbar): https://Beispiel. DYNDNS.net:5001/Enpass/Test/ wichtig ist hier die Angabe der port angabe. Wenn ihr einen individuelle Port angegeben habt tragt diesen port da natürlich einfach ein ;-). In DSM dem Benutzer den ihr definiert natürlich das Lese/Schreibrecht auf den gemeinsamen Ordner geben und auch das WebDav Recht unter Programmen. Das war es, es läuft! Entweder nimmt das Team den Hinweis auf und korrigiert ihre faq oder korrigiert die vorgehensweise. egal was ihr macht, bitte informiert uns darüber, damit wir nicht wieder vor dem Problem stehen, dass es nicht geht! Kleine Notiz: Somit könnt ihr mehrer Tresore / Benutzer anlegen und entsprechend auch über WebDav Syncronieren. Den Benutzer Ordner und den darunter hängenden Ordner habe ich immer selbst erstellt wenn ich schon einen Tresor hatte. Den Tresor habe ich dann wie oben beschrieben in den Enpass Ordner gelegt. Ich entschuldige mich für die schlechte Übersetzung, mein englisch ist grausam. Wenn ihr Fragen habt versuche ich die in englisch zu beantworten, aber in Deutsch würde es mir sehr viel leichter fallen :). Viele Grüße Seger

Hello everybody, Since I was also facing the problem and did not really get help here, I'll tell you now, how it works under Synology to 100% !!! Before a small remark: The service on WebDav was really not good of you and constantly to refer to a demo account and then not even a normal WebDav connection over other WebDav programs made to get though everything is running very clearly shows that in the case just did not put your prio! It was so annoying that you almost lost me as a customer, but now yes !!! Changes to the previous version: Apparently what has changed in the resolution of the local folder paths and thus always comes the error that he can not access! Solution: Create a shared folder "Enpass". Then I created another folder per user, for example "Test" The internal path looks like this: /Volume1/Enpass/Test/ Now very important, now you put again a folder at the Enpass means: /Volume1/Enpass/Test/Enpass/ In the folder "Test" you put your tresor / file: vault.enpassdbsync The final path for the user "test" will look like this: /volume1/Enpass/Test/Enpass/vault.enpassdbsync Respite ... ;-) In order for access to work on Enpass then the https must look like this (here it gets exciting and the actual error is visible): https://example.DYNDNS.net:5001/Enpass/Test/ important here is the specification of the port. If you have specified an individual port, of course, just enter this port there ;-). Of course, in DSM the user who defines it will give the read / write permission to the shared folder and also the WebDav right under programs. That's it, it works! Either the team picks up the hint and corrects their faq or corrects the procedure. no matter what you do, please inform us about it so that we do not face the problem again that it will not work! Small note: Thus, you can create multiple safes / users and synonymous synonymous via WebDav Syncronieren. I have always created the user folder and the folder underneath if I already had a vault. I then put the vault in the Enpass folder as described above. I apologize for the bad translation, my english is cruel. If you have any questions I will try to answer them in English, but in German it would be much easier :). many Greetings Seger

+1

@Vinod Kumar okay and I wrote you back and told you that the standardport was changed and I come up with every other WEBDav program: I send you again a screenshot and you could try it again under the same password. but unfortunately I can not because your great side always thinks I'm a spambot and PN hardly go?!?

@Vinod Kumardo you want to give us or me any information? now I have already made a test access to my webdav server available? the data is as already written completely correct! my alternative webdav port I have written to you via pn. the right ones are and were right too. You can write and read with the testuser. With every other webdav program you can read, write and execute files / folders. can you or the team please accept this, would like to give you an unlimited unlimited access without a feedback to get! I am confused! status, a vault is created and set up via webdav sync that works. but as soon as I want to create a second vault on another local folder, although a connection is returned for the first time but the second sync attempt will cause an error. furthermore, no second sync file is created at all. maybe there is any user where it works?

Did you get my 2 PM, the PM thing is crazy, I do not see if I've sent you something that sucks a bit! @Vinod Kumar

@Vinod Kumar @all First of all thanks for the quick feedback! access rights to the folder are set, it is not. The connection to folder is also made. can I help you? the problem is that I can now use no more vault. many Greetings seger