Cloudflare connection discrimination breaks Console pages

[mashdragon]

When I try to load the Console (https://console.akash.network/) on Tor Browser, the loading spinner spins forever, blocking access to the Your Account section. The reason is that requests to api.cloudmos.io are triggered by Cloudflare and return garbage 403 captcha page (and missing CORS headers) instead of the API responses.

Please consider removing Cloudflare or making it less of a hassle for users to work around the way it breaks the site. Otherwise, please advise some easy way of self hosting. I can't tell from the Readme if Cloudmos is a service I would be able to host or not. But frankly it might be too much of a hassle for me to set up my own nodes...

[Oyase-shinobi]

Hello @mashdragon
Happy weekend
I have checked the akash project and very interested in this
I would love to engage in your team and contribute in this project
may I take this issue?

[mashdragon]

@Oyase-shinobi I have no direct affiliation with akash project. Since this is a deployment configuration issue, I don't think you would be able to contribute.

[Oyase-shinobi]

@mashdragon
I see
Thanks

[baktun14]

There seems to be an issue with CORS and TOR. https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/18080

We suggest you use Chrome based browsers to use Akash Console.

[mashdragon]

This is not an issue with Tor Browser. The reason there is a CORS issue is that Cloudflare does not send a proper CORS response when it's giving you a response saying you are blocked, since the request never makes it to Akash's servers to begin with.

Generally most blockchain applications try to give access to Tor users because anonymity and decentralization is something they value, and if a Tor user can access it, that means everyone can. Bitcoin's node software had support for routing connections over Tor since Satoshi. Please give this another thought.

Alternatively can I run this locally?

[baktun14]

We can try other solutions sure