@ImatBagjaGumilar said in WordPress App Not Responding After Failed Automated Update to 6.8:

What’s the recommended way to recover the app or roll back the update?

Always a good first try to restore the latest backup.
Update can be tested again.

@JOduMonT said in How to Extend ProxyTimeout in Cloudron ?:

Apr 22 08:41:47 => Healtheck error: Error: Timeout of 7000ms exceeded

This line, the healthcheck is something Cloudron does.
It is like a curl to $APP_FQDN/health to see if the app is up and running.

The error message and the issue you described should not really corolate.

---

potenionally something could be destroyed here

You could check the NGINX file of the app to see if you could increase some timeout.

/home/yellowtent/platformdata/nginx/applications/$APP_ID/$APP_FQDN.conf

Found a real fix. App will be updated.

There are now many post about mail and IPv6 included PTR.
The forum search is a powerful tool

You need to set the PTR Record for your IPv6 in your hoster.

@Dont-Worry // @perelin will try to reproduce this in the evening (CEST Timetzone) and see if I can find a fix.

What cache time do you suggest?
Imo 14 days or even 30 days is okay.

7 days recap after applying your rules.
I believe not one spam mail has hit my spam folder or inbox so far.
normally I'd get ~20x+ spam mails a day since my Inbox also redirects my old legacy mailboxes from web.de which have been leaked and abused over and over again.

I must say, this feels very good.

@necrevistonnezr uhhhmmm
Since I set up everything with ansible, I once found this out, put in my playbook and forgot about it.
That it does not exist in the deb doc is questionable.

OH WOW! This is one impressive hack I've not seen or thought of yet.
Impressive!
I don't think this is how the /app/data/env.sh was ever intended to extend the PATH variable.
But it works!

I believe, I do not have to tell you that these librarys do not get automatically updated. And thus might be a security risk. If you are able to pull off this stunt, you must know this

@djxx said in n8n - Puppeteer - shared libraries failure:

because my hack will get overwritten at each application update.

No, no it will not since you store everything in /app/data/ this is part of the backup.
Nothing in /app/data/ will be overwritten with an app update.

Hey @djxx
Please see: https://docs.cloudron.io/apps/n8n/#custom-node-modules
This might solve your issue already

For the forum seo and searchability tho

---

Custom node modules

To install custom node modules, edit /app/data/env.sh using the File manager:

# note: this is a space separated list
export EXTRA_NODE_MODULES="handlebars@4.7.7 jsonata@2.0.2 marked@4.3.0"

The modules have to be whitelisted for use:

# note: this is a comma separated list
export NODE_FUNCTION_ALLOW_EXTERNAL=handlebars,jsonata,marked

Restart the app and use the module in Function nodes. Restarting the app will install the modules specified in EXTRA_NODE_MODULES automatically. See upstream docs for more information.

@necrevistonnezr my config, with redacted details
/etc/nullmailer/remotes:

mail.DOMAIN.TLD --port=587 --auth-login --user=sendernullmailer@DOMAIN.TLD --pass=that-is-one-secure-password --starttls

/etc/nullmailer/adminaddr:
note: this is the mailbox where to send the mailto

nullmailer@safeserver.de

/etc/nullmailer/allmailfrom

sendernullmailer@DOMAIN.TLD

restart the nullmailer.service after changing the files:

systemctl restart nullmailer.service

---

From https://wiki.debian.org/nullmailer

Check the configuration by sending a test email.

echo "hello" | NULLMAILER_NAME="Testsytem check" mail -s "This is just a test with nullmailer" "target-email-address@your-domain.net"

@philkunz said in Verdaccio Tokens now short-lived:

"It worked perfectly before"

Yes I can second that. With that annoyance in the brain everyone tents to cut short and be like "WHY?! IT WORKED?!".

@philkunz said in Verdaccio Tokens now short-lived:

On the other side, if stuff is working, and then it is not -> I'm sometimes a little confused about how migrations work, if I add too much custom stuff...

What I can tell you from ~5 years of experience with Cloudron.
This only sometimes happens if mayor changes take place.
A normal app update normally never results in such pain.
But if certain changes need to take place, like now with required OIDC, things can get a bit difficult.
Not only because Cloudron changes stuff, but with OIDC come other changes that people do not have in mind.
Like the user / password problem that does no longer work with any OIDC app.
That is why I wrote such an exsessive guide for Nextcloud:
https://forum.cloudron.io/topic/10067/guide-external-nextcloud-with-openid-social-login-calendar-caldav-synchronization

But sometimes, these changes are required for security reasons or because the apps requrie it suddenly.

I can 100 % understand your frustration and anoyance, but remember, same goes on when managing all these apps

"Why does this app now require ODIC in a minor version change? And without that fruther security update are not possible? WTF?!"

But I think there is a learning point here.
Maybe this update https://forum.cloudron.io/post/105728 should have been anounced 1-2 weeks before with some TL;DR "keep in mind the following stuff might break".
And yet, afaik, the Cloudron Team does not have the posibilty to notify users that use app XYZ specifically about these changes.
It has to be done in the forum.

I see improvment potential here.

Hey @philkunz as of right now, there are 174 apps in the Cloudron catalog.
Even me a "partner", does not have every app installed, tested and fully in my head, not yet!

If you wish to get more responses from the community, you need to be more verbose in writing your topics.
I am not writing this wag my finger but to help you, getting better and faster help from everyone here

Since I do not know the Verdaccio app at all, it would be a tremendous help for me do get details, to then maybe reproduce the issue and find a solution.

Your critic about UX is completly understandable and very valid.

After some quick research I found this github issue, which seems very similar to what you are describing.
https://github.com/verdaccio/verdaccio/issues/168

and I found https://verdaccio.org/docs/next/best/#expiring-tokens which might solve your issue already?

I am using nullmailer for my systems, which is confiugred to use a Cloudron Server SMTP for sending.
This might be something that could be setup by default in the future when Clouron is first setup.
Since every domain in Cloudron, by default, can send mails, even if they might land in spam at first.

@staff might interesting going further

@charlesnw said in Logging - targets, retention etc:

Is off-box/remote logging possible? I presume I can drop to the root shell and tweak the (r)syslog configuration to send things to a remote target. I would prefer a UI/API way todo this task (to ensure it doesn't break anything).

For 1. and 2.
Not from the UI, yet
Has to be done manually at the moment.

3. Hmmm might be something to look at.

4. I don't think so

5.
Not 100 % sure hmmm.
Same as 1. and 2. I guess.

@charlesnw this feedback is very valuable!
I could bet girish will take it to heart

@philkunz then the doc might solve your issue?

Are you talking about: https://docs.cloudron.io/apps/verdaccio/#cli-authentication ?

Tagging @nebulon since he is currently tinkering with the dashboard anyway, he might add this while he is at it.

Seems the storage bloat bug was "fixed" by cutting all attachments that are >= 15.