I have changed the error message now to this:
girish
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).
-
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.
-
Stirling-PDF - Package Updates[2.10.1]
- Install poppler-utils for pdftohtml
-
pdf-to-htm not working@sqlik I can reproduce this, fix coming.
-
Umami not responding@guyds so, I had to go back and look since it's been a while since Umami 2 was released. The changelog for package v3.0.0 already says that all event data is lost - https://git.cloudron.io/cloudron/umami-app/-/blob/master/CHANGELOG?ref_type=heads#L134 . Note that this is what upstream does - https://umami.is/docs/migrate-v1-v2#important . Bullet point 3 "The script will NOT migrate any event data into v2."
So, you have only two options:
- Either roll back to v2.4.2 package (which is the last release of umami 1). But of course, you are stuck here forever.
- Just start afresh. You lose all data anyway. Only thing retained with the migration is the websites. Even the tracker code/script is different.
Maybe we should have made a completely separate app for Umami 2 because for all practical purposes it's a different app from Umami 1...
-
Umami not responding@guyds said in Umami not responding:
Isn't there any way I can try to manually run the migration script in recovery mode?
Sure, you should be able to run the migration script in recovery mode. But the issue was that the upstream migration script is not working/complete in all situations, from what I remember. But yes, give it a try .
As for backups, restoring should work. What was the issue there? Just clone the app from backup and check the logs?
-
Tracking Code@ekevu123 it's under Settings -> Domain -> Edit . Are you logged in as admin ?
-
Login to my.cloudron.io-
cloudron.io - this is Cloudron's website (the company)
-
console.cloudron.io - this is the place where Cloudron's customers login to manage billing. you cannot manage apps or anything of that sort here
-
yourdomain.com - this is the domain you gave when you installed Cloudron, the software, on your server. IMPORTANT: cloudron the company has no access to your servers. Cloudron the software is entirely selfhosted and only you have access to the server.
-
my.yourdomain.com - this is your server's dashboard. this is where you manage apps and other things
-
my.cloudron.io - this is actually Cloudron the company's, cloudron installation. you should not (and cannot) login here!
With this in mind:
When attempting to login us assigned IP it would redirect to my.cloudron.io.
this cannot ever happen.
how would I reach login when IP Changed/DNS is not available
If IP changes, go to your DNS and then just change the IP address of my.yourdomain.com manually to the new IP. Are you talking about dynamic IP here? If so, use the Dynamic DNS feature. It will automatically update the DNS with a changing IP.
Finally, if DNS itself is not available, I guess you have to use
/etc/hosts
. See also - https://docs.cloudron.io/troubleshooting/#unreachable-dashboard -
-
Umami not responding -
Ubuntu 24.04 LTS releasedWe will have support for Ubuntu 24 starting from Cloudron 8 (next release).
-
GitLab - Package updates[1.89.3]
- Update GitLab to 16.10.4
-
Uptime Kuma - Package Updates[1.21.12]
- Update Uptime Kuma to 1.23.13
- Full changelog
- #4692 Fixed language setting issues: Localisation-matching algorithm missing some edgecase (Thanks @CommanderStorm)
- #4700 Fixed TLS issues: Getting TLS certificate through proxy & prometheus update (Thanks @chakflying)
-
TTRSS - Error 500 when loading pluginsMaybe worthwhile reporting upstream, but knowing upstream project I would live with it