wallabag: Symbolic link not allowed or link target not accessible after upgrading to 2.2.0
Issue details
After upgrading to release 2.2.0 i cannot login any more
Environment
- wallabag version (or git revision) that exhibits the issue: 2.2.0
- How did you install wallabag? Via
git cloneor by downloading the package? package - Last wallabag version that did not exhibit the issue (if applicable): 2.1.6
- php version: PHP 7.0.11
- OS: CentOS 6
- type of hosting (shared or dedicated): shared
- which storage system you choose at install (SQLite, MySQL/MariaDB or PostgreSQL): MySQL
Steps to reproduce/test case
I am running wallabag on a shared hoster which does not allow creating custom vhost configuration files. This has been resolved by using the following htaccess instructions:
RewriteCond %{REQUEST_URI} !^/web/
RewriteRule !^web/ /web%{REQUEST_URI} [L,NC]
After upgrading to release 2.2.0 my error log shows following entry. Login is not possible at the moment.
[Sat Jan 28 16:38:43 2017] [error] [client 2003:71:8f5d:3600:8565:1ab:f1cd:410f] Symbolic link not allowed or link target not accessible: /var/www/virtual/user/wallabag.mydomain.tld/web/bundles/fosjsrouting, referer: https://wallabag.mydomain.tld/login
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 20 (7 by maintainers)
I just opened a new PR to fix this bug 🎉 !
@nicosomb Your shared hosting archives have broken symlinks in
web/bundleswhich break the application completely - this is a critical issue.