Topic: Azure Free Credits for Mining Monero or CN-Heavy:Super Easy and Super Profitable - page 12. (Read 24184 times)

1 Hour Avg. Hash Rate = 1.66 KH/s

Good job!
Setup done and has been running for about 45 minutes.
No tweaking has been done and running 10 nodes in one pool.
Currently doing around 1.8 KH/s which is great.
Will report back with hashrate after a few hours.

OK, great. Just remember that there are some options to tweak your setup at the end of the guide. The main tip is to create multiple azure-batch-pools with fewer nodes instead of a single azure-batch-pool with many nodes. You'll have to click a bit more to setup everything but in my experience the increase in hashrate is worth it.
 

I am going to try this and if it really gives anything close to 1600 H/s then the 4% fee is well worth it!

Just to be clear: this includes the 2% dev-fee going to the developers. I definitely don't want to rip off the developers.
Also, i try to be very upfront about the increased fee. Nobody is forcing you to do this. If you are already making full use of your azure-account then my guide probably is not for you.

And about keeping it to myself: mining in azure has been going on for some years now. I'm pretty sure Microsoft is fully aware of the situation. If they wanted to change things, they would have done so long ago.

doesn't mean its worth 4 percent fee roflamo, unless your a super lazy cat and you've got money to toss around. 2 percent fee sure as that's the going rate for devs around here, but your requesting 4 percent indefinitely. there isn't any amount of work you could do that would be worth it at 4 percent. nothing more than a greedy prick like the rest and danm does it show


tbh you should have kept it to yourself, now you've let the word out so maybe Microsoft azure will pick up the ball quick and realize people like are doing and follow suite like google and others. people like yourself give crypto a bad name just for the sake of a few extra bucks at everyone else's expense, like the people actually paying for azure services and using them for a legit purpose without affecting other people on a server in which other vm's are running. this is why google and others don't deal with crypto, straight up abuse of there shit

Yes, there are some other guides on the web and on youtube. However, so far i have not seen a guide which gives you the following features:

• Super-easy setup: other guides are much more complicated. Also, because the batch-service is used, you can easily adjust the number of desired VMs to the amount of free credits you have (no need to setup individual VMs)
• Zero maintenance effort: Since the other guides are not so cost-effective they expect you to restart your VMs every month (or they only talk about one-time signup-credit, not about monthly free credits from an MSDN-subscription). I believe this is the first guide which will produce a steady mining-income with zero-maintenance after the initial setup
• Last but not least you'll get a great hashrate. The script on my site has a auto-tune feature, which will adapt itself to the load present on the physical server. This is also something i have not seen anywhere else.

This is how to setup own mining pool based azure.Youtube have many instruction and free.

Agree, The rules referring to the 3rd party cloud mining services, what OP want to point out is your own cloud mining and totally different

@OP, how does it differ if we could use other mining app out there compared to yours? 4% is a bit high for the fees

I assume that "Cloud services doesn't belong here!" refers to services like hashflare... Note that what i am describing in this post is very different. Also i have seen several guides for setting up azure in this very subforum, so i honestly believe i am not breaking any rules here.

Just read the 3d over you :

it says:
Cloud services doesn't belong here!

Its pinned by the admin so you know what's going to happen

Hi everybody,

There are many guides on how to setup azure-servers for mining cryptocurrency. However, this one is different. If you follow this guide, you'll get these features:

• 5 minutes to setup
• After setup, it will run indefinitely - no need to even log in to azure after the initial setup (you'll need a MSDN-subscription with monthly free credits, though)
• Attractive hashrate - currently i get around 1600 H/s, which yields around 75$ worth of Monero for my 150$ monthly free credits

So how is this possible? Well, first of all we'll be using the low-priority batch service to keep the cost down. Like this we can have several servers running for the complete month. After one month, your new monthly credits will arrive, leaving your servers and the complete setup running indefinitely.
 
The setup of the azure severs is so easy and fast because i already did the hard work for you: On my website (link see below) i have created some handy javascript which takes your wallet as input and spits out your personal customized startup-script for the azure-batch-service.

Lastly, the hashrate is so high because the script has a clever self-tuning feature which will adapt itself to the load of the physical server azure places your virtual machines on. If you are lucky, you'll have lots of idling neighboring VMs, and then the mining-software will be able to employ more of the precious L3-Cache of the Server.

Here's the link to the complete guide for mining Monero:
https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency.html
Everything is hosted on github. Check out the code if you have any doubts about the function of the script!

If you are interested in other Cryptonight or Cryptonight-Heavy-Coins, see this link: https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency_detailed.html

I have been mining like this for some months now. So far, the azure-VMs have been running smoothly without any problem (unlike the VMs from google's or amazon's cloud-service, which apparently get automatically shutdown once they detect that you are mining cryptocurrency).

If you have any questions or problems feel free to PM me or reply in this thread.

---

Extra info: How to add a worker-ID. The procedure depends on the used pool (check the pool's documentation to find out more). If your pool is already running, you'll have to restart the nodes in your pool for the changes to take effect.
1. supportXMR.com (or similar pools expecting the worker-ID in the password-field)
Have a look at the generated startup-script. It will start like this:
The worker-ID is the string between 'pool_pass1=' and ':azurecloudminingscript'. Just replace the 'x' with your desired worker-ID, e.g.
would result in the worker-ID "superhash". The string 'azurecloudminingscript' is the default-password for the login at the pool. After logging in there's an option to change the password and to set your email for getting the notifications from the pool.
2. xmrpool.eu (or similar pool expecting the ID as part of the wallet)
The pool expects the worker-ID as a suffix to the wallet. Check the pool's documentation to find out the exact format. xmrpool.eu expects a "+"-sign. This can be directly entered into the wallet-field in the html-form on my website. So instead of just putting e.g.

into the form, you would enter the string
into the form. With the generated startup-script you'll have the worker-ID "superhash".
3. Using the Azure-Pool-Name as worker-id: There are some pre-defined variables that you can also use:

• ${AZ_BATCH_POOL_ID}    : The name of the azure-pool used
• ${AZ_BATCH_ACCOUNT_NAME}    : The name of the azure-batch-account used
• ${AZ_BATCH_NODE_ID}   : The name of the azure-pool-node. Typically this is a complicated name with some special characters. Use at your own risk!

Have look at the script generated by the quickstart-guide for an example how to use the  variable ${AZ_BATCH_POOL_ID}.

---

Extra Info: Troubleshooting
Most problems can be diagnosed by looking at the output of the mining-software (xmr-stak). To see the output, you first have to connect to the node. In the azure-portal, go to your pool, then click on "Nodes" on the left pane. The list of the nodes in your pool should appear, click on the node that is making trouble (or any of them if  e.g. you have a hashrate of 0). Then, on the top pane, click "Connect". Fill a username and password and enable admin-rights (the default-value of the expiry-time never works for me - i always just put this a few days in the future).Then click on "OK".
If you are running linux on your desktop actually connecting is really simple: just copy the displayed ssh-commandline to a terminal. If you are running windows you'll have to use putty (you'll just have to fill the displayed server-details. Post in this thread if you need help with this).
Once your ssh-connection is running, type
You'll have to scroll down a bit get to the log from xmr-stak. Some problems (like connection-problems to your pool) will be obvious when reading the log. Otherwise you can post the relevant parts here and i will try to help you.

---

Full disclosure: The donation-level of the mining-software used is set to 4%. Half of this (2%) is going to the developers of the mining-software (xmr-stak), the other half is going to my pocket. You can view this as a convenience-fee for getting a tested and streamlined mining-script.

P.S.: You don't have a MSDN-subscription with free azure-credits? I have seen some people selling those here in this forum (see the subforum Economy > Marketplace > Goods > Digital goods. I have no practical experience buying MSDN-subscriptions this way, though).

Edit: added info about Sumokoin
Edit2: added info about workerid
Edit3: some more info about workerid: pre-defined variables
Edit4: added info about troubleshooting