Who is interested to run his own Pool ?

[Jumper]

@tross

Yes, the wallet running and I can mine from another pc from my own network

the issue is accessing correctly from outside. And the error displayed in the console of Chrome clearly state the issue.

Server is running on 127.0.0.1:80 however I try to load the page from dogeserver.net:8081

That is triggering the error.

XMLHttpRequest cannot load http://dogeserver.net:4443/socket.io/?EIO=3&transport=polling&t=1475161326139-51. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://dogeserver.net:8081' is therefore not allowed access.

I just not able found out yet where to put the code to allow this.

Need to set the header as follow:

res.setHeader("Access-Control-Allow-Origin", "*");
res.setHeader("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept");

But in which file and which section.... That is my current brainstorming activity

[tross]

@Jumper port forwarding set correctly?

[tross]

@tross I got port 4443 80 8124-8125 port forwarding for my server

[Blago]

@Jumper https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS

[Jumper]

@tross

Port 8081 forwarded to port 80
Port 4443, 8124, 8125 is also forwarded

[tross]

@Jumper Try blago suggestion I am out of ideas

[Jumper]

@Blago

Thanks Blago. Yeap, I have seen that.

So far I have figured out that I need to modify the file called burst-pool-protocol.js, however I was not figuring out yet where and what to modify in that file.

I will not give up :)

[morantis]

I never had this issue. What the key was for me was to ensure that the wallet is running and fully synced prior to staring the pool. Make sure that ports 8123, 8124, and 8125 have a clear route in and out of the server and that the API settings are correct in the nxt conf file.

[Jumper]

@morantis

I am not sure how to make that work. I think I have tested all options.

I am sure this is related to the script itself. The script was created in 2014, and since many required node modules was updated. Especially socket.io

The error in the browser clearly tell what is the issue. However nothing online guide me to the correct solution.

When we call the pool address in the browser, this is a request on port 80 by default. However, I configured it for port 8081. The page is getting displayed.

However, not much data is shown there since the data shoul dbe pulled by the socket.io on port 4443 and that we can see in the error that it was blocked.

XMLHttpRequest cannot load http://dogeserver.net:4443/socket.io/?EIO=3&transport=polling&t=1475161326139-51. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://dogeserver.net:8081' is therefore not allowed access.

This is why the page dot display data from outside of my home network.

Again, if I load the page from the same computer using 127.0.0.1:8081 all works perfectly.

It is quite possible that with older version of required modules that might work, however the documentation of this script is nowhere exist.

@tross

Is is possible to share your script with me? If yes, before doing it, make sure you remove the sensitive info from the burst-pool-config.js file

I want to see what IP, Domains you configured in the files since I think you are also behind NAT with port forwarding.

Thanks.

[Jumper]

Just to add, at this stage, I can give away some coins if someone can fix that for me.

[tross]

@Jumper I was behind a nat with stacking but asked for a dynamic ipv4 address. I got one for a small charge. So that means my ip can change so I use NO IP client and services and point them to my server. I think your configuration is some how not complete. I took the software you are using edited the conf.js and was good to go. When I added the noip address updater then was all set for everyone else.
wallets : [
{
walletIP : '127.0.0.1',
walletPort : 8125,
walletUrl : 'http://127.0.0.1:8125'
}
],
redirection : {
enabled : false,
target : 'http://lhc.ddns.net:8124'
},
walletIndex: 0,
blockMature : 1,
txFeePercent : 0.0005,
poolFee : 0.010,
poolDiff : 10000000,
poolDiffCurve : 0.75,
poolPort : 8124,
poolPvtKey : 'XXXXXXXX-xxxxxxxx-xxxxxxxxx-XXXXXXXXXXXXXXXXXXXXXX-xxxxxx-xxxxxxx-xxxx',
poolPublicRS : 'BURST-BLAG-Z99X-NDR4-HFFF8', <<not mine (example)
poolPublic : '17525104813427443982', <<not mine (example)
poolFeePaymentAddr : '17930413153828766298', <<not mine (example)
defaultPaymentDeadline : 1440,
poolFeePaymentTxFeeNQT : 100000000,
httpPort : 80,
websocketPort : 4443,
enablePayment : true,
minimumPayout : 10.0,
clearingMinPayout : 100.0,
lastSessionFile : 'last-session.json',
cumulativeFundReduction : 1,
nextBlockFundSaving : 0.02,
logWebsocketToConsole : false,
maxRoundCount : 360,
sharePenalty : 0.000,
maxRecentPaymentHistory : 100

Some of my values are different but pool just pays differently

[Jumper]

@tross

Thank. Mine is exactly same as your .

So if you ping burstpool.ddns.net, it will resolve to your IP provided by you ISP.

PING burstpool.ddns.net (212.43.77.219): 56 data bytes

If I access your domain with the URL: burstpool.ddns.net or with IP:212.43.77.219 in both case I can see your pool page with data in it.

At your router, you must have been forwarded the ports otherwise no one would be able to reach your server.

On my side, I am not using NO IP, but another provider which update my ISP provided IP with the DNS of the domain I am using.

So when I ping my domain, it gets resolved to my ISP provided IP correctly

PING dogeserver.net (86.41.202.185): 56 data bytes

If I access domain dogeserver.net:8081 or ip 86.41.202.185:8081 I can see the pool page, however the cosole from browser display the error which try to load the data using socket.io

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://86.41.202.185:4443/socket.io/?EIO=3&transport=polling&t=1475247621823-3. (Reason: CORS header 'Access-Control-Allow-Origin' missing).(unknown)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://86.41.202.185:4443/socket.io/?EIO=3&transport=polling&t=1475247625875-4. (Reason: CORS header 'Access-Control-Allow-Origin' missing).

Based on what I have seen while trying to debug, i am confident to say that I would need the exact version of the following module which this script was created for. Especially the socket.ie.

The following I had to install using npm:

moment, request, async, prettyjson, json-markup, compression, express, http-proxy, body-parser and socket.io

All these have installed the latest versions for sure and I know for fact that since 2014 socket.io have changed a lot.

If you could give me the versions of these modules you have, that would help a lot with debugging this issue.

Thanks.

[tross]

@Jumper I am sure you got Node.js too so it beats me why it work rather easily for me and not for you???

[Jumper]

@tross

From the system where the pool server running, I open the browser and navigate to 127.0.0.1:8081, all perfect.
From another system on my home network, I call the IP of the pool server, 192.168.1.6:8081, all perfect

So it seems that this issue is only related when I call my internet ip or the domain pointing to my internet IP.

I think I will have to debug the complete code to see why this is not working.

[tross]

@Jumper To tell you the truth when I am having so much trouble and others are not I think "Format C:" and start over.

All joking aside maybe you did too many things to get this running and created a conflict on your system. Do you have another computer
you could try just to see if it is different? I cant remember ever little thing I did but I downloaded software install node.js did my conf and off I was loosing money but my pool ran. Back up start from the beginning.

[Jumper]

@tross
@Blago

Fixed :)

http://pool.dogeserver.net:8081/

After debugging the headers sent and received while in and out of mi network, I have found out that my NAT ing was the issue.

For whatever the reason is, the port 4443 was not forwarded from my router.

So I have changed it and voila, all up and running. Uff, that was not easy :)

Thanks for all your help

Now that it's working, I will adjust the CSS and will create a TOI, in case someone else wants to learn this.

And for sure, will leave the pool running so whoever want to use it, feel free to do so.

[morantis]

I have been giving thought to the redirect function inside the pool config. I am not sure how the rewards should be set. Pretty sure. Let's say that the pools address is XY and that I am going to mine to that pool with YY. Normally the address for the pool would be set to reward itself, as in solo mining.

I think the proper set up would be YY rewards to the pool address and mines to the pool. XY is the pool address and it rewards to wherever the pool redirects to.

Why would a single person of small group do this? Simple, if I have one account that mines, there is little reason to alter things. But, if I have two accounts that mine, then I set them to mine to the pool and redirect the pool to a larger more established pool. Total spent for reward assignments.....3, one for each address. Now, later down the road I decide to mine those two accounts to a different pool, instead of changing the reward assignment for all three addresses, I just change the assignment for my pools address and that costs a total of.....1.

Plus, two smaller miners are virtually pooling into the other pool and if the pool effect holds true, results are more coins.

[Jumper]

edit, I am getting my own coins heheh

[morantis]

@Jumper Awesome, I always use the analogy of locksmiths going against the magic door. Some show up with high tech gadgets and power, but sometimes that one lone locksmith, with one key is the one that opens the door.

[bvgfhrht]

@morantis Wow! This words are deep!