Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Shoko

Pages: [1]
1
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 03, 2017, 10:01:18 am »
Sorry I forgot to add I actually tried to send it without the password part! Could it be the length maybe?

For the Cloudflare cache, I know that it can cache a lot of things including js files so I'm not sure if that was modified? I'm only saying that because I'm pretty sure I tried with multiple browsers and with my previous sessions cleared, but maybe I actually didn't!

Thanks for all the work! Happy to help if you need anything else!

2
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 03, 2017, 09:39:04 am »
Thanks!

Usually I'm testing things using Chrome in incognito mode so that I have nothing from previous sessions (cache, cookies, etc.) and also no plugins enabled. I do the same thing in Safari and Firefox if I see that it is not working in Chrome just to be on the safe side.

I managed to successfully edit your ticket and reassign it back to you. I also managed to create two tickets:
-One with the body field empty.
-One with test2 in the body field.

The reasons I did is that is that I first tried to submit a ticket with this content in the body field:
"
I have a long (25+ chars) and complex (lots of special characters) password and for some reasons I couldn't log in on the new pool. This is the error I was seeing in the console (Failed to load resource: the server responded with a status of 500 (Internal Server Error) /pool.ashx)

I changed my password to something more simple and I could log in on the new pool. I tried to switch back to my original password and I was getting the error 500 again.

This is the password (not used anymore) that wouldn't work with the new pool. Hopefully it will help with debugging:
[4i.r2Zugkb4WxbTTLy&[email protected]
"

For some reasons, I get the error 500 when trying to send that.

Also I was thinking, would it be possible that Cloudflare keeps in cache some of the files you're updating? As we're probably not using the same CDN servers, maybe if don't flush it manually we're getting different versions of theses files when rapidly updating them?

3
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 03, 2017, 09:18:06 am »
So I tried different things:

-I tried creating a new account on pool.biblepay.org. I can log in on pool.biblepay.org but not on pool2.biblepay.org (getting the invalid username/password error).
-I tried creating a new account on pool2.biblepay.org. This time I can log in on both pool.biblepay.org and pool2.biblepay.org.

Unfortunately I still can't log in on either pool with my original account :(

4
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 03, 2017, 08:26:56 am »
I did try first to just edit it first without modifying anything else. I also tried different combinations of just modifying the the "body", "submitted by" and/or "assigned to" . I also tried to just open it without modifying anything and just clicking on save but it was throwing the error 500 in every case :(

I was about to try again but I'm now having  a different issue. The pool (old and new) doesn't seem to be recognising my password anymore?

5
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 03, 2017, 07:58:18 am »
Hi Shoko-

The ticket system was written by my company and included in a prior product that I never released, so its just being shoehorned in to see if it is valuable for the web issues (in contrast to the qt-Client issues on github), so thats why its kind of malfunctioning as it has not even been configured for its intended use.

So looking at this, the ticket number field is supposed to auto increment when a new ticket is added.  FIXED.

The submitted by field is supposed to be populated with the submitters name: FIXED

The permission-view behavior by the other users on the system is supposed to respect the permission tree of the system based on the roles they play.  Since the roles are missing, everyone can see everyone elses tickets.  I am just going to leave it like that for a little while, so we can send each other tickets and escalate things to each other who want to become managers in the phase between now and the masternodes burn in period.  I could see assigning certain things to my team members who start in IT, and non-IT issues to non-it team members.

So if you want to go ahead and add it again, and then see if you can view the ticket list and click on it also.

Thanks.

Hi Rob,

I saw your ticket and can only see the ticket 902 and can click on it to see the details.

Apologies for not replying using the ticket system but it seems I am still having troubles with submitting/updating a ticket. I'm still getting the same error 500 when pressing the save button. This happens whether I'm trying to create a new ticket or update yours.

6
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 02, 2017, 09:47:40 pm »
I tried to create a ticket just now and it doesn't seem to be working unfortunately. I filled all the fields and this is the error I get when pressing the save button:

POST http://pool2.biblepay.org/pool.ashx 500 (Internal Server Error) jquery-1.12.4.js:10254

I'm also a little bit confused by how we're supposed to fill that form. What are we supposed to write in the "Ticket Number" field? I tried putting 1 in my attempts but is it supposed to be a number automatically generated instead?

Also, I was wondering if everyone could see all the tickets submitted or if they could only be seen by the account who submitted them. If it's the latter, would it be better to have the author of the ticket automatically be handled by the server instead of the "Submitted by" field? For example, in the case of someone pretending to be someone else and claiming they have issues accessing their account, etc.




7
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 02, 2017, 05:24:51 pm »
I had to manually do "addnode" to be able to get my first connection and download the blockchain. I did wait a few hours before doing that but I'm not sure how IPs of node are advertised and if it would have been able to find a connection by itself after some time. (Could that also interfere with trying to hide the IP of the server behind Cloudflare?)

My new miner seems to be working on both pools. Did a tcpdump and it looks like the miner and the pool are using port 80 to talk to each other? If so, it would make sense that it is still working with Cloudflare since port 80 is forwarded to the actual server.

I did find this article:
https://support.cloudflare.com/hc/en-us/articles/200169156-Which-ports-will-Cloudflare-work-with-

It looks like Cloudfare wouldn't be able to be used with port 40000 :/

I'm wondering if the connections you see are from nodes that had established connection with the biblepay server before you enabled Cloudflare?

As a side note, I know it's not really a priority right now but did you see my post where I wouldn't be able to log in and was getting an error 500 on pool2 depending on what password I was using?



8
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 02, 2017, 08:25:44 am »
I totally missed the part where you said you switched to cloudflare, I just realised that after looking more closely at the latency and the whois of the IP. I totally feel stupid now :P.

So I'm still having issues with deploying my new miner (0 connections) and thought it was an IPv6 issue first but it seems to actually be more of a Cloudflare issue.

I'm not sure how Cloudflare works exactly but I remember the wallet initially tries to connect to node.biblepay.org on port 40000 and I was wondering if this was still forwarded to the actual server. I tried doing telnet node.biblepay.org 40000 with no success. I tried to do the same with the actual IP of the server and it worked this time.

Concerning IPv6, I don't think there should be any issue since Cloudflare does a 6to4 tunnel so it should be totally transparent for the biblepay server.

It also might be a good idea to get a new IP for the biblepay server as it would be easy to just look at the first pages of the bitcointalk forum to find the actual IP address of the server and DDOS it, totally bypassing Cloudflare.



9
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 02, 2017, 07:54:34 am »

EDIT 2: Realised that the ipv4 also point to the same ip address for both pools, my bad. I thought they were different. Yes I do point my miners to pool2.biblepay.org. I had restarted the miners so they would load the new config and I'm running 1.0.2.8. I saw them showing up in the leaderboard on the old pool so I assumed it was still using that pool instead of the new one.

Quoting my previous edit in case you missed it, I wasn't expecting you to answer that quickly haha.

I'm actually using both ipv4 and ipv6 but I guess it's defaulting to ipv6 when available. Everything has been working fine so far =D.

I'm not sure if something changed but I've just deployed a new miner and it doesn't seem to be able to connect the seed node for the initial download? I'm wondering if it's trying to connect using ipv6 and getting denied? I will just disable it I guess and see if it works :P

10
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 02, 2017, 07:43:01 am »
I actually managed to find the cause of my login issues. I have a long (25+ chars) and complex (lots of special characters) password and for some reasons it doesn't work on the new pool. I changed my password to something more simple and it started working. I tried to switch back to my original password and I was getting the error 500 again.

EDIT: I was going to post this reply just when you did.

The ipv6 addresses of pool2 and pool are actually the same (2400:cb00:2048:1::6819:fa6e). So somebody using ipv6 will have pool and pool2 point to the same address. Only the ipv4 addresses are different.

EDIT 2: Realised that the ipv4 also point to the same ip address for both pools, my bad. I thought they were different. Yes I do point my miners to pool2.biblepay.org. I had restarted the miners so they would load the new config and I'm running 1.0.2.8. I saw them showing up in the leaderboard on the old pool so I assumed it was still using that pool instead of the new one.

11
TestNet Discussion Archive / Re: TestNet Testing Thread
« on: September 02, 2017, 07:14:24 am »
I've been trying to log in on the new pool without success :(. I tried multiple browsers and I always get this error in the console "Failed to load resource: the server responded with a status of 500 (Internal Server Error) /pool.ashx". I'm not sure if anyone is having the same issue?

Also, pool2.biblepay.org has the same ipv6 address as pool.biblepay.org. I got my miners banned when trying to test the new pool as I didn't realise that I was still connecting to the old one :-[

Pages: [1]