GIve it some time. Can take a few hours to a day, if everything has been configured correctly, to show up.
Hit me up on my channel https://t.me/bladarunner if you want to talk more about this.
Thanks for your reply. I launched my pool a few hours ago. There was some issue with the metadata file, I fixed and re-submitted the transaction. Adapools picked up the update immediately, but not pooltool and Daedalus. I will wait for some time.
I made sure that the json file I had locally was the exact version I had on my AWS host. I did this my uploading the file directly, not cutting and pasting the text.
I re calculated the hash of the metadata file.
Built a new transaction using the new hash and submitted it.
— Those are the steps that worked for me.
However I did hear of someone having their text editor insert crazy characters in the json file that ended up giving them this grief as well.
I had the same issue where I was sure that the hash of the metadata file matched the file, but my pool didn’t show up on pooltool nor on daedalus.
My pool was shown as red here https://adapools.org/daedalus, so I dug a bit deeper.
My metadata.json file was using windows-style new lines (CRLF), and after I fixed this and submitted the new hash, my pool showed up on both pooltool and daedalus.
So if your pool is not showing up, check the new line characters in your metadata.json file.