search

AnthonyZJiang / Microsoft-Reward-Chrome-Ext

A Chrome extension for Microsoft Rewards search, for accounts with two-factor authentication.
Apache License 2.0
319 stars 71 forks source link

RED colour error #112

Closed Skewter closed 1 year ago

Skewter commented 1 year ago

I am signed into my microsoft account. But still it shows error of red colour. This error is is not constant though. Extension would work some times, sometimes won't work. Extension works some time of the day but shows error other times. 

 Is the extension offline some time of the day? Like, it works some times then it won't work again randomly.

image image

esfomeado commented 1 year ago

Having the same issue.

LittleBigMan81 commented 1 year ago

Having the same issue, usually with Mobile searches, and has been happening for about 4 to 6 weeks now.

Theo2M commented 1 year ago

I fix the issue with the new option "Mobile user agent override". It seems to me that the user agent is changing, as this site indicates. I use this UA: Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) and it's working again. Sorry for my bad English

AnthonyZJiang commented 1 year ago

I am signed into my microsoft account. But still it shows error of red colour. This error is is not constant though. Extension would work some times, sometimes won't work. Extension works some time of the day but shows error other times.

 Is the extension offline some time of the day? Like, it works some times then it won't work again randomly.

image image

The issue with this is probably due to some network error on your end that the extension is not able to download UA from Github. It may be temporary.

AnthonyZJiang commented 1 year ago

I fix the issue with the new option "Mobile user agent override". It seems to me that the user agent is changing, as this site indicates. I use this UA: Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) and it's working again. Sorry for my bad English

I would advice against using a bingbot useragent. It may get you banned. I have updated the hosted UA so override should not be necessary.

Aryytt commented 1 year ago

@tmxkn1 I have used this method today. Will I get banned for using this now? I'm really worried.

I fix the issue with the new option "Mobile user agent override". It seems to me that the user agent is changing, as this site indicates. I use this UA: Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) and it's working again. Sorry for my bad English

I would advice against using a bingbot useragent. It may get you banned. I have updated the hosted UA so override should not be necessary.

AnthonyZJiang commented 1 year ago

@tmxkn1 I have used this method today. Will I get banned for using this now? I'm really worried.

I fix the issue with the new option "Mobile user agent override". It seems to me that the user agent is changing, as this site indicates. I use this UA: Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) and it's working again. Sorry for my bad English

I would advice against using a bingbot useragent. It may get you banned. I have updated the hosted UA so override should not be necessary.

Don't worry about it too much. I don't think using it once or twice will cause any issues, but don't use it day after day.

Aryytt commented 1 year ago

Alright, thank you!