FressRSS/docs/en/users/06_Mobile_access.md

This page assumes you have completed the server setup.

Enable the API in FreshRSS

1. Under the section “Authentication”, enable the option “Allow API access (required for mobile apps)”.
2. Under the section “Profile”, fill-in the field “API password (e.g., for mobile apps)”.
   • Every user must define an API password.
   • The reason for an API-specific password is that it may be used in less safe situations than the main password, and does not grant access to as many things.

See the page about the Google Reader compatible API for more details. See the page about the Fever compatible API for more details.

Testing

1. Under the section “Profile”, click on the link like https://rss.example.net/api/ next to the field “API password”.
2. Click on first link “Check full server configuration”:
   • If you get PASS then you are done, all is good: you may proceed to step 6.
   • If you get Bad Request! or Not Found, then your server probably does not accept slashes / that are escaped %2F. Proceed to step 5.
   • If you get any other error message, proceed to step 5.

Fix server configuration

• Click on the second link “Check partial server configuration (without %2F support)”:
  • If you get PASS, then the problem is indeed that your server does not accept slashes / that are escaped %2F.
    • With Apache, remember the directive AllowEncodedSlashes On
    • Or use a client that does not escape slashes (such as EasyRSS), in which case proceed to step 6.
  • If you get Service Unavailable!, then check from step 1 again.
  • With Apache:
    • If you get FAIL getallheaders!, the combination of your PHP version and your Web server does not provide access to getallheaders
      • Turn on Apache mod_setenvif (often enabled by default), or mod_rewrite with the following procedure:
        • Allow FileInfo in .htaccess: see the server setup again.
        • Enable mod_rewrite:
          • With Debian / Ubuntu: sudo a2enmod rewrite
  • With nginx:
    • If you get Bad Request!, check your server PATH_INFO configuration.
    • If you get File not found!, check your server fastcgi_split_path_info.
  • If you get FAIL 64-bit or GMP extension!, then your PHP version does not pass the requirement of being 64-bit and/or have PHP GMP extension.
    • The easiest is to add the GMP extension. On Debian / Ubuntu: sudo apt install php-gmp
  • Update and try again from step 3.