Change "You found a Cloudron out in the wild!" page?

Nicolas

Is there a simple way to change/rebrand the "You found a Cloudron out in the wild!" page that displays from time to time when different things happen?
If not, perhaps this could be moved to the suggestions forum - as it feels like a good addition to the "Basic Branding" feature set.

girish

@nicolas said in Change "You found a Cloudron out in the wild!" page?:

displays from time to time when different things happen

Do you have a rough idea how I can reproduce this? The page should only be shown when a) if you visit by IP address post installation and b) if you point a random domain (i.e no app installed) to cloudron. It was not meant to be a branding thing, it was just a place holder page which nobody will generally see.

girish

Also, when an app is down, it will show the "app is not responding" page which is already brandable - https://docs.cloudron.io/branding/#custom-pages

jdaviescoates

@girish it's also shown when visiting a url that used to have an app installed but no longer does.

Nicolas

@jdaviescoates Yes - which also occurs if you add new domains/subdomains to an app while the app goes down to reassociate everything with itself. This meant that my live site was displaying this message briefly yesterday (the more domains/subdomains you have connected to the same app for legacy reasons the longer it takes that process to complete...)

nj

I once added an wildcard A Record for *.mydomain that pointed to my box. It would show the message You found a Cloudron out in the wild! message whenever I tried to open a non-existent subdomain, like foobarbaz.mydomain.

Non-existent app:

File /home/yellowtent/box/dashboard/dist/splash.html
Message: You found a Cloudron out in the wild!
To test, point foobarbaz.yourdomain to the box and visit the url.

Non-responding app:

File /home/yellowtent/boxdata/custom_pages/app_not_responding.html
Message: ...app is not responding...
To test, stop the app and visit the url.

I am not sure if those files will be replaced during upgrade, but I have the following content in both of those files.

<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
<!-- no such app / app not working -->
</body>
</html>

It would be cool to be able to add a custom file app_not_installed.html alongside app_not_responding.html.

p44

@nj Really interesting. Should be added to each new Cloudron instance.

It will be simpler - in future - to manage this directly from "Branding" section

What do you think @girish ?

girish

@nj said in Change "You found a Cloudron out in the wild!" page?:

I am not sure if those files will be replaced during upgrade, but I have the following content in both of those files.

The /home/yellowtent/boxdata/custom_pages/app_not_responding.html is safe and won't be replaced. But the splash page will get replaced.

I think there is a bug/unintended side effect of the change I made. I will look into fixing it. I guess splash.html is really notfound.html and this can be branded as one needs. I created https://git.cloudron.io/cloudron/box/-/issues/755

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Change "You found a Cloudron out in the wild!" page?