p44
Posts
-
"Backup failed" email notification -
"Backup failed" email notificationDear all,
is it possible to add to Cloudron email notification when "Backup failed"?
Backup is a mission-critical task, so it could be better to add also an email notification.
Thank's a lot
-
Backup uploading stalls@nichu42 This could be a reason... I think source causes should be outside of Cloudron.
Let us know
-
Backup uploading stalls@nichu42 thank's a lot. So this could explain issue? I mean, maybe Windcloud's servers sometime have problems to see Hetzner servers? Just to be sure, in "Box", did you enabled allow "External reachability" setting?
-
Backup uploading stalls@nichu42 thank's for your anwser. To be more accurate, you selected Germany for VPS (or server), and also for Box, right? So both are in the same data-center? Hetzner they have Nuremberg and Falkenstein/Vogtland. Both (Vps) and Box are in the same data-center Eg. both are in Nuremberg?
In my case, server is in Nuremberg and Box is in Helsinki, Finland (to keep backups in different infrastructures), and everything is fine. Data to backup is near to 100Gb, twice a day.
-
Backup uploading stallsdear all, I've almost same configuration and all works fine... @nichu42 where do you host data? Where is hosted your storage box? I mean, wich Hetzner data-center? (they have three in Europe)
-
module 'lxml.etree' has no attribute '_ElementStringResult' -
Importing Backup error: «The "path" argument must be of type string. Received undefined»@girish in fact I used Filesystem
Thank's a lot
-
Importing Backup error: «The "path" argument must be of type string. Received undefined»@girish thank's a lot
-
Problem moving FreshRSS instance (OIDC Authentication)@girish Thank's Girish
-
Problem moving FreshRSS instance (OIDC Authentication)@girish thank's, a the moment, I changed manually config.php:
'auth_type' => 'form',
This value seems to be not persistent, but is ok...
-
Problem moving FreshRSS instance (OIDC Authentication)Dear all,
I'm moving a FreshRss instance from domain1.com to domain2.com (both are on two different Cloudron instances)
Domain1.com has "admin" user configured, with traditional access (not OIDC).
I created domain2.com FreshRss cloudron app, then imported domain1.com backup.
Domain1.com has "admin" as unique and default user. Domain2.com comes with Cloudron main user.
Basically, now I've all feed stored under "admin" user, so I cannot login on Domain2.com with "admin" user.
I logged Domain2.com in with default Cloudron user, and configured classic login option (not OIDC), so I can login with "admin" user with all feed stored, but when restarting app, login option has been automatically restored to OIDC.
I'm not a bit confused... can you help me how to manage this problem?
-
Importing Backup error: «The "path" argument must be of type string. Received undefined» -
module 'lxml.etree' has no attribute '_ElementStringResult'@nebulon thank's...
-
module 'lxml.etree' has no attribute '_ElementStringResult' -
module 'lxml.etree' has no attribute '_ElementStringResult'@nebulon first I want to be sure that is not a Cloudron-related problem, than maybe I'll open upstream.
Maybe is this issue related to Python version?
-
module 'lxml.etree' has no attribute '_ElementStringResult'@girish it happens randomly...
Edit: problem it seems to be related tho scrapes that have configured "CSS/JSONPath/JQ/XPath Filters" instruction populated from "Visual Filter Selector".
So, to reproduce please try to do this:
- Add a website Url
- In Request Select "Playwright Chromium/Javascript via 'ws://0.0.0.0:3000'"
- In "Visual Filter Selector" select some area
- Save
At this point, you should have "CSS/JSONPath/JQ/XPath Filters" populated with filters, eg. xpath1:/html/body/div[2]
Let me know,
Thank's a lot
-
module 'lxml.etree' has no attribute '_ElementStringResult'After last update to 0.45.17, I've this problem:
"module 'lxml.etree' has no attribute '_ElementStringResult'"
Any other have this issue?
Thank's a lot
-
What's coming in 7.7@girish I confirm is working fine. Instance where I tested it was not updated to latest release. Thank's a lot
-
What's coming in 7.7@girish about this point: "oidc/ldap: fix display name parsing to send anything after first name as the last name" ... I think logic has to be analyzed again... because is not working as described. Eg. "Willem van Oranje", after this update, becomes "Willem Oranje"... ("Van" is lost)