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. Clicking on a Domain's email section in the Dashboard causes Cloudron to totally restart!

Clicking on a Domain's email section in the Dashboard causes Cloudron to totally restart!

Scheduled Pinned Locked Moved Solved Support
domainsmaildashboard
19 Posts 4 Posters 2.2k 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.
  • scookeS scooke

    @girish
    What's below is all in the log. I was on the Domain panel, it had been stable for awhile and I hadn't done anything, but as soon as I clicked on the Email link, it restarted. I wrote anotherdomain.com this time because this was a new domain seemingly connected to this problem. I've even cleared out domains that weren't in use, and rebooted, before this latest restart.

    Jul 10 23:06:12 box:apphealthmonitor app health: 26 alive / 3 dead.
    Jul 10 23:06:13 box:cloudron Getting logs for box as json
    Jul 10 23:06:22 box:apphealthmonitor app health: 26 alive / 3 dead.
    TypeError: Cannot convert name to ASCII
    at Resolver.queryTxt [as resolveTxt] (dns.js:227:48)
    at Resolver.resolve (dns.js:263:21)
    at Object.resolve (/home/yellowtent/box/src/native-dns.js:32:14)
    at checkDkim (/home/yellowtent/box/src/mail.js:220:9)
    at /home/yellowtent/box/src/mail.js:480:13
    at /home/yellowtent/box/node_modules/async/dist/async.js:2948:28
    at eachOfArrayLike (/home/yellowtent/box/node_modules/async/dist/async.js:500:13)
    at eachOf (/home/yellowtent/box/node_modules/async/dist/async.js:551:16)
    at awaitable (/home/yellowtent/box/node_modules/async/dist/async.js:208:32)
    at /home/yellowtent/box/node_modules/async/dist/async.js:2947:9 [ /home/yellowtent/box/box.js:61:17 ]
    Jul 10 23:06:24 box:mail checkRblStatus: anotherdomain.com (ip: 209.182.238.112) servers: []
    Jul 10 23:06:29 box:server ==========================================
    Jul 10 23:06:29 box:server Cloudron 6.2.8
    Jul 10 23:06:29 box:server ==========================================
    Jul 10 23:06:29 box:settings initCache: pre-load settings
    Jul 10 23:06:29 box:tasks stopTask: stopping all tasks
    Jul 10 23:06:29 box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
    Jul 10 23:06:30 box:dockerproxy startDockerProxy: started proxy on port 3003
    is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
    Jul 10 23:06:30 box:shell removeCollectdProfile spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurecollectd.sh remove cloudron-backup
    Jul 10 23:06:30 box:shell removeCollectdProfile (stdout): Restarting collectd
    Jul 10 23:06:30 box:shell removeCollectdProfile (stdout): Removing collectd stats of cloudron-backup
    Jul 10 23:06:30 box:reverseproxy writeDashboardConfig: writing admin config for toutdo.com
    Jul 10 23:06:30 box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
    Jul 10 23:06:31 box:platform initializing addon infrastructure
    Jul 10 23:06:31 box:platform platform is uptodate at version 48.18.0
    Jul 10 23:06:31 box:platform onPlatformReady: platform is ready. infra changed: false
    Jul 10 23:06:31 box:apps schedulePendingTasks: scheduling app tasks
    Jul 10 23:06:31 box:cron startJobs: starting cron jobs
    Jul 10 23:06:31 box:cron backupConfigChanged: schedule 00 00 23 * * 1,3,5 (Europe/Paris)
    Jul 10 23:06:31 box:cron autoupdatePatternChanged: pattern - never (Europe/Paris)
    Jul 10 23:06:31 box:cron Dynamic DNS setting changed to false
    Jul 10 23:06:32 box:notifications alert: id=backupConfig title=Backup configuration is unsafe ack=true
    Jul 10 23:06:42 box:apphealthmonitor app health: 26 alive / 3 dead.
    Jul 10 23:06:42 box:cloudron Getting logs for box as json
    
    girishG Offline
    girishG Offline
    girish
    Staff
    wrote on last edited by
    #8

    @scooke Can you write to us at support@cloudron.io ? Would be good to have this fixed because I can't make out what the issue is. Thanks!

    scookeS 1 Reply Last reply
    0
    • girishG girish

      @scooke Can you write to us at support@cloudron.io ? Would be good to have this fixed because I can't make out what the issue is. Thanks!

      scookeS Offline
      scookeS Offline
      scooke
      wrote on last edited by
      #9

      @girish Ok, will do.

      A life lived in fear is a life half-lived

      1 Reply Last reply
      0
      • scookeS Offline
        scookeS Offline
        scooke
        wrote on last edited by
        #10

        So, I've sent you an email, but I've been poking around, and removed an IDN domain that didn't have an app installed. Even though it wasn't the initial domain that seemed to spark the problem, it could be related to the other little nugget that was in the logs, something about not being able to translate to ASCII.

        If this is related, could there be an issue with IDN domains on Cloudron? I had both a Chinese domain, and a RtL domain. I've removed both, and so far when I go to a few different places in the Dashboard, and then click in Email, everything works smooth, the green circles appear almost instanteously (where before it took awhile).

        One of the IDN's didn't actually have an A record pointing to the Cloudron (the Chinese one). Could that have caused some glitch?

        A life lived in fear is a life half-lived

        nebulonN luckowL 2 Replies Last reply
        0
        • scookeS scooke

          So, I've sent you an email, but I've been poking around, and removed an IDN domain that didn't have an app installed. Even though it wasn't the initial domain that seemed to spark the problem, it could be related to the other little nugget that was in the logs, something about not being able to translate to ASCII.

          If this is related, could there be an issue with IDN domains on Cloudron? I had both a Chinese domain, and a RtL domain. I've removed both, and so far when I go to a few different places in the Dashboard, and then click in Email, everything works smooth, the green circles appear almost instanteously (where before it took awhile).

          One of the IDN's didn't actually have an A record pointing to the Cloudron (the Chinese one). Could that have caused some glitch?

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

          @scooke right, we are using the native nodejs resolver here https://nodejs.org/dist/latest-v14.x/docs/api/dns.html#dns_class_dns_resolver and it appears to be crashing there.

          1 Reply Last reply
          0
          • scookeS scooke

            So, I've sent you an email, but I've been poking around, and removed an IDN domain that didn't have an app installed. Even though it wasn't the initial domain that seemed to spark the problem, it could be related to the other little nugget that was in the logs, something about not being able to translate to ASCII.

            If this is related, could there be an issue with IDN domains on Cloudron? I had both a Chinese domain, and a RtL domain. I've removed both, and so far when I go to a few different places in the Dashboard, and then click in Email, everything works smooth, the green circles appear almost instanteously (where before it took awhile).

            One of the IDN's didn't actually have an A record pointing to the Cloudron (the Chinese one). Could that have caused some glitch?

            luckowL Offline
            luckowL Offline
            luckow
            translator
            wrote on last edited by
            #12

            @scooke Universal Acceptance is a (not so) big issue for the internet. In short, for domains other than ascii, the internet seems to be broken.
            There is an initiative around domains other than ascii called Universal Acceptance https://uasg.tech/
            It's not just about Chinese domains. Try sending an email to thomas@müller.de, it will fail.

            Pronouns: he/him | Primary language: German

            nebulonN scookeS 2 Replies Last reply
            1
            • luckowL luckow

              @scooke Universal Acceptance is a (not so) big issue for the internet. In short, for domains other than ascii, the internet seems to be broken.
              There is an initiative around domains other than ascii called Universal Acceptance https://uasg.tech/
              It's not just about Chinese domains. Try sending an email to thomas@müller.de, it will fail.

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

              To update, I can reproduce this with a chineses IDN and looking for a fix now.

              scookeS 1 Reply Last reply
              0
              • nebulonN nebulon

                To update, I can reproduce this with a chineses IDN and looking for a fix now.

                scookeS Offline
                scookeS Offline
                scooke
                wrote on last edited by
                #14

                @nebulon I wonder why this would pop up now. Both the Chinese domain and the RtL domain were on my Cloudron for a long time. Thanks for looking into it @nebulon.

                And interesting link @luckow. I'm reading some of the info there now.

                A life lived in fear is a life half-lived

                girishG 1 Reply Last reply
                1
                • scookeS scooke

                  @nebulon I wonder why this would pop up now. Both the Chinese domain and the RtL domain were on my Cloudron for a long time. Thanks for looking into it @nebulon.

                  And interesting link @luckow. I'm reading some of the info there now.

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

                  @scooke Could be related to the fact that recent updates upgraded nodejs.

                  1 Reply Last reply
                  1
                  • luckowL luckow

                    @scooke Universal Acceptance is a (not so) big issue for the internet. In short, for domains other than ascii, the internet seems to be broken.
                    There is an initiative around domains other than ascii called Universal Acceptance https://uasg.tech/
                    It's not just about Chinese domains. Try sending an email to thomas@müller.de, it will fail.

                    scookeS Offline
                    scookeS Offline
                    scooke
                    wrote on last edited by
                    #16

                    @luckow Before I send an email to Mr. Thomas Müller, will he be expecting it, or no? Is this someone real?

                    A life lived in fear is a life half-lived

                    luckowL 1 Reply Last reply
                    0
                    • scookeS scooke

                      @luckow Before I send an email to Mr. Thomas Müller, will he be expecting it, or no? Is this someone real?

                      luckowL Offline
                      luckowL Offline
                      luckow
                      translator
                      wrote on last edited by
                      #17

                      @scooke wait. let's see 🙂 https://müller.de/ is a connected domain (not mine). And maybe there is a thomas there 🙂
                      Send out and say it's only a test 😉

                      Pronouns: he/him | Primary language: German

                      scookeS 1 Reply Last reply
                      0
                      • luckowL luckow

                        @scooke wait. let's see 🙂 https://müller.de/ is a connected domain (not mine). And maybe there is a thomas there 🙂
                        Send out and say it's only a test 😉

                        scookeS Offline
                        scookeS Offline
                        scooke
                        wrote on last edited by scooke
                        #18

                        @luckow The email was returned!

                        <thomas@xn--mller-kva.de>: host w015e2f2.kasserver.com[85.13.157.81] said: 554
                            5.7.1 <thomas@xn--mller-kva.de>: Relay access denied (in reply to RCPT TO command)
                        

                        However, sending emails to my two IDN domains work fine. Even using the "real" name of the domain and not the punycode rendering. These are though MXroute.

                        I guess the issue is in the updated nodejs.

                        A life lived in fear is a life half-lived

                        nebulonN 1 Reply Last reply
                        0
                        • scookeS scooke

                          @luckow The email was returned!

                          <thomas@xn--mller-kva.de>: host w015e2f2.kasserver.com[85.13.157.81] said: 554
                              5.7.1 <thomas@xn--mller-kva.de>: Relay access denied (in reply to RCPT TO command)
                          

                          However, sending emails to my two IDN domains work fine. Even using the "real" name of the domain and not the punycode rendering. These are though MXroute.

                          I guess the issue is in the updated nodejs.

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

                          @scooke we have traced this down to a nodejs bug apparently with the domain in question.
                          The upstream issue is at https://github.com/nodejs/node/issues/39397

                          1 Reply Last reply
                          2
                          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