f8f4b8a7386a75bace51c65ce86d3dad98287fa155bcae1378f5ea1b5ff5cb07.png
Error showing notice: File not found in filesystem.
Gaarrr, I don't like these messages: "Problem loading page, reloading in 5 seconds" Happens to often.
It looks like I'm getting somehow unauthorized (session problem? where are those saved? Not in default session path).
And another #bug: Just hit "send email notification" and the log file reads: "sharing","message":"Can't send mail to inform the user about an internal share: Address in mailbox given [@] does not comply with RFC 2822, 3.6.2."
$cookie_path = OC::$WEBROOT ? : '/'; WTF? In root (/) directory of the webserver?! No wonder why there is trouble with saving them ...
@roland Have you tried !Nextcloud? Same codebase at the moment, but likely to diverge in the next release. FWIW, I'm not having the problems you're describing, but I'm not using encrypted storage either (fully !selfhosted)
I guess when I set overwritewebroot in config, all is being tried to access there? Thumb of a rule: DO NEVER store session files in web-accessible path! You risk them being read by brute-force (just try all common names).
I never do #session-handling on my own (code), I let #PHP5 do the job for me and all went fine ... :-(
@bobjonkman yes, maybe I change over there, if they get rid of these grave mistakes. :-)
ah, okay. :-) session.cookie_path is the web path, not server's relative (document) path. Okay. Well, then why is no session saved? Hmm.
Found it out. #PHP5-FPM has a default php.ini which stores sessions by default to /var/lib/php5/sessions/ :-( I have setup it now in each "pool" separately not to mix session files from different projects.
Hmn, so it takes very long to let sharing encrypted files because they have to be re-encrypted or signed for the group/user ... Maybe that can with next releases being queued as a job so the web UI loads faster and shows a proper message, e.g. "Sharing you files may take some time depending on file amount being shared to complete."
@roland unfortunately it is not that easy because we can only re-encrypt it as long as we have the users private key to decrypt it first.
@bes So when I want to migrate, I need "./occ encrypt:decrypt-all ? Well, that won't work here, because many security-related PHP functions like system() are disabled (I disabled them).
@roland did you tried it. This command line tool just calls existing Nextcloud methods in the right order. If Nextcloud runs on your server then you should also be able to run the occ tool.
@bes I currently only have owncloud installed with 3 users (all family). I may plan to remove owncloud's files and place nextcloud's files there and simply run occ upgrade. No config changes/reset or so. I have 9.1.0 installed.
@roland regarding the encryption stuff it shouldn't make a difference if you run Nextcloud or ownCloud, it is still exactly the same code in this area. With the update to Nextcloud I would probably wait for Nextcloud 10 which is more similar to ownCloud 9.1 than Nextcloud 9. So the migration should be easier. But in general I would migrate as soon as possible if you want to switch to Nextcloud. We can't guarantee to keep a smooth upgrade path across multiple versions because ownCloud and Nextcloud will diverse more and more.