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
  • 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
  1. Cloudron Forum
  2. Support
  3. need help with installation error

need help with installation error

Scheduled Pinned Locked Moved Solved Support
installation
23 Posts 3 Posters 2.2k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M mikewen8888

    @girish i did run the sript twice on this bare metal

    the first, log stopped at

    noob@cloud:~$ sudo tail -f /var/log/cloudron-setup.log
    [sudo] password for noob:
    Running cloudron-setup with args : --
    Hit:1 http://id.archive.ubuntu.com/ubuntu focal InRelease
    Hit:2 http://id.archive.ubuntu.com/ubuntu focal-updates InRelease
    Hit:3 http://id.archive.ubuntu.com/ubuntu focal-backports InRelease
    Hit:4 http://id.archive.ubuntu.com/ubuntu focal-security InRelease
    Reading package lists...
    Reading package lists...
    Building dependency tree...
    Reading state information...
    python3 is already the newest version (3.8.2-0ubuntu2).
    curl is already the newest version (7.68.0-1ubuntu2.7).
    software-properties-common is already the newest version (0.99.9.8).
    ubuntu-standard is already the newest version (1.450.2).
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    

    and freeze at that point, i waited 30 or 40 minutes and the log just stuck there so i decided to run the script again, this time the log stopped at nginx

    Processing triggers for mime-support (3.64ubuntu1) ...
    Processing triggers for resolvconf (1.82) ...
    
    echo "==> installing nginx for xenial for TLSv3 support"
    ==> installing nginx for xenial for TLSv3 support
    curl -sL http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/nginx_1.18.0-2~${ubuntu_codename}_amd64.deb -o /tmp/nginx.deb
    
    

    Just now i tried as your suggestion:

    
    noob@cloud:~$ systemctl stop systemd-resolved
    ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
    Authentication is required to stop 'systemd-resolved.service'.
    Authenticating as: noob
    Password:
    ==== AUTHENTICATION COMPLETE ===
    noob@cloud:~$ sudo systemctl disable systemd-resolved
    [sudo] password for noob:
    Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service.
    Removed /etc/systemd/system/multi-user.target.wants/systemd-resolved.service.
    noob@cloud:~$ sudo systemctl restart unbound
    noob@cloud:~$ sudo lsof -i :53
    COMMAND  PID    USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
    unbound 7366 unbound    3u  IPv6  53429      0t0  UDP ip6-localhost:domain
    unbound 7366 unbound    4u  IPv6  53430      0t0  TCP ip6-localhost:domain (LISTEN)
    unbound 7366 unbound    5u  IPv4  53431      0t0  UDP localhost:domain
    unbound 7366 unbound    6u  IPv4  53432      0t0  TCP localhost:domain (LISTEN)
    noob@cloud:~$ curl -sL http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/nginx_1.18.0-2~${ubuntu_codename}_amd64.deb -o /tmp/nginx.deb
    noob@cloud:~$ ls
    cloudron-setup
    noob@cloud:~$
    
    
    

    i think it still not downloading that deb file

    M Offline
    M Offline
    mikewen8888
    wrote on last edited by
    #9

    sorry, wrong ls location

    noob@cloud:~$ ls /tmp/
    box-src-fHS7GD  systemd-private-7bed1c71abde445bb0e6b8f0c16c16af-systemd-logind.service-6LDx4e     systemd-private-7bed1c71abde445bb0e6b8f0c16c16af-upower.service-z0ugch
    snap.lxd        systemd-private-7bed1c71abde445bb0e6b8f0c16c16af-systemd-timesyncd.service-1T3g2e
    noob@cloud:~$
    
    
    1 Reply Last reply
    0
    • M mikewen8888

      @girish i did run the sript twice on this bare metal

      the first, log stopped at

      noob@cloud:~$ sudo tail -f /var/log/cloudron-setup.log
      [sudo] password for noob:
      Running cloudron-setup with args : --
      Hit:1 http://id.archive.ubuntu.com/ubuntu focal InRelease
      Hit:2 http://id.archive.ubuntu.com/ubuntu focal-updates InRelease
      Hit:3 http://id.archive.ubuntu.com/ubuntu focal-backports InRelease
      Hit:4 http://id.archive.ubuntu.com/ubuntu focal-security InRelease
      Reading package lists...
      Reading package lists...
      Building dependency tree...
      Reading state information...
      python3 is already the newest version (3.8.2-0ubuntu2).
      curl is already the newest version (7.68.0-1ubuntu2.7).
      software-properties-common is already the newest version (0.99.9.8).
      ubuntu-standard is already the newest version (1.450.2).
      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      

      and freeze at that point, i waited 30 or 40 minutes and the log just stuck there so i decided to run the script again, this time the log stopped at nginx

      Processing triggers for mime-support (3.64ubuntu1) ...
      Processing triggers for resolvconf (1.82) ...
      
      echo "==> installing nginx for xenial for TLSv3 support"
      ==> installing nginx for xenial for TLSv3 support
      curl -sL http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/nginx_1.18.0-2~${ubuntu_codename}_amd64.deb -o /tmp/nginx.deb
      
      

      Just now i tried as your suggestion:

      
      noob@cloud:~$ systemctl stop systemd-resolved
      ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
      Authentication is required to stop 'systemd-resolved.service'.
      Authenticating as: noob
      Password:
      ==== AUTHENTICATION COMPLETE ===
      noob@cloud:~$ sudo systemctl disable systemd-resolved
      [sudo] password for noob:
      Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service.
      Removed /etc/systemd/system/multi-user.target.wants/systemd-resolved.service.
      noob@cloud:~$ sudo systemctl restart unbound
      noob@cloud:~$ sudo lsof -i :53
      COMMAND  PID    USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
      unbound 7366 unbound    3u  IPv6  53429      0t0  UDP ip6-localhost:domain
      unbound 7366 unbound    4u  IPv6  53430      0t0  TCP ip6-localhost:domain (LISTEN)
      unbound 7366 unbound    5u  IPv4  53431      0t0  UDP localhost:domain
      unbound 7366 unbound    6u  IPv4  53432      0t0  TCP localhost:domain (LISTEN)
      noob@cloud:~$ curl -sL http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/nginx_1.18.0-2~${ubuntu_codename}_amd64.deb -o /tmp/nginx.deb
      noob@cloud:~$ ls
      cloudron-setup
      noob@cloud:~$
      
      
      

      i think it still not downloading that deb file

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #10

      @mikewen8888 You can try without the -s in curl (which is silent mode)

      curl -L http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/nginx_1.18.0-2~${ubuntu_codename}_amd64.deb -o /tmp/nginx.deb
      
      M 1 Reply Last reply
      0
      • girishG girish

        @mikewen8888 You can try without the -s in curl (which is silent mode)

        curl -L http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/nginx_1.18.0-2~${ubuntu_codename}_amd64.deb -o /tmp/nginx.deb
        
        M Offline
        M Offline
        mikewen8888
        wrote on last edited by
        #11

        @girish this is without s

        noob@cloud:~$ curl -L http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/nginx_1.18.0-2~${ubuntu_codename}_amd64.deb -o /tmp/nginx.deb
          % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                         Dload  Upload   Total   Spent    Left  Speed
          0     0    0     0    0     0      0      0 --:--:--  0:00:19 --:--:--     0curl: (6) Could not resolve host: nginx.org
        
        
        nebulonN 1 Reply Last reply
        0
        • M mikewen8888

          @girish this is without s

          noob@cloud:~$ curl -L http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/nginx_1.18.0-2~${ubuntu_codename}_amd64.deb -o /tmp/nginx.deb
            % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                           Dload  Upload   Total   Spent    Left  Speed
            0     0    0     0    0     0      0      0 --:--:--  0:00:19 --:--:--     0curl: (6) Could not resolve host: nginx.org
          
          
          nebulonN Offline
          nebulonN Offline
          nebulon
          Staff
          wrote on last edited by
          #12

          @mikewen8888 so your server still seems to have DNS resolving issues. To avoid a lot of back and forth, if you want you could add our ssh support key to your server. The public key is at https://docs.cloudron.io/support/#ssh-keys and then send us a mail with your server IP to support@cloudron.io That way we can directly look at the issue to figure out what is wrong.

          M 2 Replies Last reply
          0
          • nebulonN nebulon

            @mikewen8888 so your server still seems to have DNS resolving issues. To avoid a lot of back and forth, if you want you could add our ssh support key to your server. The public key is at https://docs.cloudron.io/support/#ssh-keys and then send us a mail with your server IP to support@cloudron.io That way we can directly look at the issue to figure out what is wrong.

            M Offline
            M Offline
            mikewen8888
            wrote on last edited by
            #13

            @nebulon yes i would like that. please give me 2 days because i still at business trip outside town. I will get back to you soon after i prepare the key and email the address

            thank you very much for the support

            1 Reply Last reply
            1
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #14

              Since this is an internal VM, please also check that outbound DNS port 53 (udp/tcp) is allowed in the firewall

              M 1 Reply Last reply
              0
              • nebulonN nebulon

                @mikewen8888 so your server still seems to have DNS resolving issues. To avoid a lot of back and forth, if you want you could add our ssh support key to your server. The public key is at https://docs.cloudron.io/support/#ssh-keys and then send us a mail with your server IP to support@cloudron.io That way we can directly look at the issue to figure out what is wrong.

                M Offline
                M Offline
                mikewen8888
                wrote on last edited by mikewen8888
                #15

                @nebulon i already added the key using

                noob@cloud:~$ sudo nano /home/.ssh/authorized_keys
                
                

                and copy paste the keys into that file

                hope it was the right procedure since i had minimal ubuntu knowledge

                and already email the IP address

                1 Reply Last reply
                1
                • girishG girish

                  Since this is an internal VM, please also check that outbound DNS port 53 (udp/tcp) is allowed in the firewall

                  M Offline
                  M Offline
                  mikewen8888
                  wrote on last edited by
                  #16

                  @girish i tried this

                  noob@cloud:~$ sudo ss -ltn
                  State                  Recv-Q                  Send-Q                                   Local Address:Port                                    Peer Address:Port                 Process
                  LISTEN                 0                       70                                           127.0.0.1:33060                                        0.0.0.0:*
                  LISTEN                 0                       151                                          127.0.0.1:3306                                         0.0.0.0:*
                  LISTEN                 0                       4096                                           0.0.0.0:111                                          0.0.0.0:*
                  LISTEN                 0                       256                                          127.0.0.1:53                                           0.0.0.0:*
                  LISTEN                 0                       128                                            0.0.0.0:22                                           0.0.0.0:*
                  LISTEN                 0                       128                                          127.0.0.1:6010                                         0.0.0.0:*
                  LISTEN                 0                       128                                          127.0.0.1:6011                                         0.0.0.0:*
                  LISTEN                 0                       4096                                              [::]:111                                             [::]:*
                  LISTEN                 0                       256                                              [::1]:53                                              [::]:*
                  LISTEN                 0                       128                                               [::]:22                                              [::]:*
                  LISTEN                 0                       128                                              [::1]:6010                                            [::]:*
                  LISTEN                 0                       128                                              [::1]:6011                                            [::]:*
                  noob@cloud:~$
                  
                  

                  is that means that outbound 53 is opened?

                  M 1 Reply Last reply
                  0
                  • M mikewen8888

                    @girish i tried this

                    noob@cloud:~$ sudo ss -ltn
                    State                  Recv-Q                  Send-Q                                   Local Address:Port                                    Peer Address:Port                 Process
                    LISTEN                 0                       70                                           127.0.0.1:33060                                        0.0.0.0:*
                    LISTEN                 0                       151                                          127.0.0.1:3306                                         0.0.0.0:*
                    LISTEN                 0                       4096                                           0.0.0.0:111                                          0.0.0.0:*
                    LISTEN                 0                       256                                          127.0.0.1:53                                           0.0.0.0:*
                    LISTEN                 0                       128                                            0.0.0.0:22                                           0.0.0.0:*
                    LISTEN                 0                       128                                          127.0.0.1:6010                                         0.0.0.0:*
                    LISTEN                 0                       128                                          127.0.0.1:6011                                         0.0.0.0:*
                    LISTEN                 0                       4096                                              [::]:111                                             [::]:*
                    LISTEN                 0                       256                                              [::1]:53                                              [::]:*
                    LISTEN                 0                       128                                               [::]:22                                              [::]:*
                    LISTEN                 0                       128                                              [::1]:6010                                            [::]:*
                    LISTEN                 0                       128                                              [::1]:6011                                            [::]:*
                    noob@cloud:~$
                    
                    

                    is that means that outbound 53 is opened?

                    M Offline
                    M Offline
                    mikewen8888
                    wrote on last edited by
                    #17

                    @girish and @nebulon I managed to continue setup process after curl error (edit /etc/resolv.conf) and put nameserver my ISP provider DNS server address and move further into installation, but continue to have problem:

                    noob@cloud:~$ sudo ./cloudron-setup
                    
                    ##############################################
                             Cloudron Setup (latest)
                    ##############################################
                    
                     Follow setup logs in a second terminal with:
                     $ tail -f /var/log/cloudron-setup.log
                    
                     Join us at https://forum.cloudron.io for any questions.
                    
                    => Updating apt and installing script dependencies
                    => Checking version
                    => Downloading version 7.1.3 ...
                    => Installing base dependencies and downloading docker images (this takes some time) ...Init script failed. See /var/log/cloudron-setup.log for details
                    noob@cloud:~$ sudo nano /etc/resolv.conf
                    noob@cloud:~$ sudo ./cloudron-setup
                    
                    ##############################################
                             Cloudron Setup (latest)
                    ##############################################
                    
                     Follow setup logs in a second terminal with:
                     $ tail -f /var/log/cloudron-setup.log
                    
                     Join us at https://forum.cloudron.io for any questions.
                    
                    => Updating apt and installing script dependencies
                    => Checking version
                    => Downloading version 7.1.3 ...
                    => Installing base dependencies and downloading docker images (this takes some time) ...Init script failed. See /var/log/cloudron-setup.log for details
                    
                    

                    and this was the log:

                    Status: Downloaded newer image for cloudron/redis@sha256:30a5550c41c3be3a01dbf457497ba2f3c05f3121c595a17ef1aacbef931b6114
                    docker.io/cloudron/redis:3.2.1@sha256:30a5550c41c3be3a01dbf457497ba2f3c05f3121c595a17ef1aacbef931b6114
                    3.2.1: Pulling from cloudron/redis
                    Digest: sha256:30a5550c41c3be3a01dbf457497ba2f3c05f3121c595a17ef1aacbef931b6114
                    Status: Downloaded newer image for cloudron/redis:3.2.1
                    docker.io/cloudron/redis:3.2.1
                    docker.io/cloudron/mail@sha256:b8b93f007105080d4812a05648e6bc5e15c95c63f511c829cbc14a163d9ea029: Pulling from cloudron/mail
                    7b1a6ab2e44d: Already exists
                    d31a421b39ea: Already exists
                    c76a020f512e: Already exists
                    9b5e5618526c: Already exists
                    ed7c6b8f03d8: Already exists
                    c8c17ce1ab75: Already exists
                    efee782790c4: Already exists
                    808ed6fa660f: Already exists
                    1fa83f475aee: Already exists
                    18d03f295db8: Already exists
                    9cab82ff68f4: Already exists
                    4bcaeaf4f2f6: Already exists
                    5b9cc15aeb11: Already exists
                    4f8c28ca9c77: Pulling fs layer
                    2c132374d0c4: Pulling fs layer
                    7966fbdf5523: Pulling fs layer
                    e7279799347e: Pulling fs layer
                    7b9f10f5a3c6: Pulling fs layer
                    1c8de110044a: Pulling fs layer
                    3fc5bea24466: Pulling fs layer
                    80d8285bbdab: Pulling fs layer
                    0894df8c0d1f: Pulling fs layer
                    27a6541de7d0: Pulling fs layer
                    488082c15c3b: Pulling fs layer
                    2469ac626830: Pulling fs layer
                    3ff575c068a0: Pulling fs layer
                    d57d78c56c55: Pulling fs layer
                    da22a21498d3: Pulling fs layer
                    a66e38f3fe62: Pulling fs layer
                    0def8839514c: Pulling fs layer
                    0259ac685b11: Pulling fs layer
                    7f2daa1ea009: Pulling fs layer
                    d8c80dd67eaf: Pulling fs layer
                    e7279799347e: Waiting
                    7b9f10f5a3c6: Waiting
                    1c8de110044a: Waiting
                    3fc5bea24466: Waiting
                    80d8285bbdab: Waiting
                    0894df8c0d1f: Waiting
                    27a6541de7d0: Waiting
                    488082c15c3b: Waiting
                    2469ac626830: Waiting
                    3ff575c068a0: Waiting
                    d57d78c56c55: Waiting
                    da22a21498d3: Waiting
                    a66e38f3fe62: Waiting
                    0def8839514c: Waiting
                    0259ac685b11: Waiting
                    7f2daa1ea009: Waiting
                    d8c80dd67eaf: Waiting
                    error pulling image configuration: error parsing HTTP 409 response body: invalid character 'e' looking for beginning of value: "error code: 1001"
                    
                    

                    after this error, I can not resume nor try to run cloudron-setup script again:

                    noob@cloud:~$ sudo ./cloudron-setup
                    Error: Some packages like nginx/docker/nodejs are already installed. Cloudron requires specific versions of these packages and will install them as part of it's installation. Please start with a fresh Ubuntu install and run this script again.
                    noob@cloud:~$
                    
                    

                    can you please analyze what went wrong this time?

                    2 nights ago your guy did connect with ssh to the server, but he aborted the installation process due to slow internet connection of the server

                    nebulonN 1 Reply Last reply
                    0
                    • M mikewen8888

                      @girish and @nebulon I managed to continue setup process after curl error (edit /etc/resolv.conf) and put nameserver my ISP provider DNS server address and move further into installation, but continue to have problem:

                      noob@cloud:~$ sudo ./cloudron-setup
                      
                      ##############################################
                               Cloudron Setup (latest)
                      ##############################################
                      
                       Follow setup logs in a second terminal with:
                       $ tail -f /var/log/cloudron-setup.log
                      
                       Join us at https://forum.cloudron.io for any questions.
                      
                      => Updating apt and installing script dependencies
                      => Checking version
                      => Downloading version 7.1.3 ...
                      => Installing base dependencies and downloading docker images (this takes some time) ...Init script failed. See /var/log/cloudron-setup.log for details
                      noob@cloud:~$ sudo nano /etc/resolv.conf
                      noob@cloud:~$ sudo ./cloudron-setup
                      
                      ##############################################
                               Cloudron Setup (latest)
                      ##############################################
                      
                       Follow setup logs in a second terminal with:
                       $ tail -f /var/log/cloudron-setup.log
                      
                       Join us at https://forum.cloudron.io for any questions.
                      
                      => Updating apt and installing script dependencies
                      => Checking version
                      => Downloading version 7.1.3 ...
                      => Installing base dependencies and downloading docker images (this takes some time) ...Init script failed. See /var/log/cloudron-setup.log for details
                      
                      

                      and this was the log:

                      Status: Downloaded newer image for cloudron/redis@sha256:30a5550c41c3be3a01dbf457497ba2f3c05f3121c595a17ef1aacbef931b6114
                      docker.io/cloudron/redis:3.2.1@sha256:30a5550c41c3be3a01dbf457497ba2f3c05f3121c595a17ef1aacbef931b6114
                      3.2.1: Pulling from cloudron/redis
                      Digest: sha256:30a5550c41c3be3a01dbf457497ba2f3c05f3121c595a17ef1aacbef931b6114
                      Status: Downloaded newer image for cloudron/redis:3.2.1
                      docker.io/cloudron/redis:3.2.1
                      docker.io/cloudron/mail@sha256:b8b93f007105080d4812a05648e6bc5e15c95c63f511c829cbc14a163d9ea029: Pulling from cloudron/mail
                      7b1a6ab2e44d: Already exists
                      d31a421b39ea: Already exists
                      c76a020f512e: Already exists
                      9b5e5618526c: Already exists
                      ed7c6b8f03d8: Already exists
                      c8c17ce1ab75: Already exists
                      efee782790c4: Already exists
                      808ed6fa660f: Already exists
                      1fa83f475aee: Already exists
                      18d03f295db8: Already exists
                      9cab82ff68f4: Already exists
                      4bcaeaf4f2f6: Already exists
                      5b9cc15aeb11: Already exists
                      4f8c28ca9c77: Pulling fs layer
                      2c132374d0c4: Pulling fs layer
                      7966fbdf5523: Pulling fs layer
                      e7279799347e: Pulling fs layer
                      7b9f10f5a3c6: Pulling fs layer
                      1c8de110044a: Pulling fs layer
                      3fc5bea24466: Pulling fs layer
                      80d8285bbdab: Pulling fs layer
                      0894df8c0d1f: Pulling fs layer
                      27a6541de7d0: Pulling fs layer
                      488082c15c3b: Pulling fs layer
                      2469ac626830: Pulling fs layer
                      3ff575c068a0: Pulling fs layer
                      d57d78c56c55: Pulling fs layer
                      da22a21498d3: Pulling fs layer
                      a66e38f3fe62: Pulling fs layer
                      0def8839514c: Pulling fs layer
                      0259ac685b11: Pulling fs layer
                      7f2daa1ea009: Pulling fs layer
                      d8c80dd67eaf: Pulling fs layer
                      e7279799347e: Waiting
                      7b9f10f5a3c6: Waiting
                      1c8de110044a: Waiting
                      3fc5bea24466: Waiting
                      80d8285bbdab: Waiting
                      0894df8c0d1f: Waiting
                      27a6541de7d0: Waiting
                      488082c15c3b: Waiting
                      2469ac626830: Waiting
                      3ff575c068a0: Waiting
                      d57d78c56c55: Waiting
                      da22a21498d3: Waiting
                      a66e38f3fe62: Waiting
                      0def8839514c: Waiting
                      0259ac685b11: Waiting
                      7f2daa1ea009: Waiting
                      d8c80dd67eaf: Waiting
                      error pulling image configuration: error parsing HTTP 409 response body: invalid character 'e' looking for beginning of value: "error code: 1001"
                      
                      

                      after this error, I can not resume nor try to run cloudron-setup script again:

                      noob@cloud:~$ sudo ./cloudron-setup
                      Error: Some packages like nginx/docker/nodejs are already installed. Cloudron requires specific versions of these packages and will install them as part of it's installation. Please start with a fresh Ubuntu install and run this script again.
                      noob@cloud:~$
                      
                      

                      can you please analyze what went wrong this time?

                      2 nights ago your guy did connect with ssh to the server, but he aborted the installation process due to slow internet connection of the server

                      nebulonN Offline
                      nebulonN Offline
                      nebulon
                      Staff
                      wrote on last edited by
                      #18

                      @mikewen8888 can you try to run the following command and see if that succeeds?

                      docker pull cloudron/mail@sha256:b8b93f007105080d4812a05648e6bc5e15c95c63f511c829cbc14a163d9ea029
                      

                      If so, it might have been a temporary docker hub issue. Also check if there is enough disk space available. Then reset the server back to the pristine Ubuntu image and retry the cloudron-setup

                      M 1 Reply Last reply
                      0
                      • nebulonN nebulon

                        @mikewen8888 can you try to run the following command and see if that succeeds?

                        docker pull cloudron/mail@sha256:b8b93f007105080d4812a05648e6bc5e15c95c63f511c829cbc14a163d9ea029
                        

                        If so, it might have been a temporary docker hub issue. Also check if there is enough disk space available. Then reset the server back to the pristine Ubuntu image and retry the cloudron-setup

                        M Offline
                        M Offline
                        mikewen8888
                        wrote on last edited by
                        #19

                        @nebulon i re-create the VM

                        install new ubuntu sever
                        run cloudron-setup script
                        encounter curl error
                        edit resolv.conf
                        re-run cloudron-setup
                        this time, docker went through with no problem
                        finished installing base dependencies and downloading docker images
                        installing version 7.1.3

                        and encounter new problem:

                        # we need unbound to work as this is required for installer.sh to do any DNS requests
                        echo -e "server:\n\tinterface: 127.0.0.1\n\tdo-ip6: no" > /etc/unbound/unbound.conf.d/cloudron-network.conf
                        systemctl restart unbound
                        cat: /home/yellowtent/box/VERSION: No such file or directory
                        2022-03-04T14:58:59 ==> installer: Updating from  to 7.1.3
                        2022-03-04T14:58:59 ==> installer: updating docker
                        /usr/sbin/mount.nfs
                        /usr/bin/sshfs
                        2022-03-04T14:58:59 ==> installer: updating node
                        rebuilt dependencies successfully
                        2022-03-04T14:59:27 ==> installer: downloading new addon images
                        2022-03-04T14:59:27 ==> installer:      Pulling docker images: cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea cloudron/turn:1.4.0@sha256:45817f1631992391d585f171498d257487d872480fd5646723a2b956cc4ef15d cloudron/mysql:3.2.1@sha256:75cef64ba4917ba9ec68bc0c9d9ba3a9eeae00a70173cd6d81cc6118038737d9 cloudron/postgresql:4.3.0@sha256:9f0cfe83310a6f67885c21804c01e73c8d256606217f44dcefb3e05a5402b2c9 cloudron/mongodb:4.2.0@sha256:c8ebdbe2663b26fcd58b1e6b97906b62565adbe4a06256ba0f86114f78b37e6b cloudron/redis:3.2.1@sha256:30a5550c41c3be3a01dbf457497ba2f3c05f3121c595a17ef1aacbef931b6114 cloudron/mail:3.6.1@sha256:b8b93f007105080d4812a05648e6bc5e15c95c63f511c829cbc14a163d9ea029 cloudron/graphite:3.1.0@sha256:30ec3a01964a1e01396acf265183997c3e17fb07eac1a82b979292cc7719ff4b cloudron/sftp:3.6.0@sha256:9c686b10c1a3ba344a743f399d08b4da5426e111f455114980f0ae0229c1ab23
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T14:59:42 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:00:02 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:00:22 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:00:42 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:01:02 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded
                        2022-03-04T15:01:22 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:01:42 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:02:02 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:02:22 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:02:42 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:03:02 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded
                        2022-03-04T15:03:22 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:03:43 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:04:03 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:04:23 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:04:43 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:05:03 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        2022-03-04T15:05:23 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                        Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                        
                        

                        its still keep running with that kind of error

                        please advice what to do

                        M 1 Reply Last reply
                        0
                        • M mikewen8888

                          @nebulon i re-create the VM

                          install new ubuntu sever
                          run cloudron-setup script
                          encounter curl error
                          edit resolv.conf
                          re-run cloudron-setup
                          this time, docker went through with no problem
                          finished installing base dependencies and downloading docker images
                          installing version 7.1.3

                          and encounter new problem:

                          # we need unbound to work as this is required for installer.sh to do any DNS requests
                          echo -e "server:\n\tinterface: 127.0.0.1\n\tdo-ip6: no" > /etc/unbound/unbound.conf.d/cloudron-network.conf
                          systemctl restart unbound
                          cat: /home/yellowtent/box/VERSION: No such file or directory
                          2022-03-04T14:58:59 ==> installer: Updating from  to 7.1.3
                          2022-03-04T14:58:59 ==> installer: updating docker
                          /usr/sbin/mount.nfs
                          /usr/bin/sshfs
                          2022-03-04T14:58:59 ==> installer: updating node
                          rebuilt dependencies successfully
                          2022-03-04T14:59:27 ==> installer: downloading new addon images
                          2022-03-04T14:59:27 ==> installer:      Pulling docker images: cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea cloudron/turn:1.4.0@sha256:45817f1631992391d585f171498d257487d872480fd5646723a2b956cc4ef15d cloudron/mysql:3.2.1@sha256:75cef64ba4917ba9ec68bc0c9d9ba3a9eeae00a70173cd6d81cc6118038737d9 cloudron/postgresql:4.3.0@sha256:9f0cfe83310a6f67885c21804c01e73c8d256606217f44dcefb3e05a5402b2c9 cloudron/mongodb:4.2.0@sha256:c8ebdbe2663b26fcd58b1e6b97906b62565adbe4a06256ba0f86114f78b37e6b cloudron/redis:3.2.1@sha256:30a5550c41c3be3a01dbf457497ba2f3c05f3121c595a17ef1aacbef931b6114 cloudron/mail:3.6.1@sha256:b8b93f007105080d4812a05648e6bc5e15c95c63f511c829cbc14a163d9ea029 cloudron/graphite:3.1.0@sha256:30ec3a01964a1e01396acf265183997c3e17fb07eac1a82b979292cc7719ff4b cloudron/sftp:3.6.0@sha256:9c686b10c1a3ba344a743f399d08b4da5426e111f455114980f0ae0229c1ab23
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T14:59:42 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:00:02 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:00:22 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:00:42 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:01:02 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded
                          2022-03-04T15:01:22 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:01:42 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:02:02 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:02:22 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:02:42 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:03:02 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded
                          2022-03-04T15:03:22 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:03:43 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:04:03 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:04:23 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:04:43 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:05:03 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          2022-03-04T15:05:23 ==> installer: Could not pull cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea
                          Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
                          
                          

                          its still keep running with that kind of error

                          please advice what to do

                          M Offline
                          M Offline
                          mikewen8888
                          wrote on last edited by
                          #20

                          @nebulon very strange, resolv.conf change again

                          so while the log still showing that error response from daemon
                          i edit (again) resolv.conf and put my ISP DNS server address

                          now it is success, finished the cloudron installation

                          so the step was:

                          install new ubuntu sever
                          run cloudron-setup script
                          encounter curl error
                          edit resolv.conf
                          re-run cloudron-setup
                          this time, docker went through with no problem
                          finished installing base dependencies and downloading docker images
                          installing version 7.1.3
                          encounter error response from daemon
                          edit resolv.conf (again)
                          error gone, continue with docker pull
                          finished installation

                          noob@cloud:~$ sudo ./cloudron-setup
                          
                          ##############################################
                                   Cloudron Setup (latest)
                          ##############################################
                          
                           Follow setup logs in a second terminal with:
                           $ tail -f /var/log/cloudron-setup.log
                          
                           Join us at https://forum.cloudron.io for any questions.
                          
                          => Updating apt and installing script dependencies
                          => Checking version
                          => Downloading version 7.1.3 ...
                          => Installing base dependencies and downloading docker images (this takes some time) ...
                          => Installing version 7.1.3 (this takes some time) ...
                          => Waiting for cloudron to be ready (this takes some time) ....
                          
                          After reboot, visit https://<IP> and accept the self-signed certificate to finish setup.
                          
                          The server has to be rebooted to apply all the settings. Reboot now ? [Y/n]
                          
                          
                          
                          [INFO] Processed migration 20210517194116-backups-provider-mountpoint
                          [INFO] Processed migration 20210528205138-notifications-drop-userId
                          [INFO] Processed migration 20210625061443-volumes-change-noop-to-mountpoint
                          [INFO] Processed migration 20210707154724-users-migrate-avatar
                          [INFO] Processed migration 20210729191138-domains-update-wellKnown-matrix-client
                          [INFO] Processed migration 20210809203855-appAddonConfigs-alter-value
                          [INFO] Processed migration 20210820172800-users-alter-loginLocationsJson
                          [INFO] Processed migration 20210921022843-apps-add-operatorsJson
                          [INFO] Processed migration 20210927211658-apps-add-crontab
                          [INFO] Processed migration 20211001095256-users-add-inviteToken
                          [INFO] Processed migration 20211001160903-apps-add-inbox
                          [INFO] Processed migration 20211006200150-domains-ensure-fallbackCertificate
                          [INFO] Processed migration 20211008171126-mailboxes-add-enablePop3
                          [INFO] Processed migration 20211012020255-mail-add-dkimKeyJson
                          [INFO] Processed migration 20211117070204-blobs-delete-dhparams
                          [INFO] Processed migration 20211117201805-eventlog-rename-source-to-sourceJson
                          [INFO] Processed migration 20220107015249-settings-sysinfo-ip-to-ipv4
                          [INFO] Processed migration 20220113223425-settings-rename-directory-config-to-profile-config
                          [INFO] Processed migration 20220115070646-subdomains-add-environmentVariable
                          [INFO] Processed migration 20220202011148-blobs-migrate-token-secret
                          [INFO] Processed migration 20220207214956-rename-subdomains-to-locations
                          [INFO] Processed migration 20220219220751-mail-ensure-dkimKey
                          [INFO] Done
                          2022-03-04T15:22:03 ==> start: Changing ownership
                          2022-03-04T15:22:03 ==> start: Starting Cloudron
                          2022-03-04T15:22:05 ==> start: Almost done
                          
                          

                          any idea what's went wrong, it was always DNS resolver change to localhost

                          M 1 Reply Last reply
                          0
                          • M mikewen8888

                            @nebulon very strange, resolv.conf change again

                            so while the log still showing that error response from daemon
                            i edit (again) resolv.conf and put my ISP DNS server address

                            now it is success, finished the cloudron installation

                            so the step was:

                            install new ubuntu sever
                            run cloudron-setup script
                            encounter curl error
                            edit resolv.conf
                            re-run cloudron-setup
                            this time, docker went through with no problem
                            finished installing base dependencies and downloading docker images
                            installing version 7.1.3
                            encounter error response from daemon
                            edit resolv.conf (again)
                            error gone, continue with docker pull
                            finished installation

                            noob@cloud:~$ sudo ./cloudron-setup
                            
                            ##############################################
                                     Cloudron Setup (latest)
                            ##############################################
                            
                             Follow setup logs in a second terminal with:
                             $ tail -f /var/log/cloudron-setup.log
                            
                             Join us at https://forum.cloudron.io for any questions.
                            
                            => Updating apt and installing script dependencies
                            => Checking version
                            => Downloading version 7.1.3 ...
                            => Installing base dependencies and downloading docker images (this takes some time) ...
                            => Installing version 7.1.3 (this takes some time) ...
                            => Waiting for cloudron to be ready (this takes some time) ....
                            
                            After reboot, visit https://<IP> and accept the self-signed certificate to finish setup.
                            
                            The server has to be rebooted to apply all the settings. Reboot now ? [Y/n]
                            
                            
                            
                            [INFO] Processed migration 20210517194116-backups-provider-mountpoint
                            [INFO] Processed migration 20210528205138-notifications-drop-userId
                            [INFO] Processed migration 20210625061443-volumes-change-noop-to-mountpoint
                            [INFO] Processed migration 20210707154724-users-migrate-avatar
                            [INFO] Processed migration 20210729191138-domains-update-wellKnown-matrix-client
                            [INFO] Processed migration 20210809203855-appAddonConfigs-alter-value
                            [INFO] Processed migration 20210820172800-users-alter-loginLocationsJson
                            [INFO] Processed migration 20210921022843-apps-add-operatorsJson
                            [INFO] Processed migration 20210927211658-apps-add-crontab
                            [INFO] Processed migration 20211001095256-users-add-inviteToken
                            [INFO] Processed migration 20211001160903-apps-add-inbox
                            [INFO] Processed migration 20211006200150-domains-ensure-fallbackCertificate
                            [INFO] Processed migration 20211008171126-mailboxes-add-enablePop3
                            [INFO] Processed migration 20211012020255-mail-add-dkimKeyJson
                            [INFO] Processed migration 20211117070204-blobs-delete-dhparams
                            [INFO] Processed migration 20211117201805-eventlog-rename-source-to-sourceJson
                            [INFO] Processed migration 20220107015249-settings-sysinfo-ip-to-ipv4
                            [INFO] Processed migration 20220113223425-settings-rename-directory-config-to-profile-config
                            [INFO] Processed migration 20220115070646-subdomains-add-environmentVariable
                            [INFO] Processed migration 20220202011148-blobs-migrate-token-secret
                            [INFO] Processed migration 20220207214956-rename-subdomains-to-locations
                            [INFO] Processed migration 20220219220751-mail-ensure-dkimKey
                            [INFO] Done
                            2022-03-04T15:22:03 ==> start: Changing ownership
                            2022-03-04T15:22:03 ==> start: Starting Cloudron
                            2022-03-04T15:22:05 ==> start: Almost done
                            
                            

                            any idea what's went wrong, it was always DNS resolver change to localhost

                            M Offline
                            M Offline
                            mikewen8888
                            wrote on last edited by mikewen8888
                            #21

                            @nebulon do i need to change resolv.conf back to local host, or keep my ISP DNS server address for cloudron to work?

                            nebulonN 1 Reply Last reply
                            0
                            • M mikewen8888

                              @nebulon do i need to change resolv.conf back to local host, or keep my ISP DNS server address for cloudron to work?

                              nebulonN Offline
                              nebulonN Offline
                              nebulon
                              Staff
                              wrote on last edited by
                              #22

                              @mikewen8888 Cloudron will set the DNS resolver to localhost as it requires unbound to run there. Given that you seem to hit a lot of rather random errors, which I don't believe many other users have ever hit, I wonder how your server setup is done. When I debugged your home server it also had strange DNS issues now this one as well running apparently in another network. Are you using any special Ubuntu flavor or have some non-standard routing setup for those servers?

                              M 1 Reply Last reply
                              0
                              • nebulonN nebulon

                                @mikewen8888 Cloudron will set the DNS resolver to localhost as it requires unbound to run there. Given that you seem to hit a lot of rather random errors, which I don't believe many other users have ever hit, I wonder how your server setup is done. When I debugged your home server it also had strange DNS issues now this one as well running apparently in another network. Are you using any special Ubuntu flavor or have some non-standard routing setup for those servers?

                                M Offline
                                M Offline
                                mikewen8888
                                wrote on last edited by mikewen8888
                                #23

                                @nebulon I agree
                                I believed that many users will have smooth installation

                                I downloaded ubuntu server 20.4.03 ISO from their website, create vm under esxi 6.7 and i use pfsense as my router and firewall in my home, and i don't know if my firewall setting is non-standard

                                next week i will put production server in my local server hosting provider and make a fresh ubuntu/cloudron installation from there and hopefully the installation will working without any trouble like this thread

                                anyway, i appreciate all cloudron's staff helping me with this issue

                                1 Reply Last reply
                                1
                                • subvenS subven referenced this topic on
                                • girishG girish forked this topic on
                                • girishG girish locked this topic on
                                Reply
                                • Reply as topic
                                Log in to reply
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes


                                • Login

                                • Don't have an account? Register

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