Are we having a problem with the Chrome browser?
"ERR_BLOCKED_BY_CLIENT"
If the login doesn't work, use Firefox.
You are viewing a single comment's thread from:
Sort: Trending
Not sure which app you are referring to. But not been having any issues with the apps I use as of now. On Brave.
On Peakd yes.
On Ecency too..
On hive.blog too.
On www.snapie.io too
What else might I be missing?
Are you on a desktop or on mobile? Inside Hive Keychain browser?
I have tested things on Desktop, Brave browser.
Humm you have the same exact Brave build as me. I am using Hive Keychain 3.15.1
Does it work fine doing a swap on Hive Keychain for example?
Yes, it works without any problems. See @ibc.
However, I cannot log in to either Peakd or Hive.blog.
Humm... sounds like a firewall thing that is preventing or applying some sort of policy. I sometimes have problems logging from work to things, because they enforce a minimum of two TLS algos, and some of the recent stuff only uses TLS 1.3.
If it worked before and stopped working, try to flush the browser cache or even attempt to connect via 3/3/5G network without connecting through your house/place wireless. If that works, then it's something along the lines I am saying.
100%, so I have ruled out the browser because I am using the same as yours (maybe just flush the cache to be sure). I have done it on mine and can't reproduce.
I would try connecting from a different internet provider to validate it's not the firewall thing I mentioned on the previous comment.
Thanks @forkyishere, but I still can't log in via Brave.
If you can do it, then everything is fine. It doesn't work for me, but I can work around it.
Ok, I have this problem now.... Brave and Firefox... but works on Edge...
Does work with HiveAuth though. Very strange... only from the Work laptop though... from Home I can't replicate this.
Do you still have this?
Ok, I think I have solved this for me.
Try this... and let me know if it works...
https://peakd.com/hive-124838/@forkyishere/re-peaksnaps-tcsc0g
Nah, I don't have any problems. It's either a node that he has selected that is blocking his broadcast, or something else.