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. Unable to log into the app store

Unable to log into the app store

Scheduled Pinned Locked Moved Solved Support
appstore
7 Posts 4 Posters 873 Views 4 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.
    • therealcoldguyT Offline
      therealcoldguyT Offline
      therealcoldguy
      wrote on last edited by girish
      #1

      Hi all I have a cloudron instance hosted on linode and looking to add an app to it. I click on the cloud store link and it is requiring me to log in. No big deal, I enter the information and it is telling me that the email already exists. Which is correct I bought a subscription. I check to make sure I am on the log in screen and not the register for an account and verify that this is the case. Tried it in Firefox and Chrome and getting the same error. Any ideas?

      1 Reply Last reply
      0
      • nebulonN Away
        nebulonN Away
        nebulon
        Staff
        wrote on last edited by
        #2

        Can you send an email with your cloudron.io account email to support@cloudron.io then I can see what is failing there.

        therealcoldguyT 1 Reply Last reply
        0
        • nebulonN nebulon

          Can you send an email with your cloudron.io account email to support@cloudron.io then I can see what is failing there.

          therealcoldguyT Offline
          therealcoldguyT Offline
          therealcoldguy
          wrote on last edited by
          #3

          @nebulon I just sent an email with the information, let me know if there is anything else you need.

          girishG 1 Reply Last reply
          0
          • therealcoldguyT therealcoldguy

            @nebulon I just sent an email with the information, let me know if there is anything else you need.

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

            @therealcoldguy thanks.

            So, the issue here was that unbound was down for some reason (this is usually because server ran out of disk space at some point).

            root@localhost:~# host my.cloudron.io
            ;; connection timed out; no servers could be reached
            
            root@localhost:~# systemctl status unbound
            ā— unbound.service - Unbound DNS Resolver
                 Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled)
                 Active: failed (Result: exit-code) since Thu 2021-12-30 15:18:35 UTC; 1 months 19 days ago
                Process: 2883 ExecStart=/usr/sbin/unbound -d (code=exited, status=1/FAILURE)
               Main PID: 2883 (code=exited, status=1/FAILURE)
            
            Warning: journal has been rotated since unit was started, output may be incomplete.
            

            systemctl restart unbound fixes the problem.

            robiR 1 Reply Last reply
            0
            • girishG girish

              @therealcoldguy thanks.

              So, the issue here was that unbound was down for some reason (this is usually because server ran out of disk space at some point).

              root@localhost:~# host my.cloudron.io
              ;; connection timed out; no servers could be reached
              
              root@localhost:~# systemctl status unbound
              ā— unbound.service - Unbound DNS Resolver
                   Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled)
                   Active: failed (Result: exit-code) since Thu 2021-12-30 15:18:35 UTC; 1 months 19 days ago
                  Process: 2883 ExecStart=/usr/sbin/unbound -d (code=exited, status=1/FAILURE)
                 Main PID: 2883 (code=exited, status=1/FAILURE)
              
              Warning: journal has been rotated since unit was started, output may be incomplete.
              

              systemctl restart unbound fixes the problem.

              robiR Offline
              robiR Offline
              robi
              wrote on last edited by
              #5

              @girish How can some test conditions be added so that when they fail, the affected service is restarted to attempt resilience, instead of failure?

              Conscious tech

              girishG 1 Reply Last reply
              0
              • robiR robi

                @girish How can some test conditions be added so that when they fail, the affected service is restarted to attempt resilience, instead of failure?

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

                @robi yeah, it's getting fixed! the appstore view needs to a show a proper error message that it cannot contact cloudron.io. As for unbound, what happens is:

                • Server runs out of disk space
                • unbound writes a 0 sized anchor file
                • It won't start anymore despite server restart.

                It's same issue as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232555

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

                  Here's the debian bug for unbound - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989959

                  1 Reply Last reply
                  1
                  • girishG girish referenced 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