Cloudron post install questions
-
I've gone through the installation process successfully, however, when it attempts to show the page content on https://my.domain.com, it briefly displays the screen but then forwards to a standard 404 error.
I had temporarily forwarded ports 80 and 443 to the host private IP, received the same response.
Pinged my.domain.com and verified that it is indeed forwarding to my public IP address via Cloudflare.
Can the default ports be assigned to non-standard ports?
Any help with diagnosing and correcting the 404 issue would be great, thanks in advance.
-
if you briefly see the page, it might mean that some script redirects you. Can you just curl your dashboard domain and see what is actually delivered?
To be on the same page, you were successfully going through the Cloudron DNS and setup screens after installation by visiting your IP ?
-
@nebulon said in Cloudron.io post install questions:
if you briefly see the page, it might mean that some script redirects you. Can you just curl your dashboard domain and see what is actually delivered?
When I issue: curl https://my.domain.com/setup.html I receive the following response:
curl: (7) Failed to connect to my.domain.com port 443 after 12 ms: Bad accessFor now, port 443 is forwarding to the correct private IP address where the server is hosted.
To be on the same page, you were successfully going through the Cloudron DNS and setup screens after installation by visiting your IP ?
Yes, I had completed adding the Global API key that I retrieved from Cloudflare and entered my email address associated with that account.
It went through its process and went to the second page telling me that it was retrieving the certificate for 443 access.
Shortly after, a brief glimpse at the next setup screen (before I can access your app store) and then forwards/resolves to a 404.
-
@nebulon I tried that actually and was able to get it connected. However, now I have an app that is stuck on 'installing' and won't let me stop the task, or remove the app (or go through the steps that requires placing the app in a recovery mode).
Is there a way to completely wipe my slate so that I can try to install an app again?
-
-
@ejarvis said in Cloudron post install questions:
Is there a way to completely wipe my slate so that I can try to install an app again?
You can just reboot the server. That should make it unstuck if this is related to the Ubuntu kernel issue. Can you please try that?
-
@BrutalBirdie I'm checking this now, thanks for the link.
-
@girish said in Cloudron post install questions:
@ejarvis said in Cloudron post install questions:
Is there a way to completely wipe my slate so that I can try to install an app again?
You can just reboot the server. That should make it unstuck if this is related to the Ubuntu kernel issue. Can you please try that?
I've tried that. First rule of troubleshooting, eh?
-
@BrutalBirdie Applied that via SSH, everything went smoothly. However, the app is still stuck in 'installing' mode and won't let me stop or remove it.
^^screenshot -
@ejarvis Ah, the "Queued" usually either means the platform is still starting or the backup is running. For the latter, you can check in the Backups view. For the former, can you see
/home/yellowtent/platformdata/logs/box.log? Does it show some error or goes on about platform lock not released? -
@girish said in Cloudron post install questions:
@ejarvis Ah, the "Queued" usually either means the platform is still starting or the backup is running. For the latter, you can check in the Backups view. For the former, can you see
/home/yellowtent/platformdata/logs/box.log? Does it show some error or goes on about platform lock not released?It does say that there is a conflict and that the task is locked.
Box POST /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/exec 409 Conflict App not installed or running 465.399 ms>
2022-12-01T01:06:16.237Z box:locker Lock unreleased platform_start
Box POST /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/restart 409 Conflict Locked by task 3 : pending_install />On the bright side, the log files are very verbose and relatively detailed, with nearly everything that we need to know. Is there something else that I can verify for you?
-
-
@girish You mean this?
Box POST /api/v1/tasks/3/stop 409 Conflict task is not active 816.625 ms - 61
Box GET /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/files/ 404 Not Found Unable to find container sftp 401.543>
Box GET /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/files/ 404 Not Found Unable to find container sftp 701.603>
Box GET /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/files/ 404 Not Found Unable to find container sftp 628.086Top header says Cloudron 7.3.2
-
@girish Well, the result is interesting:
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to restart 'box.service'.
Authenticating as: Edwin Jarvis (jarvis)
Password:
==== AUTHENTICATION COMPLETE ===Ummm...
-
@ejarvis
Did you install Cloudron on your Ubuntu Desktop Computer?
It looks like you are running as userjarviswho does not have permission to execute that command.
So you should usesudo systemctl restart box.serviceBut please answer first on what systems you installed Cloudron.
Like very specific, tell us all. -
@ejarvis said in Cloudron post install questions:
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
~~
Authenticating as: Edwin Jarvis (jarvis)Looks like CentOS Desktop to me.
@ejarvis please post the output of
cat /etc/*-release
If you're not on Ubuntu 20.04 or 22.04 we won't help you any further and I would advice you to follow the Cloudron installation docs. -
@subven said in Cloudron post install questions:
@ejarvis said in Cloudron post install questions:
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
~~
Authenticating as: Edwin Jarvis (jarvis)Looks like CentOS Desktop to me.
@ejarvis please post the output of
cat /etc/*-release If you're not on Ubuntu 20.04 or 22.04 we won't help you any further and I would advice you to follow the Cloudron installation docs.Umm... no?
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focalI installed a minimal XFCE4 desktop environment so that I could VNC into the server as needed.
Do you think this is part of the issue?
