Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Payment pointer Bob fails #1717

Open
bourgeoa opened this issue Feb 4, 2023 · 10 comments
Open

Payment pointer Bob fails #1717

bourgeoa opened this issue Feb 4, 2023 · 10 comments

Comments

@bourgeoa
Copy link
Member

bourgeoa commented Feb 4, 2023

@michielbdejong
I skipped the corresponding test :

 1) API
       Payment Pointer Bob
         GET Payment Pointer document
           should redirect to example.com:
     Error: write EPROTO 139799603906496:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

      at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
@michielbdejong
Copy link
Member

Thanks for the heads-up.

Ah, this started failing because the cert on https://bob.com/ expired!
Should be easy to fix by changing "bob.com" to "example.com", or some other domain name.

@bourgeoa
Copy link
Member Author

bourgeoa commented Mar 12, 2023

replacing bob.com with example.com or service.com did not resolve the issue.

.expect('location', 'https://bob.com/.well-known/pay')

certificates do not appear to be old -rwxrwxrwx 1 root root 1285 Feb 17 16:59 cert.pem

Error: write EPROTO 140539925039040:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

@zg009
Copy link
Contributor

zg009 commented Mar 27, 2024

@zg009
Copy link
Contributor

zg009 commented Apr 6, 2024

@bourgeoa This test is passing for me on main branch when I removed the skip. I have self-signed certificates that I created less than a month ago. That could be your issue?

@bourgeoa
Copy link
Member Author

bourgeoa commented Apr 7, 2024

@zg009 No explanation. My keys are young and the test is still failing

# ls -al test/keys
total 32
drwxrwxrwx 1 root root  512 Mar 10 10:54 .
drwxrwxrwx 1 root root  512 Mar 23 14:55 ..
-rwxrwxrwx 1 root root 1285 Mar 10 10:54 cert.pem
-rwxrwxrwx 1 root root 1107 Mar 10 10:54 client-cert.pem
-rwxrwxrwx 1 root root 1679 Mar 10 10:54 client-key.pem
-rwxrwxrwx 1 root root 1679 Mar 10 10:54 key.pem
-rwxrwxrwx 1 root root 1386 Mar 10 10:54 user1-cert.pem
-rwxrwxrwx 1 root root 1703 Mar 10 10:54 user1-key.pem
-rwxrwxrwx 1 root root 1314 Mar 10 10:54 user2-cert.pem
-rwxrwxrwx 1 root root 1675 Mar 10 10:54 user2-key.pem

@zg009
Copy link
Contributor

zg009 commented Apr 7, 2024

@bourgeoa I am running NSS tests on WSL v2 in Ubuntu 20.04. My version of OpenSSL is 1.1.1f. It may be a versioning/OS issue.

@bourgeoa
Copy link
Member Author

bourgeoa commented Apr 9, 2024

@zg009
You are right the test passes with WSL2 in ubuntu 20.04, but fails on WSL 1 that I am normally using
On the contrary with WSL2 an other test fails in http-test.js (POST multipart) but succeed in WSL1

Strange

@zg009
Copy link
Contributor

zg009 commented Apr 9, 2024

@zg009 You are right the test passes with WSL2 in ubuntu 20.04, but fails on WSL 1 that I am normally using On the contrary with WSL2 an other test fails in http-test.js (POST multipart) but succeed in WSL1

Strange

@bourgeoa Can you point out the line it http-test POST which fails? All of mine are passing on WSL2.

@bourgeoa
Copy link
Member Author

bourgeoa commented Apr 9, 2024

This is the test that fails for me on WSL2

describe('POST (multipart)', function () {

@zg009
Copy link
Contributor

zg009 commented Apr 9, 2024

This is the test that fails for me on WSL2

describe('POST (multipart)', function () {

This is working for me on WSL2 on the main branch. I'm not sure what the issue could be just scanning the file. Can you rerun it and show the full error? I'm wondering where it is failing the test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants