Who is interested to run his own Pool ?
-
I wouldn't mind running one, but would have to learn the software etc. I have access to a virtual environment that I could throw it up pretty quickly. Also have a decent VPS that could probably handle it (linux)
-
I've been looking into the code a little and set up the pool on my own computer, and connected to it from one of my miners, but it was giving weird deadlines. So I will have to continue working on it. I saw that I can rent a server from 1&1 for 10 bucks a month which runs windows server.
I am still interested, just need to figure things out more.
-
Well, I have a pool running however I don't have any miners on it yet. I am going to add my laptop to it, however I dont have space on it really (plotting 10 gigs as we speak)
If I could get a couple of people to check it out and let me know, here is the address (no domain name, yet)
Its basically straight out of the box, but it gives me something to learn and play with, and help spread the burst love!
Let me know if you try to connect and how it goes.
-
Well I took it down for the night. I was getting a lot of weird deadlines and strangeness. Here is a screen shot:
-
I got a pool locally running and seem to be doing ok with one miner. My problem is my ISP hasnt changed my ipv4 address yet. So cant access from the outside.
Another problem is web designing. I need to fix some stuff so learning on the fly. Rome wasnt build in a day.
-
Did you guys was able to set this up?
I have tested myself as well. I did not have any issue to connect my miner from the same network, however, from outside of my network the pool page was simply not loading data.
When I inspected what happening I have seen the following ajax error:
cors header 'access-control-allow-origin' missing
No issue when I load the pool url locally on the same server.
I have done port forwardings: Port 80, 4443 and 8124 but still the same.
I have also modified the hosts file to make sure locally all resolve to 127.0.0.1
Does anyone know what to change in any of that JS file to make that work?
-
@Jumper I forgot about this post wish I would of updated. The problem was my ip was stacked meaning it was behind a Nat. I contacted them and for a small fee they gave me a dynamic address. So no I use NOIP and all works well. This German ISP wanted me to try with IPv6
but couldnt figure out how I could host a website and anyone could access.
-
Thanks for the quick response.
I have a domain called Dogeserver.net, which for sure host a website on port 80. I am hosting this at home, so I have the port forwarding set to my local IP
I am using a service similar to noip.org to pint the domain to my internet IP so all this setup correctly.
For the miner, since I am already using port 80 on my network, I set port 8081 to be forwarded to my burstpool server on port 80
If you try dogeserver.net:8081 you should see a page, and as an example in crom you right click and go to inspect, then console tab, you would see all these errors.
So somehow in the script I need to allow Access-Control-Allow-Origin
-
@Jumper Are you running a wallet?
-
@tross Mine looks like that before wallet server is started!
-
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
-
@Jumper port forwarding set correctly?
-
@tross I got port 4443 80 8124-8125 port forwarding for my server
-
-
Port 8081 forwarded to port 80
Port 4443, 8124, 8125 is also forwarded
-
@Jumper Try blago suggestion I am out of ideas
-
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 :)
-
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.
-
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.
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.
-
Just to add, at this stage, I can give away some coins if someone can fix that for me.

