# PageSigner extension seems to have issues

**URL:** <https://bisq.community/t/pagesigner-extension-seems-to-have-issues/1935>\
**Category:** Uncategorized\
**Created:** [May 1, 2017, 11:22am UTC](https://bisq.community/t/pagesigner-extension-seems-to-have-issues/1935 "2017-05-01T11:22:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![valankar](https://bisq.community/letter_avatar/valankar/32/6_22734026db12803ebb3e059622ac3534.png) [@valankar](https://bisq.community/u/valankar)\
**Post date:** [May 1, 2017, 11:22am UTC](https://bisq.community/t/pagesigner-extension-seems-to-have-issues/1935/1 "2017-05-01T11:22:19Z")

</div>

Every time I’ve tried to use PageSigner I get socket timeouts:

![](https://bisq.community/uploads/default/original/1X/b8486cfe635c7dbabacb810f464debc3cda55dfe.png)

Though I have not yet had to use it (I was merely trying it out), I wonder whether this is a reliable way to prove payments. I am not sure how well this extension is written.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [May 1, 2017, 5:01pm UTC](https://bisq.community/t/pagesigner-extension-seems-to-have-issues/1935/2 "2017-05-01T17:01:09Z")

</div>

It works with about 70% of webpages. You can try to contact the TLSNotary guys on their IRC.

---

<div class="post-metadata">

**Author:** ![ZeroTax](https://bisq.community/letter_avatar/zerotax/32/6_22734026db12803ebb3e059622ac3534.png) [@ZeroTax](https://bisq.community/u/ZeroTax)\
**Post date:** [October 29, 2019, 10:41pm UTC](https://bisq.community/t/pagesigner-extension-seems-to-have-issues/1935/3 "2019-10-29T22:41:54Z")

</div>

> It works with about 70% of webpages. You can try to contact the TLSNotary guys on their IRC.

@ManfredKarrer  
Maybe that was true 2016-17. They got no support today. PageSigner is not working with TLS 1.2+ that is common now.

Due to problems with PageSigner the new **[Veruv](https://veruv.com)** cuould be used to certifiy bank statements. Usually the bank is not able to provide digitally-signed statements.

_“If it isn’t possible to generate the required proof with PageSigner, the user will be asked to request a digitally-signed statement from their bank with evidence of their position”._  
(Trading Rules and Dispute Resolution)

---

<div class="post-metadata">

**Author:** ![ZeroTax](https://bisq.community/letter_avatar/zerotax/32/6_22734026db12803ebb3e059622ac3534.png) [@ZeroTax](https://bisq.community/u/ZeroTax)\
**Post date:** [November 5, 2019, 3:15pm UTC](https://bisq.community/t/pagesigner-extension-seems-to-have-issues/1935/4 "2019-11-05T15:15:06Z")

</div>

> It works with about 70% of webpages. You can try to contact the TLSNotary guys on their IRC.

@ManfredKarrer  
Maybe that was true 2016-17. They got no support today. PageSigner is not working with TLS 1.2+ that is common now.