Pingger
commented
4 years ago No, the given nextcloud instance is configured incorrectly.
IF you are the owner, you should make sure that (for apache2; if you are using nginx you would need look for the equivalent there)
- mod_rewrite is enabled
- nextcloud can write to .htaccess
- apache2 is configured to actually use the .htaccess
The .htacess should contain a section like this, if it does and it is not working, your server ignores the file or does not have mod_rewrite enabled:
<IfModule mod_rewrite.c>
Options -MultiViews
RewriteRule ^core/js/oc.js$ index.php [PT,E=PATH_INFO:$1]
RewriteRule ^core/preview.png$ index.php [PT,E=PATH_INFO:$1]
RewriteCond %{REQUEST_FILENAME} !\.(css|js|svg|gif|png|html|ttf|woff2?|ico|jpg|jpeg|map|webm|mp4)$
RewriteCond %{REQUEST_FILENAME} !core/img/favicon.ico$
RewriteCond %{REQUEST_FILENAME} !core/img/manifest.json$
RewriteCond %{REQUEST_FILENAME} !/remote.php
RewriteCond %{REQUEST_FILENAME} !/public.php
RewriteCond %{REQUEST_FILENAME} !/cron.php
RewriteCond %{REQUEST_FILENAME} !/core/ajax/update.php
RewriteCond %{REQUEST_FILENAME} !/status.php
RewriteCond %{REQUEST_FILENAME} !/ocs/v1.php
RewriteCond %{REQUEST_FILENAME} !/ocs/v2.php
RewriteCond %{REQUEST_FILENAME} !/robots.txt
RewriteCond %{REQUEST_FILENAME} !/updater/
RewriteCond %{REQUEST_FILENAME} !/ocs-provider/
RewriteCond %{REQUEST_FILENAME} !/ocm-provider/
RewriteCond %{REQUEST_URI} !^/\.well-known/(acme-challenge|pki-validation)/.*
RewriteRule . index.php [PT,E=PATH_INFO:$1]
RewriteBase /
<IfModule mod_env.c>
SetEnv front_controller_active true
<IfModule mod_dir.c>
DirectorySlash off
</IfModule>
</IfModule>
</IfModule>
hydrian
ajh0912
Steps to reproduce
Expected behavior
Opens Nextcloud News with the subscribe 'Web address' option prefilled with FEED-URL
Actual behavior
403 Forbidden Forbidden You don't have permission to access this resource.
Proposed fix
Looks like the URL format should be https://YOUR-FQDN/index.php/apps/news/?subscribe_to=FEED-URL
Nextcloud 18.0.1 News 14.1.3