Jump to content

PunishmentOfLuxury

Bronze Member
  • Content Count

    977
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by PunishmentOfLuxury

  1. Eri is my favourite crypto YTer, but I think she's joining dots that don't exist in this ABB video. Shadni is clearly a TM squatter.
  2. Success!! I solved the problem by moving from AWS to GCP. Google Cloud enables TLSv1.3 whereas AWS is only on v1.2. It may also be necessary to enable HTTP2, but not sure about that. The CORS headers were not the problem. In fact, the new configuration still fails the payidvalidator test (not with a 404, but 0 error code), but the payme$mydomain address resolves fine with Xumm.
  3. There's a Discord channel for PayID, it was mentioned in the Dev Conference video as chat.payid.org. Cannot find it on the Discord app - anyone have an invite link for it?
  4. Thanks, yes I have now included that line, plus a few others under the <Directory /> section. I followed the guidelines in Set CORS (Cross-Origin Resource Sharing) Headers and these instructions Setting CORS (cross-origin resource sharing) on Apache with correct response headers allowing everything through. The great news is, I got rid of all the CORS issues flagged by the PayIDValidator. BUT I still get a 404: I also tried the testing script outlined on the first link above and loaded it into my browser. Looking in the console, I see: I'm really puzzled because I can load https://mydomain/.pay/payme.json in my browsers, but somehow it's not accessible to the PayID protocol. So, I turned my attention to the Apache RewriteRule as shown by Matt: I tested the Rewrite Rule line only with this helpful resource: Test your htaccess rewrite rules. Https://mydomain/payme maps correctly to .../mydomain/.pay/payme.json So now I suspect the RewriteCond is not working correctly. Or I'm doing something really stupid. Been struggling for with this for days.
  5. Some progress: I thought maybe I had too strict <Directory> rules in httpd.conf. I loosened them for the directory .../mydomain/.pay with "Require all granted" and now I can see the listing of the directory, and can view files payme.json and test.html, in a web browser. But the PayID validator says exactly the same as it did before - a 404. Matt's address returns HTTP Status Code 200 (meaning "The resource has been fetched and is transmitted in the message body."). Why am I getting a 404 if the json file is where it should be and readable according to my browser? (Matt's address also fails all of the Header Checks, but there is extra content listed after that relating to the retrieved file.)
  6. Those highlighted folders are not present on my AWS instance. Thanks, Matt. I restored the backslash and tried the validator. The results are very disappointing (Your own PayID address is given a score of 44% by the validator.) Seems like the protocol is not reading the files. What permissions should I set for the .pay folder and the payme.json file? I have 755 and 644 respectively.
  7. According to https://docs.payid.org/payid-headers there seems to be a syntax error in "%{HTTP_ACCEPT}" "application/xrpl-mainnet\+json". There should be no backslash according to the official site. I deleted it but my PayID still doesn't work in Xumm, nor in Gatehub.
  8. Thanks again @NightJanitor - it will take a fair bit more learning on my part before I can understand everything you wrote. But I have made some progress. I started over with a fresh AWS AMI Linux 2 instance (as opposed to Linux 1 first time around). The installs of Apache and Certbot went much more smoothly than before. I got the required SSL certificates and all was good with https access to mydomain and www.mydomain. SSL Labs gave an A rating for both. That was before I fiddled with httpd.conf. I tried adding the code as listed in post #1, but it broke SSL again. Then I inspected /etc/letsencrypt/options-ssl-apache.conf and replaced the SSL configuration in httpd.conf to mirror it: Tested again with my browsers - padlocks everywhere - yes!! SSL Labs now gives me A+ for both my domain and www.mydomain. It's allowing TLS 1.2 only. However, testing with Xumm, I still can't get the PayID section to work. I'm not sure how the rewrite code got into <VirtualHost InstancePublicIP:80>, I don't remember putting it there. I think Certbot did that. I wouldn't have thought it would affect Xumm because the PayID protocol mandates SSL and isn't going to be polling port 80. The other content there came from Let's Encrypt with Certbot on Amazon Linux 2: Anyway, I then commented out all the rewrite lines in the current Listen 80 section, leaving the code directly above, but nothing changed - SSL still good, PayID no joy. I can't find .htaccess anywhere (using ls -a). It's not in /var/www/html. I guess your distro is different.
  9. Thanks. I see what you mean about my having the server name and alias swapped cf. Matt. But his .pem files are in his www.HISDOMAIN folder whereas mine are in my MYDOMAIN folder. This arrangement of mine could be the consistency of tiny minds, and entirely irrelevant to the problem, or crucial - I'll wait for further input I didn't know about .htaccess, will check it out.
  10. Sorry, I wasn't clear - I'm talking about old Rippletrade names (~nameexample) with Bithomp.
  11. Works a treat with Rippletrade names - knew they'd be useful one of these decades.
  12. I'm totally new to Apache, so excuse me if I've made a silly mistake. I am trying to follow Matt Hamilton's example. I started an AWS EC2 free micro instance, Linux AMI (not Linux 2). I registered a domain name and pointed it at the public IP of the instance. Apache installed fine and I was able to get it to serve index.html from /var/www/html folder. Then I used Letsencrypt Certbot according to this guide to generate certificates. It seemed to work because when I went to https://mydomain and https://www.mydomain I got the padlock icon in my browser, plus the analysis from www.ssllabs.com/ssltest/analyze.html?d=mydomain was A, almost perfect, for both alternative URLs. The .pem files are where they should be. Then I edited /etc/httpd/conf/httpd.conf. I only quote the sections I edited: I set permissions as: sudo chmod 755 /var/www/html/.pay and sudo chmod 644 payme.json Restarted Apache. Curiously I've now lost SSL for www.mydomain but not for mydomain. SSL Labs shows "Certificate name mismatch" for www.mydomain. I tried making a Xumm payment to payme$mydomain but the app says "server not found". Any help gratefully received!!
  13. Would be nice for UK folks if Binance Jersey followed suit.
  14. This route is no longer open. TW will not accept deposits from Kraken, since the former changed its bank. You can now trade XRP/GBP on both Kraken and Bitstamp. Unfortunately volumes are tiny on Kraken; a lot better on Bitstamp, but still low in comparison with XRP/USD for example. I don't know if either exchange offers withdrawals to a UK bank account via Faster Payments.
  15. This route is no longer open. TW will no longer accept deposits from Kraken, since the former changed its bank. You can now trade XRP/GBP on both Kraken and Bitstamp. Unfortunately volumes are tiny on Kraken; a lot better on Bitstamp, but still low in comparison with XRP/USD for example. I don't know if either exchange offers withdrawals to a UK bank account via Faster Payments.
  16. Thanks for making the fix, @Warbler One more thing, though. On v 0.4.8 "Scan QR Code" doesn't work on Android 10 Chrome. It seems that the page doesn't ask for permission to use my mobile camera, so I just get an expanded blank white space when I tap that button. I tried setting the camera permission for bithomp.com in Chrome settings but it isn't possible - the webpage has to ask for it.
  17. Problem solved. Bithomp just now updated their submit page to version 0.4.8 and I tried the Tx blob string that had failed a few hours ago and now it's gone through! I'm very relieved. I am a bit puzzled why the exact same Tx blob previously failed with Xumm, Ripplerm and Padanaram.digital, though. EDIT: @Kakoylafound the problem. Bithomp includes a bit of extra text in its Tx blob that other sites don't use - don't know what its purpose is, but it prevents non-Bithomp sites from submitting a valid transaction with a Bithomp generated blob.
  18. Calling @Warbler I tried again with a freshly downloaded copy of Bithomp Tools from Github. Same problem, cannot submit the offline-generated TX blob with the Xumm app or with Bithomp submit or with Padanaram.digital. If I use the Decode function on the Bithomp submit page, the output gives the correct source and destination addresses, sequence number and transaction type. I don't know how to interpret the rest of it and I don't really want to post it here. I can ping xrpl.ws but pings to s1.ripple.com are intermittent, some fail, some connect. I guess I could try using the Ripplerm wallet offline, but it's not very user friendly.
  19. Thanks, that's useful info. Are you saying that all transaction blobs created by Bithomp Tools in offline mode are set up to be sent to s3.ripple.com? I thought the actual server would be chosen by the online site doing the submitting, but I don't know much about this techincal stuff.
  20. I'm having trouble submitting aTX blob that I created on an offline PC with Bithomp Tools. I tried scanning the QR code with Xumm on my mobile and it just gave me a blank page, no warnings of errors. Then I went to bithomp.com/submit online and pasted the TX blob string into the box. The Submit button just keeps on throbbing, no error thrown up. There are a couple more sites for submitting TX blobs listed in this thread, but none of those work either. Perhaps it's my internet connectivity, though I tried both home wifi and mobile networks. What addresses should I ping to check connectivity with the XRPL servers? EDIT: I can ping both s1.ripple.com and s2.ripple.com. I tried both servers in the Ripplerm online wallet, but when I submit the blob I get "undefined: undefined" as the response in both cases.
  21. @Warbler When I go to bithomp.com/submit/ on my mobile, I get: I tried two different internet connections, one wifi, one mobile. "Loading" never stops. QR code scanning doesn't do anything - camera doesn't appear.
  22. As no doubt does Cobalt, the XRPL turbo option that no one at Ripple (that means no one anywhere) is working on. Good summary of the nonsense that has surrounded XRP for years, @SquaryBone
  23. I used the David Schwartz method without being a coder. I googled for instructions. If the person is not up to that, then they have to trust someone who is not with Ripple because that company is banned from creating a wallet. If I had to trust any non-Ripple employee in this space, it would be Wietse Wind, who is indirectly funded by Ripple. I gave his solution as well, which requires nothing more than opening an html file in a browser.
×
×
  • Create New...