I have changed the error message now to this:
AppDev
Cloudron App Packagers
Posts
-
ERROR : "You are seeing this page because the DNS record of 74.48.163.80 is set to this server's IP but Cloudron has no app configured for this domain" -
ERROR : "You are seeing this page because the DNS record of 74.48.163.80 is set to this server's IP but Cloudron has no app configured for this domain"@poisonbrain I guess you navigated by IP in your browser ? Once you have installed and setup Cloudron, you cannot access by IP address and only by domain name.
The error message is... cryptic Generally, people set a wildcard DNS entry . Like
*.domain.com
points to the server's IP. Then, when someone navigates torandom.domain.com
, then they see this page and it will sayYou are seeing this page because the DNS record of random.domain.com is set to this server's IP but Cloudron has no app configured for this domain
.The above page is "reused" for when a user navigates by IP address and
random.domain.com
gets replaced with the IP address. Not ideal... -
Can't import project from previous installation@Lloyd66 thanks! I have added it to the docs.
-
Monitor incoming port 25@threetrees3 there's no reliable way from inside a server to check if incoming connections are working. Someone has to initiate a connection from outside the server.... An idea is to use some external monitoring service to connect to port 25 periodically (or another Cloudron instance with uptime kuma).
-
How to restore mail from encrypted backups?You first need to decrypt the backup: https://docs.cloudron.io/guides/decrypt-backups/
-
Umami not responding@guyds https://stackoverflow.com/questions/73362797/prisma-migration-error-the-database-schema-is-not-empty maybe ? IIRC, umami v1 was not using prisma and umami v2 moved to prisma. So I guess we have to tell prisma that migrations are already run?
-
Deploying moodle@taowang yes, since we have cloudron backups (which are app level), we disable the backups inside the app.
-
Backups to Storj suddenly fails: "Error listing objects in snapshot/app_0c3fb7c9-77c7-4d96-a90a-b75b5d1562bf. Message: ListObjects(V2): listing too many items for gateway-side filtering"If you are using rsync, maybe you can try tgz. Looks like S3 API has some incompatibility with too many files?
-
Umami not responding@guyds we are in sync about the situation
But to clarify, you should still be able to follow upstream instructions. It might be a bit different on Cloudron but you should atleast be able to try them out.
- You have to put the app in recovery mode. Repair -> Recovery
- Then, in a web terminal of the app, you can run whatever commands you want.
https://git.cloudron.io/cloudron/umami-app/-/blob/master/start.sh?ref_type=heads is the startup script of Cloudron. When in recovery mode, the app container is created but the start up script is not executed. So, you have to then execute the exports at https://git.cloudron.io/cloudron/umami-app/-/blob/master/start.sh?ref_type=heads#L11 manually in the web terminal. Hopefully, all this makes sense (if you have dealt with Docker before, it should be straightforward).
-
pdf-to-htm not working@sqlik fixed in latest package.