@matthewdykstra issue is somewhere on the DNS side. Is that domain using Cloudflare? If so, for a start I would disable Cloudflare proxying for my.mjsiebolt.pro and just make that point to your server (so a single A record). Once that starts working, you can re-enable Cloudflare proxying and see.
@scooke thankfully not. he did trash some websites, maybe not realizing how easy it is to restore a backup, but he wasn't ambitious enough to try and jack my server
@robi said in Prevent app from opening in new tab?:
I wouldn't change the default
%
Opening an app in a new tab is key productivity for me.
Would be more than little p***ed off for it not be available.
It's also possible you are on a very old version of Cloudron (like Cloudron 6, where we initially introduced translations). You have to clear the browser cache in that case.
@S0ulf3re I think the issues you are facing to related to DNS, so the box logs probably won't help.
As a first step to get the dashboard reachable again, ismy.domain.com pointing to Cloudron server IP? You can check host my.domain.com on your PC to verify what the DNS is configured as.
@jdaviescoates said in Apps Were Crashing Now Cloudron Dashboard is Inaccessible:
I wonder if we could use one of the notification/ automation type apps (or something could be built into Cloudron itself), to get notifications about when disk space is running low?
Yes, agreed! It's in the backlog to notify via some external channel. Probably 8.0.
Just to add, what I ended up doing was just using Surfer and creating an index.html file with this:
<!DOCTYPE html>
<html>
<head>
<title>United Diversity - Together We Have Everything</title>
<meta http-equiv = "refresh" content = "0; url = https://my.uniteddiversity.coop/" />
</head>
<body>
<p>Will redirect shortly to https://my.uniteddiversity.coop/</p>
</body>
</html>
@girish So clever! Worked like a charm.
The only part where I had to fuss for a few minutes is that the app errored on changing to the new domain; it got stuck on de-registering the old domain. I went into the Domain manager and deleted the domain entirely from the Cloudron and then the app was able to receive the new domain without problem.
Thank you so much for writing the steps out in detail. I really appreciate it!
@scooke we have traced this down to a nodejs bug apparently with the domain in question.
The upstream issue is at https://github.com/nodejs/node/issues/39397
@d19dotca thanks for reporting. The 404s only come from map files for the minified 3rdparty libraries here. Those are only fetched if you open the webinspector to enabled nicer debugging, so those are non-fatal and can safely be ignored.
@nebulon Nice, your absolutely right.
Both are crashing over and over but by the looks of it for different reasons.
I will start a separate threads about those issues but you solved the last mystery here, first issue was terminal not loading after update due to browser cache, 2nd issue is the apps are actually crashing over and over and that is why the terminal keeps resetting.
Thanks for your help!
