R
Odd, but got it working in the end
even after restarting the postgres service I could not get a success restore
hence Until I rebooted, i was not able to clone from an existing backup and get the clone of the app to show me the usual login screen after a success dump.
After rebooting, backup restore from a clone went just fine.
I'm starting to think the problem may have happened even before, and that I have been making empty backups
I'm not sure how I can confirm this tho, but no matter what I restore, all I get is an empty Baserow
If I clone from a previous backup, any backup, I end up in the same first admin creation screen 
Similar issue here, but my logs are a bit different , I have tried to restore from previous backup but havent managed to connect with my existing user of recovered any of my databases. Honestly a bit worried because one of these were a journalist project about to launch
trying a restore now with a postgres service restart
same situation
I'm trying to use the bounce feature of listmonk
But
What I see in the log is :
2025/01/14 error scanning bounce mailbox: unknown charset: unknown charset: charset "ns_4551-2": htmlindex: invalid encoding name
Second error :
2025/01/14 bounced subscriber ( / ) not found
the from inbox I used contains plenty of bounce to check and process, but I'm not sure I'm actually logged in the in box at all.
Any idea how I can debug this further ?
I managed to install by it by removing some un-used community nodes, not sure which one was causing this but by cleaning up I got it to install
Most people would be more interested to run their own PDS than a Relay I think, it's probably going to be bit by bit, i'm not expecting Bluesky to be born in a desired state of perfection because nothing on the internet is ever born that way but I do hope that over time more and more parts of Bluesky will able to be run by users if they choose so
What about this approach : https://github.com/itaru2622/bluesky-selfhost-env
I'm trying to install the n8n bluesky node
but I get strange errors in some N8N deployments, also referenced here
N8N install is 1.71.2 (upstream version) and v3.60.0 cloudron version
I'v managed to install it just fine on another cloudron, but one is still refusing me to install
Any idea what could be done here ?
Just to be clear, moving the box MAIL domain and MY (dashboard) worked seamlessly
and the PTR record on the VPS side is also already in place.
but attempting to associate an existing or a new web app to this naked domain is broken for some reason, and it makes no sense since both the A record MY and the MX record MAIL were created just fine.
Logs from when attempting to associate a container/app to the naked domain
ec 01 16:39:17 box:dns/porkbun get: in zone infinitespace.click of type CNAME
Dec 01 16:39:18 box:dns/porkbun get: in zone infinitespace.click of type A
Dec 01 16:39:19 box:dns upsertDNSRecord: location on domain infinitespace.click of type A with values ["147.78.130.44"]
Dec 01 16:39:19 box:dns/porkbun upsert: in zone infinitespace.click of type A with values ["147.78.130.44"]
Dec 01 16:39:22 box:dns Attempt 80 failed. Will retry: Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}
Dec 01 16:39:22 box:dns registerLocation: Upsert error. retryable: true. Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}
Dec 01 16:39:27 box:dns/porkbun get: in zone infinitespace.click of type CNAME
Dec 01 16:39:28 box:dns/porkbun get: in zone infinitespace.click of type A
Dec 01 16:39:29 box:dns upsertDNSRecord: location on domain infinitespace.click of type A with values ["147.78.130.44"]
Dec 01 16:39:29 box:dns/porkbun upsert: in zone infinitespace.click of type A with values ["147.78.130.44"]
Dec 01 16:39:31 box:dns registerLocation: Upsert error. retryable: true. Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}
Dec 01 16:39:31 box:dns Attempt 81 failed. Will retry: Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}
Dec 01 16:39:36 box:dns/porkbun get: in zone infinitespace.click of type CNAME
Dec 01 16:39:37 box:dns/porkbun get: in zone infinitespace.click of type A
Dec 01 16:39:39 box:dns upsertDNSRecord: location on domain infinitespace.click of type A with values ["147.78.130.44"]
Dec 01 16:39:39 box:dns/porkbun upsert: in zone infinitespace.click of type A with values ["147.78.130.44"]
Dec 01 16:39:42 box:dns registerLocation: Upsert error. retryable: true. Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}
Dec 01 16:39:42 box:dns Attempt 82 failed. Will retry: Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}
Dec 01 16:39:47 box:dns/porkbun get: in zone infinitespace.click of type CNAME
Dec 01 16:39:48 box:dns/porkbun get: in zone infinitespace.click of type A
Dec 01 16:39:49 box:dns upsertDNSRecord: location on domain infinitespace.click of type A with values ["147.78.130.44"]
Dec 01 16:39:49 box:dns/porkbun upsert: in zone infinitespace.click of type A with values ["147.78.130.44"]
Dec 01 16:39:51 box:dns registerLocation: Upsert error. retryable: true. Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}
Dec 01 16:39:51 box:dns Attempt 83 failed. Will retry: Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}
Dec 01 16:39:56 box:dns/porkbun get: in zone infinitespace.click of type CNAME
Dec 01 16:39:58 box:dns/porkbun get: in zone infinitespace.click of type A
Dec 01 16:40:00 box:dns upsertDNSRecord: location on domain infinitespace.click of type A with values ["147.78.130.44"]
Dec 01 16:40:00 box:dns/porkbun upsert: in zone infinitespace.click of type A with values ["147.78.130.44"]
Here an example of how it could be interesting to be able to add a custom value
use case, self-verification in Nostr : https://wedistribute.org/2024/05/nostr-nip-05/
Indeed I'm aware of this, my goal was more the access to app-store and smooth app upgrades and of course : Active Directory support to enable easy SSO in my context.
And because we have our self-signed certificate deployed across our entire Windows Desktop park, I was thinking that would have been enough to sign my "cloudron.intranet.domain" with our root certificate and then enable anyone in the IT dept to access a set of applications.
huh okay, but does this mean I'm the only one having deployed (more or less) cloudron in this context ?
@girish i'm able to get npm packages just fine by having my .npmrc configured to use my intranet proxy, I wonder if the systemd box service couldn't be used to also use npmrc ?
Hmm redsocks is difficult, I need more time to analyze which local IP I have to configure so that requets are temporarily routed to it
2024/04/02 14:44:39 [error] 88905#88905: *1350 upstream prematurely closed connection while reading response header from upstream, client: 10.200.3.157, server: my.c
loudron.***.****.***, request: "POST /api/v1/appstore/register_cloudron_with_setup_token HTTP/2.0", upstream: "http://127.0.0.1:3000/api/v1/appstore/register_cloudro
n_with_setup_token", host: "my.cloudron.***.****.***", referrer: "https://my.cloudron.***.****.***/"
2024/04/02 14:44:39 [error] 88905#88905: *1350 connect() failed (111: Unknown error) while connecting to upstream, client: 10.200.3.157, server: my.cloudron..***.****.***, request: "GET /api/v1/cloudron/status HTTP/2.0", upstream: "http://127.0.0.1:3000/api/v1/cloudron/status", host: "my.cloudron.***.****.***", referrer: "https:/
/my.cloudron.***.****.***/"
i'm wondering if there is a curl command I could do to register this token and then a file I could edit with the token
I'm going to investigate redsocks
in the meantime the only error remaining has to do with collectd, the service appears to be running fine
but the graphie containers freaks out as if graphite had never been initialized
ā
ā ā
ā WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x55988453aa90 pid: 19 (default app) ā
ā *** uWSGI is running in multiple interpreter mode *** ā
ā spawned uWSGI master process (pid: 19) ā
ā spawned uWSGI worker 1 (pid: 26, cores: 1) ā
ā spawned uWSGI worker 2 (pid: 27, cores: 1) ā
ā 2024-04-02 09:38:27,960 INFO success: uwsgi entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) ā
ā 2024-04-02 09:38:27,960 INFO success: carbon-cache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) ā
ā 2024-04-02 09:38:27,963 INFO spawned: 'whisper-cleanup' with pid 28 ā
ā Cleanup old whisper databases... ā
ā find: ā/var/lib/graphite/whisper/collectd/localhost/ā: No such file or directory ā
ā 2024-04-02 09:38:27,978 INFO exited: whisper-cleanup (exit status 1; not expected) ā
ā 2024-04-02 09:38:29,984 INFO spawned: 'whisper-cleanup' with pid 30 ā
ā Cleanup old whisper databases... ā
ā find: ā/var/lib/graphite/whisper/collectd/localhost/ā: No such file or directory ā
ā 2024-04-02 09:38:30,000 INFO exited: whisper-cleanup (exit status 1; not expected) ā
ā 2024-04-02 09:38:33,007 INFO spawned: 'whisper-cleanup' with pid 32 ā
ā Cleanup old whisper databases... ā
ā find: ā/var/lib/graphite/whisper/collectd/localhost/ā: No such file or directory ā
ā 2024-04-02 09:38:33,022 INFO exited: whisper-cleanup (exit status 1; not expected) ā
ā 2024-04-02 09:38:34,023 INFO gave up: whisper-cleanup entered FATAL state, too many start retries too quickly
Or I could add this below directly to the box.service file ?
Environment="http_proxy=http://myproxy:1234" "https_proxy=http://proxy:1234"