Cloudron Forum

@murgero said in Connection not private - whole Cloudron down:

"net::ERR_CERT_AUTHORITY_INVALID" this error means your client PC has a CA issue, not your cloudron. This is likely cause the cert didn't update after changing the default domain (I assume is what you are doing). Is it working now that it's sat for a minute, it may have renewed that cert.

You said it was a problem on my client computer and so that got me thinking. I completely forgot that I made some changes to my local hosts file for testing. I removed those and it is working again. Your suggestion pointed me in the right direction, so thanks for that!

@timconsidine Grist is miles above Noco and Baserow. I'd love to see it on Cloudron.

I'm able to access https://www.****.com/wp-json/wp/v2/dealers from a browser or Postman but not from an HTTP Request node using get. It just times out. I've tried with authentication and without. My WordPress credentials don't seem to work either. I generated an app password for my user, but it rejects it with:

Couldn’t connect with these settings
ETIMEDOUT

This is a public URI anyway, so it should need authentication, right?

The connection timed out, consider setting the 'Retry on Fail' option in the node settings
Error details

From HTTP Request
Error code

ETIMEDOUT

Full message

connect ETIMEDOUT 64.34.166.70:443
Request

{ "headers": { "accept": "application/json,text/html,application/xhtml+xml,application/xml,text/;q=0.9, image/;q=0.8, /;q=0.7" }, "method": "GET", "uri": "https://www.****.com/wp-json/wp/v2/posts", "gzip": true, "rejectUnauthorized": true, "followRedirect": true, "resolveWithFullResponse": true, "followAllRedirects": true, "timeout": 300000, "encoding": null, "json": false, "useStream": true }
Other info
Item Index

0

Node type

n8n-nodes-base.httpRequest

Node version

4.2 (Latest)

n8n version

1.55.3 (Self Hosted)

Time

9/9/2024, 9:49:22 PM

Stack trace

NodeApiError: The connection timed out, consider setting the 'Retry on Fail' option in the node settings at Object.execute (/app/code/node_modules/n8n-nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts:1892:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Workflow.runNode (/app/code/node_modules/n8n-workflow/src/Workflow.ts:1384:8) at /app/code/node_modules/n8n-core/src/WorkflowExecute.ts:1072:27 at /app/code/node_modules/n8n-core/src/WorkflowExecute.ts:1794:11

EDIT:
Could Cloudron possibly have these addresses blacklisted?
https://community.n8n.io/t/http-request-timeout-issue-with-an-api-but-works-fine-on-postman/12572/2
https://docs.n8n.io/manage-cloud/cloud-ip/

Can Cloudron be installed on Ubuntu 23.04?

Hmm, that was TOO easy. I wonder why I never think of that. For me it was actually just shift+refresh.

I installed Vaultwarden last week and it worked fine. I came back this week to do some work in it and it suddenly gave me this error:

You are seeing this page because the DNS record of vaultwarden.yourdomain.com is set to this server's IP but Cloudron has no app configured for this domain.

I have other apps installed that are working fine. I tried uninstalling and reinstalling Vaultwarden to no avail. What am I doing wrong?

I'm using Linode and it appears they only provide Cloudron on Ubuntu 20.04, and therefore they only provide NextCloud 27. I want to upgrade to NC 28 or 29 and Ubuntu 22.04 or 24.04. Is there a way to do this, or is this a Linode question?

EDIT: It looks like Akamai/Linode does support 22.04 now. My question then is do I upgrade Ubuntu, then log in to Cloudron and upgrade it?

I currently have a Linode that is running Cloudron v8.0.4 (Ubuntu 20.04.6 LTS). I want to either upgrade the server to 22.04 and then 24.04 or install a fresh Linode Cloudron server. If I choose the latter I will need to move all my Cloudron apps to the new server. Which is the best way to do this? Linode says upgrading Ubuntu can be problematic and they recommend starting with a fresh install, then moving everything. I'd appreciate any advice from someone who has dealt with this as well as links to documentation that can help. Thanks in advance.

My current Linode server using Cloudron is based on Ubuntu 20.04. They do not offer 24.04 yet, but Digital Ocean does. I created a droplet at DO with Cloudron/Ubuntu 24.04 and am having trouble getting it running, much less restore my backups.

My goal is to ultimately use the same domain (lets just call it example.com), but the recommended way of using the etc/hosts file on Windows to fake the DNS and doing a dry run is not working for me, for example:
123.123.12.12 my.example.com
But I can only access it directly from the IP in the browser.

I tried setting it up with an alternative domain instead. Let's call it exampledomain.com. I created an A record pointing my to the IP. The Cloudron setup just sits there waiting for the DNS propagation when a DNS check reveals it is propagated.

I noticed there is a restore option, so I click it. I downloaded the last backup config, which was saved to a volume named CloudronVolume on the Linode server. I uploaded the backup tar files to the new volume on the DO server. I try to restore the config and it tells me:
"Access denied. Create /mnt/CloudronVolume/snapshot and run "chown yellowtent:yellowtent /mnt/CloudronVolume" on the server"

My volume on DO does not have the same name. Does it need to? I gave the entire volume permission, so I'm not sure where to go from here. Any help would be greatly appreciated.

EDIT:
I did have to change the name of the directory for the volume because Cloudron is looking for that specific configuration.

After adding a volume to my old Linode Cloudron server, setting up backups to go there and restoring to the new DO server my old Linode Cloudron is now freaking out. I tried moving an app's data to the volume and it throws the error:
An error occurred during the data migration operation:
Addons Error: Error setting up postgresql. Status code: 500 message: connect ECONNREFUSED ::1:5432

I can't even start apps on it:
FileSystem Error: Could not create nginx config directory: ENOSPC: no space left on device, mkdir '/home/yellowtent/platformdata/nginx/applications/acc4c4d3-9bed-42a5-b440-946c4dd86b99'

I don't understand why something like the Postgresql setup or IPV6 changed on my old Cloudron server. What could have caused the sudden change and how do I fix it?

OK, instead of increasing the disk space or trying to hunt down files to delete, I decided to set up the new server on a temporary domain to test everything out (and might just migrate to that domain permanently).

One issue I ran into was Cloudron wouldn't recognize the DNS in the domain settings when changing the dashboard domain. Since I set up the server with IPv6 I had to enter both the IPv4 and 6 addresses into the DNS config for my domain (I'm doing it manually since Godaddy and NameCheap won't let you use their API unless you have a LOT of domains and/or pay a premium). I'll have to do that for every app individually.

I'll have to think ahead as far as disk space is concerned so I don't run into the Postgresql problem again.
Thanks for your help!

I recently moved my entire Cloudron and have been working on migrating my old domain to a new one. Here is a link to some issues I had with that:

https://forum.cloudron.io/topic/12750/moving-entire-cloudron-from-linode-to-digital-ocean?_=1733434654935

After working on some other priorities and coming back to this, I was no longer able to access the my.olddomain.com Cloudron console. Also, some of my apps are available and others are not. I cannot bypass the security error in the advanced option in my browser either. Here is the error I get:

Your connection is not private
Attackers might be trying to steal your information from my.olddomain.com (for example, passwords, messages, or credit cards). Learn more about this warning
net::ERR_CERT_AUTHORITY_INVALID

I'm paying for Cloudron and added my new domain to it while keeping the old one on the plan as well, however the old one now says it's the free plan and the new is paid. I need to access my old instance, but I don't know what I need to do to be able to access it. I tried logging in to my Linode and updating the certificate but it says it doesn't recognize the cloudron command. Any help would be greatly appreciated.

ChatGPT says to try reinstalling the cloudron CLI with this:
sudo npm install -g cloudron
But I don't know why it wouldn't be there to begin with. I don't want to mess anything up. The only thing I can think of is my license is not working because of the domain switch, but I should still be able to access the Cloudron control panel.

I disabled the Redis plugin in my WordPress dashboard and also in my Cloudron dashboard. My site says "There has been a critical error on this website." I tried restarting the app. I'm not sure how to reenable the Redis plugin in WP without access to the admin backend. The plugin still exists in the wp-content folder. Do I need to change something in a config file or something? How can I fix this?

I can't see the admin settings in the gear menu. I've tried the following:

1. Added my Cloudron user as and Operator for the app. That user cannot see the admin settings.

2. According to these instructions: https://docs.cloudron.io/apps/metabase/
   I ran the Reset Password commands and changed the password for the default admin user account admin@cloudron.local, then logged in with that. No admin settings are available.

I can't add databases and configure MetaBase because of this. What do I need to do?

I managed to log into the back end of WP and started enabling and disabling different plugins. I discovered there was a conflict with one of them related to Toolset and WooCommerce. It's working again now.