So I have my stake pool up and running and wanted to check whether the metadata is crawled as it should but when I check https://smash.cardano-mainnet.iohk.io/api/v1/errors/f2132a2d557dc1d00fcc58fe3fdf64e89d1fe080625afd32b60999e0. It shows an invalid URL error.
Thanks a bunch! I completely forgot to forward port 6000 on my ISP’s router…
Do you happen to know if IOHK will retry crawling the metadata or would I need to (re-)issue it myself?
So I’ve waited some time now but my stake pool still won’t show up in daedalus or adapools.org and even though I’ve registered my relay to the topologyUpdater, it won’t register my relay in the topology.json.
Any thoughts on what I can do to get my pool registered?
Hi, thanks for thinking with me.
That’s definitely weird… I have tried the same command previously. When I try the same command I get the json file without any such captcha (as seen in the picture).
I have contacted my web hosting company to clear things up but I am afraid there is still another issue at hand because pool.vet seems to be able to crawl the metadata without issues as well. Any other ideas?
Additionally I tried from my other machine and it shows same error, with captcha.
Interestingly enough from my VPS in oracle cloud or from my dedicated servers in OVH it doesn’t work, but from VPS in Cantabo everything is fine and from my home IP it works too. So seems your provider has some weird logic, so some VPS it trusts and other it doesn’t and IPs from home providers are whitelisted, so that why you don’t get this error from your PC.
In any case, move your metadata file somewhere else.