Network error (expected ':status' header not present) #344
Comments
|
|
|
Same here. Edit: works with VPN. |
|
Getting the same error on various WiFi networks and LTE, haven't been able to log in recently. Is there any additional debug info that could help? Initially I was using Google login where I got this error on trying to reload. I also set up a Feedly account but that still gets the same error. |
|
Same here. Happening on wi-fi and 4G, since very early today.... |
|
You can bypass this by logging out and then logging back into Feedly again but this time click the 3 dots in the upper right corner and uncheck the "https" sign-in option. The good news is that everything will work again. The bad news is that your login is no longer secure. Sadly, it looks like the beginning of the end for this once great but now dead for years project. Time to start looking for something comparable. There sure aren't a lot of quality choices. |
That is the problem. If anyone find a real alternative, please share. I tried a lot of apps, but they are really slow in comparison. |
|
Hmm trying that, but now Google login won't work. |
|
+1 |
|
I had the same problem. What I did to resolve this is to export my rss feeds (opml) from Feedly and create an account on Feedly without Google. Import opml files, and then login from Greader with your new account. Alternatively, in your account settings in Feedly, you can link accounts and create a login. I noticed this feature after I had already done the above. If someone could try it and let us know. |
|
I linked my existing account to Facebook and then logged back into gReader that way. |
|
@jasonimani and @camisotro , which error were you getting? This bug is intended for the ":status header not present" error. The "Error: disallowed user agent" issue already has issues #338 and #343, it's confusing if they get mixed together here. I don't think that the workaround of linking a different account type helps for the ":status header not present" error. @jasonimani , FYI, creating a new Feedly account and linking it in Feedly fixed the "disallowed user agent" error, but I'm still stuck at the ":status header not present" error, I get this after attempting to login with the Feedly account. As a side note, I'm now using the Feedly Android app which works OK, though I preferred GReader. |
|
Sorry to clarify, I attempted the suggested workaround to the error for this issue, and then when trying to log in I ran into the user agent issue. I bypassed the latter by linking a different account type. I think the reason we're all seeing the user agent issue too is, many of us logged into gReader years ago and haven't attempted to reauthenticate since before that was an issue. |
|
@klausw Sorry you're correct. There are two issues and should be in separate threads. Initially, my problem was the topic of this forum (Network error (expected ':status' header not present). In an attempt to troubleshoot, I logged out...among many other ideas. Which led to the Google authentication issue. Sorry to hear that the solution I posted didn't fix the issue for you. I'm not sure if linking accounts will work or not, hence I asked someone to try it. I created a whole new account and imported my feeds, which is working for me. I'll checkout the Feedly app. Thanks! |
|
The same issue. |
|
gReader was abandoned years ago; it remains the best, but it's dead as projects go. The developer did the same with News+ in 2015. I'm enjoying NewsJet as an alternative RSS reader. Fast, free, beautiful dark theme, and a great internal browser. It's pretty simple and the Pocket integration could be better, but at least it still appears alive. |
|
Same story, same error... Never had any issues since moving all my RSS data from Google (since Google auth was broken) to a separate Feedly account. But this one is tough 🤔 |
|
@Ack0, can confirm. But not for all VPNs. US didn't work for me, but UK did. Thank you! |
|
Any one managed to fix it? I've logged out and not I can't not log in.. Using newsjet in the meantime but isn't the same :( |
|
@mariozhivago the same happened to me. You may try to reinstall and will be automatically logged in once you launch the app. This worked for me all the time. FYI, I was also already logged in into my Feedly app and a Feedly account in Chrome. Possibly, it takes login context from Chrome on the fly 🤔 |
|
@rootex- unfortunately didn't work.. |
|
But thank you |
|
It's an https error. Turn off the https and the error is gone. |
|
Please FIX this bug! |
|
It's strange that it broke so suddenly. Did Feedly start using HTTP2? Or was it an Android update? |
|
@wmill I don't think it's an Android update since the problem appeared last week. How do I turn off https? |
|
@mariozhivago you may try turning on VPN then, this thing really helps. |
|
Just thought I'd add my voice to this one. I have recent install on a new phone. Works fine over 4g, but broken over WiFi. Tried uninstalling, clearing cache etc. I'm logging in with a feedly account because of the other issue with google accounts. |
|
@LaughingJohn it does not work over my 4g, VPN needed for both cases |
|
Same here - problem just cropped up two days ago on Feedly Pro Android. WiFi or 4G either one. Reinstalling didn't help. Is it time to look for a new RSS app for my Feedly account? |
|
I worked around this by creating a feedly account, linking that to my google account within feedly, then logging into gReader using the feedly account with https disabled. See #278 for additional details. |
|
Update - I have a Feedly login - I just logged out and back in again with HTTPS disabled - works fine. |
|
@Origen17 did this solve the issue with receiving RSS feed updates? Or just the greader login issue itself? |
|
I'm not familiar with that issue - I don't have it myself. |
|
@Origen17 it is strange you don't have issues with feed updates |
|
I don't see that listed in this thread - what is going on? |
|
@Origen17 I am talking about the network error on trying to sync rss feed. Please look through the top post of this thread |
|
Right - that is what me and dswisher corrected as logged above. |
|
@Origen17 OK, once again. Did this solve the greader sync issue and you are now able to receive updates via wifi and mobile network without any errors? |
|
Yes it did - I was never talking about the login issue. |
|
@Origen17 -- how do you disable HTTPS from the Feedly or GReader apps? I don't see any such option in the Settings menu. Thank you. |
|
Logout. Then at the login dialogue, there is a menu at the top right. Uncheck it in that menu. |
|
|
|
If this project was alive I would never post this but even if I loved gReader and was my favorite app, it seems it's time to start using a different client. I tried most of them and I think most of you will like FeedMe and Palabre. Both are good and quite customizable. FeedMe is even open source. They are not as perfect as gReader was but it seems is time to move. |
|
I've tried a couple of dozens rss readers. None of them has such perfect widgets like gReader... |
|
I had this issue for the most of the day today, however, somehow it just worked from mobile but not from the tablet. While being annoyed at gReader I started to look for alternative and found FeedMe. Looks oddly similar to gReader and it's being actively developed (last release 24 Feb) it's free and has no ads. It's a good idea to donate something to support the guy! My plan is to move to that app permanently. |
|
Just got home from work and oddly it seems to be working now on WiFi. Maybe it's something feedly are doing.. |
|
I had the same problem and somehow after a few hours all is working again. Possibly the issue was not with greader. |
|
Yes it worked... Thank you guys. |
|
It's working here. Thanks, God. |
|
Please try latest version or beta https://github.com/noinnion/greader/tree/master/apk/beta, |
Lately I've been getting the above error almost every time I sync on WiFi whether at home or the office. For whatever reason sync works on mobile data but not WiFi. Any insights?
The text was updated successfully, but these errors were encountered: