Cloudron Forum

@james thanks! Just DM'ed you with more information.

I just noticed that my Cloudron instance is experiencing similar symptoms: my Email status settings says that my IP is blocked by SpamHaus Zen, but when I put my IP into SpamHaus Zen's checker it comes up clean.

It's a bit unclear at the moment if there is a resolution to this or not?

@girish perfect, I'm back in - thank you!

Hey all! Been a minute...

I'm trying to login back into my Cloudron Gitlab account. I believe I used to use the 'login via Github', but it seems that option is no longer there. Am I missing something? Or is there a way I can 'recover' my Cloudron Gitlab account via a plain username/password combo?

Thanks!

@timconsidine thanks for documenting this! FWIW, on the latest version I had to update the command slightly to this to get it working: python3 /app/code/calibre-web/cps.py -s user:pwd -p ./app.db -g ./gdrive.db

Agreed with @iamthefij - previously I pretty much gave up on the iOS PWA since I wasn't able to log in at all. IMO, it's probably at least worthy of a mention in the docs for iOS users who want to use the PWA.

@iamthefij amazing! Good find, thanks for sharing. Would probably be good to have this bundled in for future updates.

Thanks @girish!

Hey Cloudron team!

I just migrated my Cloudron to a new server and had some issues around updating DNS entries to the new IP address. Specifically I use Namecheap, but either way, from the logs below we can see there is logic that can probably be optimized. I have about 40 apps or so installed on my box, so if a DNS provider has any rate limiting on their API, it can cause issues when doing a complete DNS migration/update. See log below for what I was seeing:

Jan 06 11:21:41box:dns registerLocation: Get error. retryable: true. Too many requests

In this case, I would expect Cloudron to gracefully register this error (assuming we're getting a legitimate 429 status code from the DNS API), and retry with exponential backoffs until all queries are completed. Instead, this failed on all 3 of my domains since the first one has a lot of apps, and therefore DNS entries, to complete successfully.

A few related thoughts:

1. I love Cloudron! The migration as a whole was pretty smooth even given this DNS hiccup. I just went into my Namecheap dashboard and updated them all manually not ideal, but not the end of the world. Besides that the upgrade process went without a hitch. Thanks for all that you do to help make it so!
2. I was hoping to register this bug in your Cloudron Gitlab instance but I don't think I have permissions for that, even when I was logged in? I hope this is the right place to report this issue.
3. The reason I moved servers is due to Cloudron 7.6.2 needing AVX support. I personally think that such a large dependency should have been introduced in a major version (ie 8.0.0) so that users like myself wouldn't be 'stranded' on a random version like 7.6.1 and not able to receive any updates at all (including on the apps, because of an issue reported in a separate thread on the forum here).

@girish good find! I just pushed up a fix that should fix file uploads. I'll comment again when I have some tests ready!

Appreciate the input!

I just pushed up some changes to make the app a bit more official: image, markdown files, etc. It should be ready for people to use if they'd like! I've been able to create a Collection, leverage Templates for additional fields, and use the API pretty seamlessly.

Again, the repo is here.

@girish @nebulon if we want to make this app official let me know and I can start working towards making some tests for it.

@girish that's exactly what I needed to be able to get Koillection up and running! Thanks so much. The problem at the end was also getting a write-friendly directory for user sessions for Symfony, by symlinking /run/php/session into /app/data. I pushed up the latest which is a working application to the repo here.

@girish is there interest in making this an official app? If so I can work on making tests for this (no guarantee of timeline though). The other question is how strict the precedence is for auto-creating users on app installation? Currently on install the user needs to go in and create the first user. If a user is a pre-req for an installable app then I'd need to find a way to bake an admin user in.

Good news! With some help from the developer I was able to make some strides with this, and am now stuck on a new error. The Koillection application is built on top of Symfony, a PHP framework, which introduces some complexity which don't get along well with Cloudron's read-only fs. I'm wondering if anyone knows of any other Symfony based applications that could help point me in the right direction? I also pushed up the latest code to the repo in the meantime if anyone wants to take a look!
cc @girish @nebulon
Thanks and happy Thanksgiving

I was able to get to the next error - progress! The app is now booting up properly. However, on first boot of the app it redirects users to a setup page endpoint, and I'm getting a 404 error on that page. Latest code is pushed up to my repo here, would appreciate if anyone is able to take a look!

@robi yep, that's probably what's going to need to happen!

@timconsidine this doesn't right to me unfortunately since I believe apps are run via the cloudrun user, I don't think each app gets its own user - feel free to correct me (anyone) if I'm mistaken. Appreciate the help looking into this error though @timconsidine !

@robi thanks for the response!
You're talking about the 'generate-keypair' command? Yikes, I definitely did muck that up somehow however, even after fixing it and even commenting out that line entirely I'm still seeing the same (1): Fatal Error Preloading failed to getpwnam("koillection") error

@girish @nebulon wondering if either of you have seen the error above previously and know of a way forward?

I have a decent start for Koillection but am getting an error when trying to start up:
Mon Sep 18 01:03:32 2023 (1): Fatal Error Preloading failed to getpwnam("koillection")

Is someone able to help me figure this out and help me get past this error? I pushed up my what I have so far here. Any help would be appreciated! I'm obviously happy to do the clean up work on the repo afterwards, just really want to get past this one error. Thanks!