Cloudron Forum

overholt

I'd like to see this as well.

overholt

@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!

overholt

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.

overholt

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!

overholt

It's my old server that is having the problem. I tried deleting some of the larger and older backups, freeing up several GB of space. I retried the config but get this error:

I don't understand why my old server would be the one with the database issue. I only added a volume and configured backups to go there because I was running out of space. I moved those backups to my new server and the new one seems to work fine right now (I've been setting the DNS manually in my hosts file and enabling/disabling records in there to bounce back and forth between the old and new server - flushing the DNS on my Windows workstation as well and verifying the IP in the browser inspect>network tab).

overholt

@nebulon I'm not sure how best to reduce that disk space. I tried removing onlyoffice (which is stopped currently) but it said "Addons Error: Error tearing down postgresql. Status code: 500 message: connect ECONNREFUSED ::1:5432"

I'm looking at the backups through the command line and also the directory sizes:

I don't want to delete something and make the problem worse.

overholt

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?

overholt

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.

overholt

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.

overholt

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.

overholt

@overholt said in Disabling Redis on WordPress crashed site:

@joseph said in Disabling Redis on WordPress crashed site:

what are the app logs saying?

Nothing about this error:
Time Source Details
12:18 PM george App was re-configured
12:16 PM george App was re-configured
12:02 PM george App was re-configured
11:57 AM george App was re-configured
11:42 AM george App was started
11:42 AM george App was stopped
11:41 AM george App was re-configured
8:56 AM george App was started
8:56 AM george App was stopped
8:55 AM george App was restarted
8:55 AM george App was re-configured
8:55 AM george App was re-configured
8:53 AM george App was restarted
8:49 AM george App was started
8:49 AM george App was stopped

The last log has these details. Notice it says "".

{
  "appId": "a986644a-0659-4da5-9b9f-78a5ad223fff",
  "app": {
    "id": "a986644a-0659-4da5-9b9f-78a5ad223fff",
    "appStoreId": "org.wordpress.unmanaged.cloudronapp",
    "installationState": "installed",
    "runState": "running",
    "health": "healthy",
    "containerId": "35bc835409f47b62778e44c6bf7db9641899469aafd5bac3eac66cb3ca67eac2",
    "memoryLimit": 1073741824,
    "cpuQuota": 70,
    "label": null,
    "notes": null,
    "taskId": null,
    "sso": false,
    "enableBackup": true,
    "proxyAuth": false,
    "containerIp": "172.18.18.221",
    "crontab": null,
    "creationTime": "2024-09-21T16:28:46.000Z",
    "updateTime": null,
    "enableAutomaticUpdate": true,
    "upstreamUri": "",
    "enableMailbox": true,
    "mailboxDisplayName": "",
    "mailboxName": "wp.app",
    "mailboxDomain": "******.com",
    "enableInbox": false,
    "inboxName": null,
    "inboxDomain": null,
    "enableTurn": 1,
    "enableRedis": 0,
    "storageVolumeId": null,
    "storageVolumePrefix": null,
    "ts": "2024-10-04T16:16:12.000Z",
    "healthTime": "2024-10-04T16:18:00.000Z",
    "hasIcon": false,
    "hasAppStoreIcon": true,
    "manifest": {
      "id": "org.wordpress.unmanaged.cloudronapp",
      "title": "WordPress (Developer)",
      "author": "WordPress developers",
      "description": "WordPress (Developer) package gives you complete control over your WordPress installation.\nUnlike the WordPress (Managed) package, core WordPress files are editable. Because the core files\nare editable, you have to keep WordPress updated from the WP Admin dashboard. Some salient features are:\n\n* Supports all migration plugins. Use this package to migrate your existing site into Cloudron.\n* Make changes to WordPress via SFTP or the File Manager.\n* Supports all WordPress security plugins like WordFence.\n* Update WordPress from inside WordPress' admin dashboard.\n\n## About\n\nWordPress is web software you can use to create a beautiful website or blog.\nWe like to say that WordPress is both free and priceless at the same time.\n\nThe core software is built by hundreds of community volunteers, and when\nyou’re ready for more there are thousands of plugins and themes available\nto transform your site into almost anything you can imagine. Over 60 million\npeople have chosen WordPress to power the place on the web they call “home”\n— we’d love you to join the family.\n\n### Apps\n\n* [Android](https://play.google.com/store/apps/details?id=org.wordpress.android&hl=en)\n* [iOS](https://itunes.apple.com/us/app/wordpress/id335703880?mt=8&uo=6&at=&ct=)\n",
      "tagline": "Transform your site into almost anything",
      "version": "3.7.2-1",
      "upstreamVersion": "6.6.2",
      "healthCheckPath": "/wp-includes/version.php",
      "httpPort": 80,
      "manifestVersion": 2,
      "website": "https://wordpress.org/",
      "contactEmail": "support@cloudron.io",
      "configurePath": "/wp-login.php",
      "icon": "logo.png",
      "addons": {
        "mysql": {},
        "oidc": {
          "loginRedirectUri": "/wp-admin/admin-ajax.php?action=openid-connect-authorize"
        },
        "localstorage": {
          "ftp": {
            "uid": 33,
            "uname": "www-data"
          }
        },
        "sendmail": {
          "optional": true,
          "supportsDisplayName": true
        },
        "scheduler": {
          "wpcron": {
            "schedule": "*/1 * * * *",
            "command": "/app/pkg/cron.sh"
          }
        },
        "redis": {
          "optional": true
        }
      },
      "tags": [
        "hosting",
        "blog",
        "cms",
        "weblog",
        "ghost",
        "website",
        "wix",
        "squarespace"
      ],
      "optionalSso": true,
      "mediaLinks": [
        "https://screenshots.cloudron.io/org.wordpress.unmanaged.cloudronapp/1.png",
        "https://screenshots.cloudron.io/org.wordpress.unmanaged.cloudronapp/2.png",
        "https://screenshots.cloudron.io/org.wordpress.unmanaged.cloudronapp/3.jpg"
      ],
      "changelog": "* Fix session expiry when using OIDC login\n",
      "postInstallMessage": "This app is pre-setup with an admin account. The initial credentials are:\n\n**Username**: admin<br/>\n**Password**: changeme<br/>\n\nPlease change the password immediately.\n\n<sso>\nCloudron users get the `editor` role by default. You can give the user\n`admin` role inside WordPress' admin dashboard.\n</sso>\n",
      "multiDomain": true,
      "minBoxVersion": "7.4.3",
      "forumUrl": "https://forum.cloudron.io/category/77/wordpress-developer",
      "documentationUrl": "https://docs.cloudron.io/apps/wordpress-developer",
      "dockerImage": "cloudron/org.wordpress.unmanaged.cloudronapp:20240913-071948-949f0e125"
    },
    "tags": [],
    "checklist": {},
    "reverseProxyConfig": {},
    "portBindings": {},
    "accessRestriction": null,
    "operators": null,
    "debugMode": null,
    "servicesConfig": {},
    "secondaryDomains": [],
    "redirectDomains": [],
    "aliasDomains": [],
    "subdomain": "wp",
    "domain": "******.com",
    "certificate": null,
    "env": {},
    "mounts": [],
    "error": null,
    "iconUrl": "/api/v1/apps/a986644a-0659-4da5-9b9f-78a5ad223fff/icon",
    "fqdn": "wp.******.com"
  },
  "enableRedis": true,
  "taskId": "2508"
}

@joseph said in Disabling Redis on WordPress crashed site:

what does crashing mean here?

Crash means...
@overholt said in Disabling Redis on WordPress crashed site:

My site says "There has been a critical error on this website."

This means the website won't load on the front or back end. It just stopped working altogether.

I don't know what else to do from here besides ditch this install and try to start with a fresh one. Any ideas are greatly appreciated.

overholt

@joseph said in Disabling Redis on WordPress crashed site:

what are the app logs saying?

Nothing about this error:
Time Source Details
12:18 PM george App was re-configured
12:16 PM george App was re-configured
12:02 PM george App was re-configured
11:57 AM george App was re-configured
11:42 AM george App was started
11:42 AM george App was stopped
11:41 AM george App was re-configured
8:56 AM george App was started
8:56 AM george App was stopped
8:55 AM george App was restarted
8:55 AM george App was re-configured
8:55 AM george App was re-configured
8:53 AM george App was restarted
8:49 AM george App was started
8:49 AM george App was stopped

@joseph said in Disabling Redis on WordPress crashed site:

what does crashing mean here?

Crash means...
@overholt said in Disabling Redis on WordPress crashed site:

My site says "There has been a critical error on this website."

This means the website won't load on the front or back end. It just stopped working altogether.

I don't know what else to do from here besides ditch this install and try to start with a fresh one. Any ideas are greatly appreciated.

overholt

@joseph I tried both of those (see my original post).
Do I need to manually restart the redis service? If so, how?
I don't know if a the repair process will help.
I don't have a full Cloudron backup of the WP instance but I do have a backup of the WP site itself. I suppose I could create a nother WP instance and restore the backup to it. It would be nice to find out what happened though so I don't do it again.
Also, normally, if I disable a plugin it does not appear in the WordPress plugins directory, or it will have ...-disabled" or something after it. I have disabled plugins in my plugins folder that don't appear to be renamed. IS this expected behavior in Cloudron? Is there another mechanism by which plugins are disabled?

overholt

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?

overholt

@nebulon You are right. Our website hosting provider had to whitelist the n8n server's IP. Thanks for your help!

overholt

@nebulon I ran the curl command from the root user via SSH and from the terminal inside the N8N app and in both cases it said:

root@localhost:~# curl -v --no-tcp-nodelay https://www.****.com/wp-json/wp/v2/posts

Trying ...:443...
connect to ... port 443 failed: Connection timed out
Failed to connect to www.omrto.com port 443: Connection timed out
Closing connection 0
curl: (28) Failed to connect to www.omrto.com port 443: Connection timed out

overholt

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/

overholt

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

overholt

When I try to add an 11th user I get the following message:

"Free organizations may have up to 10 members. Upgrade to a paid plan to invite more members."

Evidently there was a patch done to fix this:
https://github.com/dani-garcia/vaultwarden/discussions/4707

But the version on Cloudron is not fixed, even though it is updated:

App Info

App Title and Version Vaultwarden 1.31.0
App ID 0173af22-9609-414a-8e30-18abde324530
Package Version com.github.bitwardenrs@1.17.0
Last Updated07/09/2024
No new updates available

What is weird to me is it says it is updated to 1.31.0, but the Package version appears to be 1.17.0. I'm not sure how to verify this. The app package in the App Store is listed as 1.31.0. I installed this package several months ago, so perhaps 1.17.0 isa the version I first installed.

Is there a way for me to force the changes in the config file in Cloudron? I looked in there but there is nothing like this:

"seats": 10, // The value doesn't matter, we don't check server-side 
 "maxCollections": 10, // The value doesn't matter, we don't check server-side

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

Cloudron Forum

overholt

Posts