Cloudron Forum

Quoting the docs page:

LazyLibrarian is a program to follow authors and grab metadata for all your digital reading needs.

The current source repo is https://gitlab.com/LazyLibrarian/LazyLibrarian.git

Releases(Tags) are at https://gitlab.com/LazyLibrarian/LazyLibrarian/tags

Bug reports at https://gitlab.com/LazyLibrarian/LazyLibrarian/issues

And finally Reddit https://www.reddit.com/r/LazyLibrarian/

EDIT:

Licence: GNU GPL v3.0
Docker: Yes - https://sasquatters.com/lazylibrarian-docker/ http://sasquatters.com/lazylibrarian-configuration/

Docker packages
LinuxServer : https://hub.docker.com/r/linuxserver/lazylibrarian/
The docker package includes ghostscript for magazine cover generation and calibredb (via optional variable)
LinuxServer docker is multi-arch and works on X86_64, armhf and aarch64 (calibredb only available on X86_64)
The dockers can be upgraded using the lazylibrarian internal upgrade mechanism

I believe Cloudron should also include the official open-source Bitwarden release, in addition to its support for Vaultwarden.

@james said in Migrating Cloudron to New Host Acci:

You can follow the guide here: https://docs.cloudron.io/backups#steps, but for your old server.

If it was unclear, I couldn't restore from a backup in the first place. I think whatever problem I was having in the first place caused that. But now I can't access the dashboard for the original instance anyway.

Side note: Can a mod rename the thread for me? I realized I made a typo. Can "Acci" be changed to "Provider"?

I got it working. Turns out I had made a mistake.

I think it would make sense to use something like ClearFlask to better manage feature requests and app requests. It would also allow you to publish a development roadmap integrated with the feature requests. This would also allow this forum to be used more exclusively for support purposes.

+1 also think this would be great

@girish said in Apps Were Crashing Now Cloudron Dashboard is Inaccessible:

systemctl restart box

Ran that command and I now have access to the dashboard,

@jdaviescoates didn't realize how to until if already posted.

@girish It's up now, and all the errors have disappeared.

I've been using Cloudron for a few years now, specifically on shared domains where I also host other resources. Recently (past few weeks), I've encountered issues. These issues can manifest in two ways:

• Cloudron app certificates become invalid, although the main Cloudron dashboard seems to function normally.
• My other resources on the same domain become inaccessible or unable to renew their certificates.

Does anyone have any suggestions on how to troubleshoot these conflicts arising from using Cloudron apps on shared domains?

I apologize, I've been really busy. Ended up just being a combination of me setting conflicting DNS records and issues with Let's Encrypt ACME verification. I fixed both and everything is working properly now.

I've been dealing with some ongoing issues with my WordPress site and backups, and I could really use some advice.

It all started back in October when my site got corrupted and showed the error message: “There has been a critical error on this website.” After some time, I finally managed to restore it, but the same problem hit again last week. I had to go back to a very old backup because trying to restore from more recent ones just brought up the same error, even though they were from before the issues began.

This seems to be a WordPress-specific problem since my other applications are working fine. I don’t think the server is the issue, either.

On top of that, I’ve noticed that some apps aren’t backing up correctly, and old backups aren’t being deleted, which might be leading to storage problems.

I'm not sure if these two issues are connected, but I'd appreciate any tips on diagnosing and fixing them. Has anyone experienced something similar? Any suggestions would be great!

@joseph give me a bit I'll pull them.

Hi everyone,

I'm experiencing a persistent issue with several of my Cloudron apps (Gogs, WordPress, and Mastodon). They're all showing the same error:

Network Error: Network error downloading icon : getaddrinfo EAI_AGAIN api.cloudron.io

This seems to be a DNS resolution problem where my server can't reach api.cloudron.io. I've been troubleshooting this issue on and off for about a month now with no success.

Things I've already tried:

• Restarting the affected apps
• Recovering from backups
• Checking my server's DNS configuration

None of these approaches have resolved the problem. The error persists across restarts and even after restoring from backups, which suggests it might be something more fundamental with my server configuration or network setup.

Has anyone encountered a similar persistent issue? I'm looking for more advanced troubleshooting steps since the basic approaches haven't worked. Could this be related to:

• Network configuration at the host level?
• Firewall rules blocking outbound connections?
• DNS resolver issues on my server?
• Something specific to how Cloudron apps connect to api.cloudron.io?

Any insights or suggestions would be greatly appreciated. This has been frustrating to deal with for so long.

Thanks in advance for your help!

Re: Change Primary Domain an Dashboard via Terminal/CLI

Hello everyone,

I'm reaching out for some urgent help regarding an issue I'm having with my old Cloudron instance. I've been experiencing constant crashing and network errors for months (you can see some of my previous struggles here.

Because of these persistent problems, I decided to move to a different hosting provider. However, during the setup of my new Cloudron instance, I made a crucial mistake: I accidentally assigned it the same subdomain that my old instance was using.

Now, I can access my new Cloudron instance without any issues, but I've completely lost access to my old instance.

Here's what I've tried so far:

• I attempted to point a subdomain from a secondary domain (which was connected to the old instance) at the old instance's IP. Unfortunately, this didn't work for dashboard access as it wasn't configured as the Dashboard Domain.
• I also tried using my most recent backup, but that didn't help in regaining access either.

I also ran cloudron-support --troubleshoot on the old instance, and here's the output:

Vendor: Linode Product: Compute Instance
Linux: 5.4.0-216-generic
Ubuntu: focal 20.04
Execution environment: kvm
Processor: AMD EPYC 7542 32-Core Processor x 4
RAM: 8136064KB
Disk: /dev/sda         93G
[OK]    node version is correct
[OK]    IPv6 is enabled and public IPv6 address is working
[OK]    docker is running
[OK]    docker version is correct
[OK]    MySQL is running
[OK]    nginx is running
[OK]    dashboard cert is valid
[OK]    dashboard is reachable via loopback
[OK]    No pending database migrations
[FAIL]  Service 'mysql' is not reachable
[OK]    Service 'postgresql' is running and healthy
[OK]    Service 'mongodb' is running and healthy
[OK]    Service 'mail' is running and healthy
[OK]    Service 'graphite' is running and healthy
[OK]    Service 'sftp' is running and healthy
[OK]    box v9.0.15 is running
[OK]    netplan is good
[OK]    DNS is resolving via systemd-resolved
[OK]    Dashboard is reachable via domain name
[OK]    Domain samgreenwood.ca is valid and has not expired
[OK]    unbound is running

It looks like Service 'mysql' is not reachable, which might be part of the problem.

I'm really stuck and need to either regain access to my old instance to retrieve critical data or figure out the best way to proceed from here. Any advice or guidance would be incredibly helpful!

Thanks,
Sam

Never mind, I fixed it. Turned out that moving the Syncthing app to the volume instead of trying to connect the volume independently.

I've been trying to setup a WP Multisite network but the WP app keeps crashing whenever I have made the required changes in the wp-config file. I get the following error: