For some reason this warning comes and goes. Just checked and it's gone without any actions on my side. What exactly would I put in the php.ini?
Andreas
Posts
-
Nextcloud 30.0 -
Nextcloud 30.0Unfortunately the warning is back:
The PHP OPcache module is not properly configured. The OPcache interned strings buffer is nearly full. To assure that repeating strings can be effectively cached, it is recommended to apply "opcache.interned_strings_buffer" to your PHP configuration with a value higher than "12".. For more details see the documentation ↗.
-
Spacebar Chat (was Fosscord) on Cloudron - Open Source Discord alternativeThis is now called Spacebar https://github.com/spacebarchat
-
NextCloud Re-scanSimply open the web terminal and enter
occ files:scan
. Nothing else should be needed. -
Make SSO User admin@girish Just fyi, simply changing the entry in the DB works.
-
Make SSO User adminDoes anyone know how I can make a SSO user admin? Doesn't seem to be possible in the UI after the account creation.
-
Has anyone here switched from Google Workspace, MS365, or a similar service to Cloudron?@igaudette I've been using the built in mail server without any problems whatsoever for a few years now. I had to white/greylist my IP at the very beginning but no issues since.
-
Nextcloud 30.0@nebulon I added
'opcache.revalidate_freq' => 60,
, the warning is gone now, we will see if that solved it. -
Memos is now available@necrevistonnezr Yes that's a massive disappointment. Without any mobile support it's practically useless, as nice and practical this might be
-
Nextcloud 30.0Yes it's showing up in my current installation.
-
Nextcloud 30.0 -
Nextcloud 30.0The PHP OPcache module is not properly configured. The OPcache interned strings buffer is nearly full. To assure that repeating strings can be effectively cached, it is recommended to apply "opcache.interned_strings_buffer" to your PHP configuration with a value higher than "12".. For more details see the documentation ↗.
-
NTFY app overview always says "connecting..."@lukas said in NTFY app overview always says "connecting...":
Btw.: I switched in Element App to NextPush and this works fine.
With me it's actually the other way around. I've been using ntfy for Element Push but I'd like to install NextPush for Nextcloud talk notifications but can't get it to work. I'm sure it's some trivial thing that's missing but I can't find any proper documentation on setting it up. Would you mind sharing the steps you took?
I have installed the App on the NC-Level and on my mobile device. Logged in on my device, it shows up in the backend of the NC-Level App but won't display notifications.
-
FLOSS ecosystem vs. hubs like nextcloud. Which do you prefer?@necrevistonnezr said in FLOSS ecosystem vs. hubs like nextcloud. Which do you prefer?:
mail, calendar, talk-app, online office - that makes sense to have as an integrated experience
Yes that's what I do as well. Plus contacts. But already things like project management or document archive are better done with different software. I've been playing with paperless and it's looking really polished so far.
-
FLOSS ecosystem vs. hubs like nextcloud. Which do you prefer?Same, I prefer dedicated solutions by now. For example the NC Polls app is notoriously unstable. I much rather use rallley.
-
Unable to connect with self hosted instance, airdrop.net works fine@girish Great, thank you! is there a way to export the turn credentials? I would like to use those as backup. I tried entering
${TURN_PASSWORD} & ${TURN_USER}
in the terminal but those don't give me any values. Probably because they weren't generated on reboot.For anyone else who might be interested in this: I'm trying to use a turn server which has only set up auth-secret. So far this is my unsuccessful setup:
{ "sdpSemantics": "unified-plan", "iceServers": [ { "urls": "stun:turn.tld.com:5349" }, { "urls": "stuns:turn.tld.com:5349" }, { "urls": "stun:my.tld.com:3478" }, { "urls": "turn:turn.tld.comm:5349", "auth-secret": "c3de313cf548f0f09f380033e9dc1271f3969305c5dd78542f1c2fa62890305e" }, { "urls": "turns:turn.tld.comm:5349", "auth-secret": "c3de313cf548f0f09f380033e9dc1271f3969305c5dd78542f1c2fa62890305e" }, { "urls": [ "turns:my.tld.com:3478", "turn:my.tld.com:3478" ], "username": "", "credential": "" } ] }
-
Nextcloud 30.0Ha I was about to post this lol
-
Whitelabeling is not complete@potemkin_ai said in Whitelabeling is not complete:
btw, why would you expose platform version in the public accessible API?
True, this should at least require a token
-
Issues with Forwarding Emails from Cloudron to Google WorkspaceThe information you need is in this report. Basically this is referring to an E-Mail which did not meet the senders own policies. So The DMARC settings of the senders domain (mi-home.ee) are set to disallow the sending of these E-Mail. You should let them know of this E-Mail and see if they actually sent it themselves.
-
Unable to connect with self hosted instance, airdrop.net works fineAs title says. I have the feeling, this might have something to do with the turn server being used. I assume it's using the cloudron turn server? If so, please make this optional and let me use my own turn server.