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. System not working for the app store

System not working for the app store

Scheduled Pinned Locked Moved Solved Support
unboundappstore
2 Posts 2 Posters 304 Views 2 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.
    • S Offline
      S Offline
      stlpedro
      wrote on last edited by girish
      #1

      System has been very unstable with a bunch of issues in the last couple of days. I just got in and saw that the dns resolution is not working...

      Tried the other things in the forum but it still not working. This is prod so we need it back up as soon as possible.

      ubuntu@cr1:~$ sudo systemctl status unbound-resolvconf.service
      ā— unbound-resolvconf.service - Unbound DNS server via resolvconf
      Loaded: loaded (/lib/systemd/system/unbound-resolvconf.service; enabled; vendor preset: enabled)
      Active: failed (Result: start-limit-hit) since Wed 2023-06-28 20:52:23 UTC; 35s ago
      Process: 1155 ExecStart=/usr/lib/unbound/package-helper resolvconf_start (code=exited, status=0/SUCCESS)
      Process: 1200 ExecStop=/usr/lib/unbound/package-helper resolvconf_stop (code=exited, status=0/SUCCESS)
      Main PID: 1155 (code=exited, status=0/SUCCESS)

      Jun 28 20:52:22 cr1 systemd[1]: Started Unbound DNS server via resolvconf.
      Jun 28 20:52:23 cr1 systemd[1]: Stopping Unbound DNS server via resolvconf...
      Jun 28 20:52:23 cr1 systemd[1]: unbound-resolvconf.service: Succeeded.
      Jun 28 20:52:23 cr1 systemd[1]: Stopped Unbound DNS server via resolvconf.
      Jun 28 20:52:23 cr1 systemd[1]: unbound-resolvconf.service: Start request repeated too quickly.
      Jun 28 20:52:23 cr1 systemd[1]: unbound-resolvconf.service: Failed with result 'start-limit-hit'.
      Jun 28 20:52:23 cr1 systemd[1]: Failed to start Unbound DNS server via resolvconf.

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

        Right, you need to figure why unbound is not starting. The logs are in journalctl -u unbound -fa . Note that if unbound doesn't work, DNS doesnt work properly on the server and makes this quite unstable (as you experienced already).

        1 Reply Last reply
        0
        • girishG girish marked this topic as a question on
        • girishG girish has marked this topic as solved 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