Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync Error with iOS App "Fiery Feeds" #2043

Closed
benbeton opened this issue Oct 12, 2018 · 24 comments
Closed

Sync Error with iOS App "Fiery Feeds" #2043

benbeton opened this issue Oct 12, 2018 · 24 comments
Labels
API 🤝 API for other clients
Milestone

Comments

@benbeton
Copy link

Hi,

I'm using an awesome RSS Reader called "Fiery feeds" on iOS.
After setting up the API password and doing the first sync (this one works) I never get it to sync again.

According to the App dev, the logs from Fiery Feeds shows nothing wrong.

The only thing I can see Is the following in my error_log_apache:

[Fri Oct 12 21:21:54 2018] [error] [pid 7222] mod_proxy_fcgi.c(834): [client 134.3.0.0] AH01071: Got error 'PHP message: PHP Notice: session_start(): ps_files_cleanup_dir: opendir(/var/lib/php-sessions) failed: Permission denied (13) in /.../freshRSS/lib/Minz/Session.php on line 18\n'

any idea what this could be?
the install check says everything is fine (green)

FreshRSS Master
Fiery Feeds 2.1.1
PHP 7.1.23

@Alkarex Alkarex added this to the 1.12.0 milestone Oct 13, 2018
@Alkarex Alkarex added the API 🤝 API for other clients label Oct 13, 2018
@Alkarex
Copy link
Member

Alkarex commented Oct 13, 2018

Hello,
I do not think this is related to FreshRSS, but looks more like a PHP configuration issue.
See e.g. https://stackoverflow.com/questions/2904862/issues-with-php-5-3-and-sessions-folder

What OS do you use for your server?
Do you observe a similar problem when logging in and out of your Web interface?

A difference in the case of the API is that we do not use cookies.

FreshRSS/p/api/fever.php

Lines 28 to 30 in afa9020

ini_set('session.use_cookies', '0');
register_shutdown_function('session_destroy');
Minz_Session::init('FreshRSS');

session_name($name);
session_start();

@Alkarex Alkarex removed this from the 1.12.0 milestone Oct 13, 2018
@Twilek-de
Copy link
Contributor

I have seen this happen three times now (I am using almost the same setup. I am using debian testing on the server). I thought that it maybe happened after I reset my passwords (to the same passwords alas). The only thing I could do then is to delete the account in fiery feeds and readd them. Right now they are working again.

@Twilek-de
Copy link
Contributor

Nah not the password reset. Just stopped working again. Fiery feed hangs on "Uploading changes". I don´t see apache or FreshRSS errors, it just stops working.

@Alkarex
Copy link
Member

Alkarex commented Oct 21, 2018

I do not have any Apple device to test, unfortunately, so additional debug information is welcome.
If possible, try to favour clients using our Google Reader API, which is more efficient and exposes more features.

@Twilek-de
Copy link
Contributor

I have contacted the author of Fiery Feeds as the programm explicitly offers FreshRSS support. Maybe he´ll know what´s the problem. Which IOS News Readers do support the Google Reader API??

@Twilek-de
Copy link
Contributor

I have contacted the author of Fiery Feeds as the programm explicitly offers FreshRSS support. Maybe he´ll know what´s the problem. I also send the logs (which are a SQLITE Database) of FF. @Alkarex I could send them to you as well if you are interested, althought I would like to not post them here publicly. Apart from that which IOS News Readers do support the Google Reader API?? I could only find fever API implementations. Unread works. Reeder I could not get to login.

@Alkarex
Copy link
Member

Alkarex commented Oct 21, 2018

I am not aware of any client - let alone open source client - on iOS, which would support the Google Reader API from a custom server. However, many iOS clients do support the Google Reader API but without providing the option to change the server, since it is the type of API used for back-ends such as The Old Reader, Innoreader, Feedly, etc. (with some slight variations). So it would not be so difficult for them to allow the option of typing a custom server.

On my side, I would be interested in more logs. It would be possible to enable more precise logs, inspired from:

FreshRSS/p/api/greader.php

Lines 88 to 110 in 9897086

function debugInfo() {
if (function_exists('getallheaders')) {
$ALL_HEADERS = getallheaders();
} else { //nginx http://php.net/getallheaders#84262
$ALL_HEADERS = array();
foreach ($_SERVER as $name => $value) {
if (substr($name, 0, 5) === 'HTTP_') {
$ALL_HEADERS[str_replace(' ', '-', ucwords(strtolower(str_replace('_', ' ', substr($name, 5)))))] = $value;
}
}
}
global $ORIGINAL_INPUT;
return print_r(
array(
'date' => date('c'),
'headers' => $ALL_HEADERS,
'_SERVER' => $_SERVER,
'_GET' => $_GET,
'_POST' => $_POST,
'_COOKIE' => $_COOKIE,
'INPUT' => $ORIGINAL_INPUT
), true);
}

(I can prepare something, if you are willing to test a bit more)

I think that it is best to provide a link to a working test instance when contacting the developer of a client, so they do not have to install one themselves to test.

@Alkarex Alkarex added this to the 1.12.0 milestone Oct 21, 2018
@Twilek-de
Copy link
Contributor

Well I will wait what he has to say to the log. If I can test something just tell me what to do and where to send the log data.

Alkarex added a commit to Alkarex/FreshRSS that referenced this issue Oct 21, 2018
@Alkarex
Copy link
Member

Alkarex commented Oct 21, 2018

Please check #2063 , which should generate more logs.
Just paste your logs here (after replacing any confidential information) or send then to me privately.

@Twilek-de
Copy link
Contributor

I have added the debug code to fever.php. Where should the extra logging info show up? It is not in the log of the admin.

@Alkarex
Copy link
Member

Alkarex commented Oct 21, 2018

It is supposed to be in ./FreshRSS/data/users/_/log_api.txt

@Twilek-de
Copy link
Contributor

Found it and as the old AOL saying goes You got mail.

For those logs I deleted the FreshRSS Account in Fieryfeeds and readded it. This initial sync went well. Then I tried to manually resync and it got stuck. So whatever causes the problem should be in there.

@Twilek-de
Copy link
Contributor

The author of FF was able to reproduce the behaviour with his own device and is now looking into it.

@Alkarex
Copy link
Member

Alkarex commented Oct 23, 2018

It looks like Fiery Feeds enters an infinite loop with /FreshRSS/api/fever.php/?api&items&since_id=566575407

It could be related to the fact that this since_id looks like a 32-bit integer, while FreshRSS uses 64-bit.

@Twilek-de
Copy link
Contributor

I got the answer that that was exactly the problem and that it will be fixed in the next FF update. Thanks again for the excellent support @Alkarex and also to Lukas Burgstaller the author of FF.

@benbeton
Copy link
Author

benbeton commented Oct 23, 2018

thank you all for the help, I'll test the new version when its available on TestFlight!

Alkarex added a commit that referenced this issue Oct 24, 2018
* Add Fever API debug

#2043

* Default without debug logging
@Alkarex Alkarex modified the milestones: 1.12.0, 1.13.0 Oct 26, 2018
@Alkarex
Copy link
Member

Alkarex commented Dec 16, 2018

Closing, but feedback welcome, when there is any news

@Alkarex Alkarex closed this as completed Dec 16, 2018
@user858753257
Copy link

Hi ,

Short question : which settings have you used to get FF working ?

I used the URL with ....fever.php .

Which login credentials should I use ? The admin oder the api key ?

@Twilek-de
Copy link
Contributor

I used the same URL as to the web interface without any direct reference to a php file and then my username and password.

@Alkarex
Copy link
Member

Alkarex commented Dec 28, 2019

@F3000 It should be your API password. Depending on the apps (versions), you might have to provide the full API URL (ending with e.g. greader.php or fever.php depending on the chosen API)

@user858753257
Copy link

Thanks didn’t work for me :

@Alkarex shoud I open a new issue for that ?

I have tried following server URL‘s:

https://rss55.uber.space/fresh
https://rss55.uber.space/fresh/p/i/ (webui)

When I look into your Doku I should use this :
https://rss55.uber.space/fresh/api/fever.php

I have tried both with user: admin password : admin password

And :

User : admin password : api password

In FF I get with all combination this error :
D38FF759-81A6-40F1-AC01-EDD5D464E2D3

I hope you can help me

@user858753257
Copy link

When I click on the little text after the api Passwort field I see following :
What does the “Key symbol” button on the web ui do ?

Is this critical ?

A5050247-E441-465E-99BC-9BC154A277F0

@Alkarex
Copy link
Member

Alkarex commented Dec 28, 2019

@F3000 It would be good to fix those warnings. In ./freshrss/data/config.php, you should have a line like:

'base_url' => 'https://rss55.uber.space/fresh/p/',

Currently, your Fever API is https://rss55.uber.space/fresh/p/api/fever.php but if you can, it is better to avoid exposing your /freshrss/p/ in your URL, and instead use a sub-domain such as https://freshrss.example.net/ or a folder alias such as https://example.net/freshrss/ (instead of https://example.net/freshrss/p/ ). Check https://freshrss.github.io/FreshRSS/en/admins/10_ServerConfig.html and https://freshrss.github.io/FreshRSS/en/admins/03_Installation.html

@user858753257
Copy link

@Alkarex

many thanks for helping :)
https://rss55.uber.space/fresh/p/api/fever.php is working fine .

For the other things I open a separate ticket

javerous pushed a commit to javerous/FreshRSS that referenced this issue Jan 20, 2020
* Add Fever API debug

FreshRSS#2043

* Default without debug logging
mdemoss pushed a commit to mdemoss/FreshRSS that referenced this issue Mar 25, 2021
* Add Fever API debug

FreshRSS#2043

* Default without debug logging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API 🤝 API for other clients
Projects
None yet
Development

No branches or pull requests

4 participants