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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
hareenH

hareen

@hareen
About
Posts
11
Topics
4
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Two subscriptions detached from Cloudron Instances
    hareenH hareen

    @joseph Thanks Joseph. Issue was resolved by following steps on email and subscriptions are now linked correctly.

    Support licence

  • Two subscriptions detached from Cloudron Instances
    hareenH hareen

    I have an issue with subscriptions attached to 2 Cloudrons. I was setting up a 2nd Cloudron yesterday on the same domain and as I utilised the same domain during setup, it detached the subscription from my main server and moved it to the new one. Afterwards, I tried to resolve it by purchasing another subscription, so each server has a subscription, and also changed the domain to be my.example.cloud on server 1 and my.eu.example.cloud on servers 2.

    Both servers Currently note the following and installs apps without issues.

    "A Cloudron.io account is used to access the App Store and manage your subscription.

    Account Email cloudron-email@example.com
    Cloudron ID <cloudron-id>
    Subscription Premium Yearly"

    The issue is that the Cloudron ID shown on both servers is the same and seems to be connected to the same subscription. Additionally, when visiting the https://console.cloudron.io/ Cloudrons page, it isn't showing the last seen time for the server and current version. Instead, it shows "Setup Instructions: Create a fresh Ubuntu Noble 24.04 x64 server and run these commands" on both subscriptions.

    I have emailed support@cloudron.io the above details including email address, cloudron-ids and subscription-ids.

    Support licence

  • Deploying Anubis (AI Crawler Filtering) on a Cloudron Server
    hareenH hareen

    Setup Overview
    In this setup, I will be using Nginx Proxy Manager, but these instructions will also apply to other reverse proxy setups. The goal is to proxy Cloudron traffic via Anubis without disrupting the existing Cloudron installation. To achieve this, I’ll be utilizing a second VPS to deploy Anubis and to proxy traffic. This arrangement allows to proxying of selected apps through Anubis instead of the entire server.

    Note: This setup will not work for apps on Cloudron that require additional ports to be forwarded, beyond just port 443.

    VPS Configuration

    VPS 1: This VPS runs Cloudron with the apps you want to proxy.

    VPS 2: This VPS runs Ubuntu Server and hosts three Docker containers:

    • Nginx Proxy Manager: This acts as the reverse proxy for traffic going to Anubis.

    • Anubis: This container forwards valid requests to the Cloudron server on VPS 1.

    • Redis: Anubis stores completed challenge data in memory by default, which is lost on restart. The Redis container provides persistent storage for this data, ensuring that Anubis retains challenge information between restarts.

    The following steps assume that Docker is installed and the user is familiar with deploying a Docker Compose file.

    VPS 2 Docker Compose

    See below for docker compose for above mentioned container stack. I've made comments below where modification's required. For additional information on Anubis Variables, visit this link.

    services:
      ngixn-proxy-manager:
        image: jc21/nginx-proxy-manager:latest
        container_name: npm
        restart: unless-stopped
        ports:
          - "127:.0.0.1:80:80"
          - "443:443"
          - "127:.0.0.1:81:81"
        volumes:
          - /home/appdata/npm/data:/data #Change this path for npm data as required
          - /home/appdata/npm/letsencrypt:/etc/letsencrypt #Change this path for npm certs as required
        networks:
          - anubis-cloudron
        
        
      anubis-cloudron-redis:
        image: redis:8-alpine
        container_name: anubis-cloudron-redis
        restart: always
        volumes:
          - redis_data:/data
        networks:
          - anubis-cloudron
    
    
      anubis-cloudron:
        image: ghcr.io/techarohq/anubis:latest
        container_name: anubis-cloudron
        ports:
          - "127.0.0.1:10000:10000" #This port can be utilised with a prometheus container for Anubis metrics
          - "127.0.0.1:8300:8300" #The network port that Anubis listens on. 
        pull_policy: always
        restart: always
        depends_on:
          - anubis-cloudron-redis
        environment:
          BIND: ":8300" #The network port that Anubis listens on. 
          DIFFICULTY: "4" #The difficulty of the challenge
          METRICS_BIND: ":10000" # Prometheus Metrics Port
          SERVE_ROBOTS_TXT: "true" #If set true, Anubis will serve a default robots.txt file that disallows all known AI scrapers.
          POLICY_FNAME: "/data/cfg/botPolicy.yaml" # Config file Internal location. This can be left as it is.
          TARGET: "https://<CLOUDRON-VPS-IP-ADDRESS>" #Change this to the IP address of Cloudron Server.
          TARGET_INSECURE_SKIP_VERIFY: "true" #Skip TLS certificate validation for targets that listen over https. This is required.
          REDIRECT_DOMAINS: "app1.example.cloud, app2.example.cloud" #These should match the current cloudron app sub domains. This can be expanded as required.
          COOKIE_DYNAMIC_DOMAIN: "true" #If set to true, automatically set cookie domain fields based on the hostname of the request. 
          COOKIE_EXPIRATION_TIME: "168h" #The amount of time the authorization cookie is valid for.
          COOKIE_SECURE: "true"
          ED25519_PRIVATE_KEY_HEX: "4e7d024d97030b8e80f89de052494b31ff799d0ee83c238c6f22d01979ba8b54" #This is a sample key. Generate a new key by running 'openssl rand -hex 32' and paste it here
          OG_PASSTHROUGH: "false" #If set to true, Anubis will enable Open Graph tag passthrough. 
        volumes:
          - "/home/appdata/anubis/cloudron.yaml:/data/cfg/botPolicy.yaml:ro" # Config file location. Change this to the location of file below in section below. This is to be manually created.
    
        networks:
          - anubis-cloudron
    
    
    volumes:
      redis_data:
      
    networks:
      anubis-cloudron:
        driver: bridge 
       
    

    Anubis - Config file

    Below's the configuration file which I'm utilising for Cloudron. This setup allows both Mastodon and Pixelfed to be behind Anubis. Modify the configuration file as required depending on your Cloudron services and change mapping of config file path on docker compose file based on where this file is saved.

      - import: (data)/bots/ai-robots-txt.yaml
      - import: (data)/bots/cloudflare-workers.yaml
      - import: (data)/bots/headless-browsers.yaml
      - import: (data)/bots/us-ai-scraper.yaml
      - import: (data)/crawlers/googlebot.yaml
      - import: (data)/crawlers/bingbot.yaml
      - import: (data)/crawlers/duckduckbot.yaml
      - import: (data)/crawlers/qwantbot.yaml
      - import: (data)/crawlers/internet-archive.yaml
      - import: (data)/crawlers/kagibot.yaml
      - import: (data)/crawlers/marginalia.yaml
      - import: (data)/crawlers/mojeekbot.yaml
      - import: (data)/clients/git.yaml
      - import: (data)/common/keep-internet-working.yaml
    
    
      - name: allow-uptime-kuma
        user_agent_regex: Uptime-Kuma.*
        action: ALLOW
    
      - name: allow-api
        path_regex: ^/api/
        action: ALLOW
    
      - name: allow-assets
        action: ALLOW
        path_regex: \.(eot|ttf|woff|woff2|css|js|jpg|jpeg|png|mp4|webp|svg)$
    
      - name: allow-website-logos
        action: ALLOW
        path_regex: ^/hareen/website-logos/.*$
    
      - name: allow-well-known
        path_regex: ^/.well-known/.*$
        action: ALLOW
    
      - name: allow-mastodon-actors-objects
        path_regex: ^/users/[^/]+(/.*)?$
        action: ALLOW
    
      - name: allow-shared-inbox
        path_regex: ^/inbox$
        action: ALLOW
    
      - name: allow-pixelfed-actors-objects
        path_regex: ^/@[^/]+(/.*)?$
        action: ALLOW
    
      - name: allow-user-inbox
        path_regex: ^/@[^/]+/inbox$
        action: ALLOW
    
      - name: allow-nodeinfo-webfinger
        path_regex: ^/\\.well-known/(host-meta|webfinger|nodeinfo.*)$
        action: ALLOW
    
      - name: generic-browser
        user_agent_regex: >-
          Mozilla|Opera
        action: CHALLENGE
    
    dnsbl: false
    
    thresholds:
      - name: minimal-suspicion
        expression: weight <= 0
        action: ALLOW
    
      - name: mild-suspicion
        expression:
          all:
            - weight > 0
            - weight < 10
        action: CHALLENGE
        challenge:
          algorithm: metarefresh
          difficulty: 1
          report_as: 1
    
      - name: moderate-suspicion
        expression:
          all:
            - weight >= 10
            - weight < 20
        action: CHALLENGE
        challenge:
          algorithm: fast
          difficulty: 2
          report_as: 2
    
      - name: extreme-suspicion
        expression: weight >= 20
        action: CHALLENGE
        challenge:
          algorithm: fast
          difficulty: 4
    
    store:
      backend: valkey
      parameters:
        url: "redis://anubis-cloudron-redis:6379/0"
    
    

    Note: Redis is mapped in the configuration file and therefore creation of a config file is required prior to deploying the docker compose file above (Refer to 'store:' in above config).

    Once the above setup is deployed, visit the Nginx Proxy Manager interface on Port 81, setup an account by following the on screen instructions.

    DNS Provider Configuration

    Visit the DNS provider, and change the ipv4 and ipv6 addresses of app1.example.cloud and app2.example.cloud, which points at VPS1 (Cloudron server) which were setup previously with Cloudron, to point at VPS2 (Anubis server) ipv4/ipv6 address instead.

    Note: This change will disrupt these services till the next few steps are followed.

    Nginx Proxy Mananger Configuration

    First setup a SSL cerificate for *.example.cloud by visiting the SSL Certificate Tab → Let's Encrypt Certificate. DNS challange option can be utilised here for automated validation without needing to open port 80. Instructions will be shown when the slider's enabled.
    Screenshot 2025-08-09 at 7.44.43 PM.png

    Add a Proxy Host for app1.example.cloud. Set the scheme as http and point at the Anubis container (anubis-cloudron:8300 if above docker compose file was followed).
    Screenshot 2025-08-09 at 6.03.56 PM.png

    Next click SSL and select the certificate created in the previous step. Then enable Force SSL and HTTP/2 Support. Both HSTS options can also be enabled here based on the application being proxied.
    Screenshot 2025-08-09 at 6.09.29 PM.png

    Allow inbound traffic on port 443 on VPS 2, and ensure that UFW or any other firewall in use also allows traffic on this port. Once this is configured, app1.example.cloud (hosted on Cloudron) will be accessible with Anubis protection in place.

    To add additional Cloudron subdomains, repeat the same steps. Don't forget to update the Docker Compose file to include the new subdomains in the REDIRECT_DOMAINS environment variable within the Anubis container configuration.

    Optional Steps
    A Prometheus docker container can be deployed which can be used with Anubis Metrics Port (10000 in above docker compose) to monitor the Anubis instance with Grafana to output data similar to this.
    Screenshot 2025-08-09 at 6.31.40 PM.png

    Discuss

  • Deploying Anubis (AI Crawler Filtering) on a Cloudron Server
    hareenH hareen

    @james I'd be happy to. I'll put together a guide and share it here over the weekend.

    Discuss

  • Deploying Anubis (AI Crawler Filtering) on a Cloudron Server
    hareenH hareen

    Just an update on this. I managed to get everything working.

    I set up an Anubis instance on the second VPS, with the TARGET configured as https://<cloudron-ip>:443. For the REDIRECT_DOMAINS, I specified the services I wanted to proxy through Anubis, like so:
    REDIRECT_DOMAINS=app1.example.cloud,app2.example.cloud

    After that, I added those domains to Nginx Proxy Manager and pointed it at Anubis container port, and everything is now working as expected.

    Discuss

  • Deploying Anubis (AI Crawler Filtering) on a Cloudron Server
    hareenH hareen

    I'm wondering whether it's possible to deploy something like Anubis (Github, Webpage) to challenge web scraper bots when visiting certain subdomains on a Cloudron instance.

    I currently have another VPS which I have deployed Anubis with Nginx proxy Mangager and it works pretty well at stopping crawlers as per metrics output of Anubis.

    If it can't or shouldn't be deployed on Cloudron itself, is it possible for the VPS with Nginx Proxy Manager to handle traffic and then forward it to Cloudron? Not sure how Cloudron will behave with addition of an additional reverse proxy in front of it.

    Discuss

  • Server out of disk space
    hareenH hareen

    Thank you. That was my issue. I've followed the instructions on that thread and then truncated the syslog files which were around 50GB in size.

    Support logs disk space

  • Server out of disk space
    hareenH hareen

    I previously received " /dev/sda is at 100% capacity" and apps started crashing 5 days ago when i created a 100GB volume and moved 30GB of data (Nextcloud, pixelfed, etc) out of the server. Today that 30 GB has been consumed by "Everything else (Ubuntu, etc) 82.23 GB" which was previously around 50GB.

    I'm not sure how to diagnose the issue. I've checked previous threads on similar issues and backups aren't stored locally so /var/backups had about 100MB of files.

    Cloudron Ver: v8.3.1

    Support logs disk space

  • Cloudron v8.0.6 Stuck on Platform Status Starting services, this can take a while
    hareenH hareen

    @joseph , Running 'cloudron-support --recreate-containers' fixed the issue. Thank you.

    Support docker update

  • Cloudron v8.0.6 Stuck on Platform Status Starting services, this can take a while
    hareenH hareen

    Hi Joseph, I had 9GB of space on the server when this happened. I run it on linode so I restored a snapshot from 2 days ago, upgrade the VPS which now has 35GB spare space and 2GB spare ram and then upgraded the server. After 2 retries the upgrade still fails which is quiet disappointing.

    [no timestamp]  cmd: 'docker run --restart=always -d --name=mysql --hostname mysql --net cloudron --net-alias mysql --log-driver syslog --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock --log-opt syslog-format=rfc5424 --log-opt tag=mysql --ip 172.18.30.1 -e CLOUDRON_MYSQL_TOKEN=3c0e900572f8e6a0bf8ab8cac5c745343970e5bb28148ea6e12a17ac1838b5fdb5cd182b8f8bf07bcd30fa27ac4bc5f309d9b5feaa103ccaf21ff6bc210c58401c585a92749fe2a3f6e88a9e5f86fe749a79bc1f6a87d3b8437cc3fa9dd2520c73bc0ab28cae8f83e5ef09308eb38f84084fd672e421185a0df73293ae328597 -e CLOUDRON_MYSQL_ROOT_HOST=172.18.0.1 -e CLOUDRON_MYSQL_ROOT_PASSWORD=49b4e809bd7b9acaf8698e3afd7def7c919388c26d121ea3d17adf968bfb46d2a4d0d88ecd15ea360defc16addf9d0048910b10e7eeeb9336dc5436fc876cc7c463d1aa37b5a534746325092572b7650a53680f3dd8b8eeae5a440391b5ec0c07414c85720a0977d82b1f364f12f43fc490a2b9383420ac7a6680ffa510951b7 -v /home/yellowtent/platformdata/mysql:/var/lib/mysql --label isCloudronManaged=true --cap-add SYS_NICE --read-only -v /tmp -v /run registry.docker.com/cloudron/mysql:3.4.3@sha256:8934c5ddcd69f24740d9a38f0de2937e47240238f3b8f5c482862eeccc5a21d2 '
    [no timestamp]  }
    Sep 26 10:29:48 box:platform startInfra: Failed to start services. retry=false (attempt 0): startMysql errored with code 125 message Command failed: docker run --restart=always -d --name=mysql --hostname mysql --net cloudron --net-alias mysql --log-driver syslog --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock --log-opt syslog-format=rfc5424 --log-opt tag=mysql --ip 172.18.30.1 -e CLOUDRON_MYSQL_TOKEN=3c0e900572f8e6a0bf8ab8cac5c745343970e5bb28148ea6e12a17ac1838b5fdb5cd182b8f8bf07bcd30fa27ac4bc5f309d9b5feaa103ccaf21ff6bc210c58401c585a92749fe2a3f6e88a9e5f86fe749a79bc1f6a87d3b8437cc3fa9dd2520c73bc0ab28cae8f83e5ef09308eb38f84084fd672e421185a0df73293ae328597 -e CLOUDRON_MYSQL_ROOT_HOST=172.18.0.1 -e CLOUDRON_MYSQL_ROOT_PASSWORD=49b4e809bd7b9acaf8698e3afd7def7c919388c26d121ea3d17adf968bfb46d2a4d0d88ecd15ea360defc16addf9d0048910b10e7eeeb9336dc5436fc876cc7c463d1aa37b5a534746325092572b7650a53680f3dd8b8eeae5a440391b5ec0c07414c85720a0977d82b1f364f12f43fc490a2b9383420ac7a6680ffa510951b7 -v /home/yellowtent/platformdata/mysql:/var/lib/mysql --label isCloudronManaged=true --cap-add SYS_NICE --read-only -v /tmp -v /run registry.docker.com/cloudron/mysql:3.4.3@sha256:8934c5ddcd69f24740d9a38f0de2937e47240238f3b8f5c482862eeccc5a21d2
    [no timestamp]  Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/yellowtent/platformdata/mysql" to rootfs at "/var/lib/mysql": mount /home/yellowtent/platformdata/mysql:/var/lib/mysql (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.
    [no timestamp] 
    Sep 26 10:29:48 box:platform BoxError: startMysql errored with code 125 message Command failed: docker run --restart=always -d --name=mysql --hostname mysql --net cloudron --net-alias mysql --log-driver syslog --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock --log-opt syslog-format=rfc5424 --log-opt tag=mysql --ip 172.18.30.1 -e CLOUDRON_MYSQL_TOKEN=3c0e900572f8e6a0bf8ab8cac5c745343970e5bb28148ea6e12a17ac1838b5fdb5cd182b8f8bf07bcd30fa27ac4bc5f309d9b5feaa103ccaf21ff6bc210c58401c585a92749fe2a3f6e88a9e5f86fe749a79bc1f6a87d3b8437cc3fa9dd2520c73bc0ab28cae8f83e5ef09308eb38f84084fd672e421185a0df73293ae328597 -e CLOUDRON_MYSQL_ROOT_HOST=172.18.0.1 -e CLOUDRON_MYSQL_ROOT_PASSWORD=49b4e809bd7b9acaf8698e3afd7def7c919388c26d121ea3d17adf968bfb46d2a4d0d88ecd15ea360defc16addf9d0048910b10e7eeeb9336dc5436fc876cc7c463d1aa37b5a534746325092572b7650a53680f3dd8b8eeae5a440391b5ec0c07414c85720a0977d82b1f364f12f43fc490a2b9383420ac7a6680ffa510951b7 -v /home/yellowtent/platformdata/mysql:/var/lib/mysql --label isCloudronManaged=true --cap-add SYS_NICE --read-only -v /tmp -v /run registry.docker.com/cloudron/mysql:3.4.3@sha256:8934c5ddcd69f24740d9a38f0de2937e47240238f3b8f5c482862eeccc5a21d2
    [no timestamp]  Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/yellowtent/platformdata/mysql" to rootfs at "/var/lib/mysql": mount /home/yellowtent/platformdata/mysql:/var/lib/mysql (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.
    [no timestamp] 
    [no timestamp]  at /home/yellowtent/box/src/shell.js:73:23
    [no timestamp]  at ChildProcess.exithandler (node:child_process:430:5)
    [no timestamp]  at ChildProcess.emit (node:events:518:28)
    [no timestamp]  at maybeClose (node:internal/child_process:1105:16)
    [no timestamp]  at ChildProcess._handle.onexit (node:internal/child_process:305:5)
    Sep 26 10:31:26 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
    [no timestamp]  Unknown error: 400 <html>
    Dec 31 23:43:52 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at getSystemGraphs (/home/yellowtent/box/src/routes/system.js:126:28)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  status: 500,
    [no timestamp]  internalError: BoxError: Unknown error: 400 <html>
    [no timestamp]  <head><title>400 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  <center><h1>400 Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at Object.getSystem (/home/yellowtent/box/src/graphs.js:106:46)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  reason: 'External Error',
    [no timestamp]  details: {}
    [no timestamp]  },
    [no timestamp]  details: {}
    [no timestamp]  }
    Sep 26 10:32:10 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
    [no timestamp]  Unknown error: 400 <html>
    Dec 31 23:43:52 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at getSystemGraphs (/home/yellowtent/box/src/routes/system.js:126:28)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  status: 500,
    [no timestamp]  internalError: BoxError: Unknown error: 400 <html>
    [no timestamp]  <head><title>400 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  <center><h1>400 Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at Object.getSystem (/home/yellowtent/box/src/graphs.js:106:46)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  reason: 'External Error',
    [no timestamp]  details: {}
    [no timestamp]  },
    [no timestamp]  details: {}
    [no timestamp]  }
    Sep 26 10:34:34 box:locker Lock unreleased infra_start
    Sep 26 10:35:09 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
    [no timestamp]  Unknown error: 400 <html>
    Dec 31 23:43:52 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at getSystemGraphs (/home/yellowtent/box/src/routes/system.js:126:28)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  status: 500,
    [no timestamp]  internalError: BoxError: Unknown error: 400 <html>
    [no timestamp]  <head><title>400 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  <center><h1>400 Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at Object.getSystem (/home/yellowtent/box/src/graphs.js:106:46)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  reason: 'External Error',
    [no timestamp]  details: {}
    [no timestamp]  },
    [no timestamp]  details: {}
    [no timestamp]  }
    Sep 26 10:39:34 box:locker Lock unreleased infra_start
    Sep 26 10:41:26 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
    [no timestamp]  Unknown error: 400 <html>
    Dec 31 23:43:52 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at getSystemGraphs (/home/yellowtent/box/src/routes/system.js:126:28)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  status: 500,
    [no timestamp]  internalError: BoxError: Unknown error: 400 <html>
    [no timestamp]  <head><title>400 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  <center><h1>400 Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at Object.getSystem (/home/yellowtent/box/src/graphs.js:106:46)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  reason: 'External Error',
    [no timestamp]  details: {}
    [no timestamp]  },
    [no timestamp]  details: {}
    [no timestamp]  }
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  status: 500,
    [no timestamp]  internalError: BoxError: Unknown error: 400 <html>
    [no timestamp]  <head><title>400 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  <center><h1>400 Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at Object.getSystem (/home/yellowtent/box/src/graphs.js:106:46)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  reason: 'External Error',
    [no timestamp]  details: {}
    [no timestamp]  },
    [no timestamp]  details: {}
    [no timestamp]  }
    Sep 26 10:32:10 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
    [no timestamp]  Unknown error: 400 <html>
    Dec 31 23:43:52 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at getSystemGraphs (/home/yellowtent/box/src/routes/system.js:126:28)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  status: 500,
    [no timestamp]  internalError: BoxError: Unknown error: 400 <html>
    [no timestamp]  <head><title>400 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  <center><h1>400 Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at Object.getSystem (/home/yellowtent/box/src/graphs.js:106:46)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  reason: 'External Error',
    [no timestamp]  details: {}
    [no timestamp]  },
    [no timestamp]  details: {}
    [no timestamp]  }
    Sep 26 10:34:34 box:locker Lock unreleased infra_start
    Sep 26 10:35:09 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
    [no timestamp]  Unknown error: 400 <html>
    Dec 31 23:43:52 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at getSystemGraphs (/home/yellowtent/box/src/routes/system.js:126:28)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  status: 500,
    [no timestamp]  internalError: BoxError: Unknown error: 400 <html>
    [no timestamp]  <head><title>400 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  <center><h1>400 Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at Object.getSystem (/home/yellowtent/box/src/graphs.js:106:46)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  reason: 'External Error',
    [no timestamp]  details: {}
    [no timestamp]  },
    [no timestamp]  details: {}
    [no timestamp]  }
    Sep 26 10:39:34 box:locker Lock unreleased infra_start
    Sep 26 10:41:26 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
    [no timestamp]  Unknown error: 400 <html>
    Dec 31 23:43:52 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at getSystemGraphs (/home/yellowtent/box/src/routes/system.js:126:28)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  status: 500,
    [no timestamp]  internalError: BoxError: Unknown error: 400 <html>
    [no timestamp]  <head><title>400 Bad Request</title></head>
    [no timestamp]  <body>
    [no timestamp]  <center><h1>400 Bad Request</h1></center>
    [no timestamp]  <hr><center>nginx</center>
    [no timestamp]  </body>
    [no timestamp]  </html>
    [no timestamp] 
    [no timestamp]  at Object.getSystem (/home/yellowtent/box/src/graphs.js:106:46)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    [no timestamp]  reason: 'External Error',
    [no timestamp]  details: {}
    [no timestamp]  },
    [no timestamp]  details: {}
    [no timestamp]  }
    
    
    
    Support docker update

  • Cloudron v8.0.6 Stuck on Platform Status Starting services, this can take a while
    hareenH hareen

    My Cloudron instance updated last night to 8.0.6 and it's been stuck on 'starting services'. I have tried rebooting and also restarting box service as mentioned on another post with no luck. The following is the output of the box log:

    docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/yellowtent/platformdata/mysql" to rootfs at "/var/lib/mysql": mount /home/yellowtent/platformdata/mysql:/var/lib/mysql (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.
    
        at /home/yellowtent/box/src/shell.js:73:23
        at ChildProcess.exithandler (node:child_process:430:5)
        at ChildProcess.emit (node:events:518:28)
        at maybeClose (node:internal/child_process:1105:16)
        at ChildProcess._handle.onexit (node:internal/child_process:305:5)
    2024-09-24T21:52:34.615Z box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
    HttpError: Unknown error: 400 <html>
    <head><title>400 Bad Request</title></head>
    <body>
    <center><h1>400 Bad Request</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    
        at getSystemGraphs (/home/yellowtent/box/src/routes/system.js:126:28)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
      status: 500,
      internalError: BoxError: Unknown error: 400 <html>
      <head><title>400 Bad Request</title></head>
      <body>
      <center><h1>400 Bad Request</h1></center>
      <hr><center>nginx</center>
      </body>
      </html>
      
          at Object.getSystem (/home/yellowtent/box/src/graphs.js:106:46)
          at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
        reason: 'External Error',
        details: {}
      },
      details: {}
    }
    
    Support docker update
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search