Cloudron Forum

I second this. Firecrawl would be a great addition to the App Library.

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!

I followed the instructions, now the child sites work but the main network site isn't,

Clarification:

This instance has WP Multisite enabled. I get the error mentioned above on the subcidiary sites but get a "Error establishing a database connection" on the main network site.

Here are links the the logs:

• Cloudron Sys Log
• WordPress Event Log
• WordPress Terminal Log

@SamGreenwood Also, is there a way to pull the main Cloudron log file and the app log files at once?

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

@IniBudi said in Issues with WordPress Corruption and Backup Management:

@SamGreenwood make sure that you use LAMP instead of WordPress Developer or Managed.

The instance I'm using is WP (Managed). I was hoping there's a way to fix it without having to create a new server. I don't want to lose my content.

@joseph said in Issues with WordPress Corruption and Backup Management:

If WP keeps getting corrupt, it is possible that the site is hacked. The backup situation and WP not loading is most likely not related.

I doubt it, I don't see any traffic that looks unusual. It seems like an issue with the WP package.

@IniBudi said in Issues with WordPress Corruption and Backup Management:

Try to switch your PHP version to 7.4,

How do I do that?

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!

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

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.

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

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

+1 also think this would be great

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.

@nebulon nope, the odd part is the dashboard reports all renewal attempts as green.

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 got it working. Turns out I had made a mistake.

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: