search

Ruzihm / coin-chance

An open source crypto currency play-and-invest gambling site
GNU Affero General Public License v3.0
35 stars 23 forks source link

Having trouble getting it going #8

Closed fedaykinofdune closed 10 years ago

fedaykinofdune commented 10 years ago

I didn't see any way to contact you directly. I tried running the line in the readme to run the server in production mode but still get an error (internal server error) when trying to access the server. I'm fairly sure I've configured everything properly, but maybe I've missed something.

Ruzihm commented 10 years ago

I get these tickets in my email so this is good for me :+1:

The server process should print some info on startup and then some more stuff when each user visits the website. Is it printing anything? If it's printing an error, please copy and paste it here (feel free to censor the base paths to the server directory)

Also, if you have it configured SESSION_STORE_TYPE = "REDIS" , make sure you have a redis service running. If you don't have redis, you can set SESSION_STORE_TYPE = "MEMORY" until you get redis set up. The memory session store is not intended for production and may be slow, resource hungry, etc. If you have redis set up, there is the SESSION_STORE_OPTIONS variable that you can specify redis options as specified here

I'll add that info to the readme shortly, promise. If there's any more info you need to set it up I'll add that too. Thanks for your patience! :stuck_out_tongue:

fedaykinofdune commented 10 years ago

Ok, I got it, thanks! Sorry, I'm still a bit new with Node.js and I completely overlooked redis. Now I finally get to test it out! What about an administration account in the app?

Ruzihm commented 10 years ago

None yet :grin:

fedaykinofdune commented 10 years ago

Still having problems, got it running but when someone makes a deposit, it shows up in the "" default coin account but won't let them make a bet.

On Mon, May 12, 2014 at 8:11 PM, Richard Van Tassel < notifications@github.com> wrote:

None yet [image: :grin:]

— Reply to this email directly or view it on GitHubhttps://github.com/Ruzihm/coin-chance/issues/8#issuecomment-42907287 .

Ruzihm commented 10 years ago

Very strange, I have a few ideas of how that could happen. Are different users getting different deposit addresses or are they all getting the same?

When the server creates a new user account, it should give each user a distinct hash that is used to name the account in the wallet. When the main page is being rendered and the account address is determined, it will create the account in the address if it doesn't already exist. It sounds like either the hash isn't being formed properly, or that the wallet isn't creating the account at that time. Let me know if different users are getting different deposit addresses.

Also, what coin are you using? I want to make sure there aren't any incompatibilities in the API that need to be worked around.

Ruzihm commented 10 years ago

Also, the server is supposed to subsume user deposits into the "" account, then credit them for it in the database. I have changed the particulars of how that works in the last 2 updates. Try updating to the new version (0.3.2 at the moment) and see if that fixes it.

fedaykinofdune commented 10 years ago

ok, I will give it a shot here in a bit, thanks :) Been busy with work stuff.

On Thu, May 15, 2014 at 7:43 AM, Richard Van Tassel < notifications@github.com> wrote:

Also, the server is supposed to subsume user deposits into the "" account, then credit them for it in the database. I have changed the particulars of how that works in the last 2 updates. Try updating to the new version (0.3.2 at the moment) and see if that fixes it.

— Reply to this email directly or view it on GitHubhttps://github.com/Ruzihm/coin-chance/issues/8#issuecomment-43204234 .

fedaykinofdune commented 10 years ago

I updated it today and got it fired back up, sent a few coins in to check it out, it is making new accounts in the coin daemon, and I did confirm deposit, but after trying to log back in when the coins confirmed, site stopped responding so I checked the console session, found this:

loggin in via cookie getuserbalance Got balance: 4.32107405

/var/www/8chance/src/model/coin.js:101 exports.getUserBalance(task.userId, function (err, bal) { ^ ReferenceError: task is not defined at Object.exports.balanceQueue.push.func (/var/www/8chance/src/model/coin.js:101:36) at /var/www/8chance/src/model/coin.js:91:10 at Object.q.process as _onImmediate at processImmediate as _immediateCallback

Ruzihm commented 10 years ago

Thanks. That bug should now be fixed in 0.3.3

Closing for now, please feel free to reopen if you run into another problem :)