Closed ltraveler closed 1 year ago
I experience this issue on multiple devices and multiple browsers. Tested 3 laptops (Win 10 and Win 11) and 2 phones (Android and Iphone)
I tried to get some more info through Network and Console Developer tab, but with no luck, cos app completely freeze.
Update (2:42 PM UTC): Currently Chrome on my 1st Laptop is working, while Edge still not.
I had no problem on validation, but after validation the problem appeared. The problem (hangs) occurs immediately after entering the private key and password.
There may be a problem with the server where app.idena.io is installed You need to decentralize (load-balance) app.idena.io
Install app.idena.io on several servers and redistribute the load, and possibly also switch to another server if a problem occurs.
Many people had problems with validation today.
Vercel blocking web app, maybe considering as ddos ?
app.idena.io spam to google analystics 10k per minute requests, that hangs the browser
app.idena.io spam to google analystics 10k per minute requests, that hangs the browser
On my 1st laptop, on Firefox, I had AdBlocker installed which block these requests, so web app there worked like a charm. On rest of my devices and browsers I hadn't any AdBlocker so it failed...
I can login using https://app.idena.io/wallets but can´t if using https://app.idena.io or https://app.idena.io/home
Some latest facts that we know for the current moment:
My question is, would it be possible to run everything related to the web app from IPFS? Alternatively, could the entire node application encapsulate the web application as well, allowing people in the shared node marketplace apart from API key to get the link to the encapsulated web application on the shared node operator side?
The only way app.idena.io/home is working for me is in incognito mode
I think the biggest problem, in the case of running the web application on the side of the shared node operators, would be how to verify the web app? I believe the shared node would need to have a mechanism to ensure that the web app has not been changed. For example, it could involve creating and signing a container by the developers, and idena-go would have to check that signature before trusting it and use it as official representation of the web-app.
Some people have reported that after authorization, the browser gets stuck after some time, and a message appears asking to stop the page. As a result, many people failed the validation because of this issue.