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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Configuring External Directory causes Cloudron to reboot

    Support
    external-ldap
    2
    8
    61
    Loading More Posts
    • 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.
    • P
      phsc last edited by girish

      I am trying to configure an External Directory (Active Directory on Win Server 2016). I have been putting in the minimum amount of information to save the configuration, but get an error and a disconnection. Looking at the event log, each time this happens, there is a boot event.

      error.PNG

      event.PNG

      This was happening with version 7.2.5, as well as the latest version 7.3.4.
      Cloudron is hosted on premises - Latest version of Ubuntu on Hyper-V Host.
      I'm not very experienced in this field, so not sure if I'm doing something wrong or what.

      Thanks in advance.

      1 Reply Last reply Reply Quote 0
      • nebulon
        nebulon Staff last edited by

        Can you check the box.log file on the server via SSH? That file is located at /home/yellowtent/platformdata/logs/box.log and should contain some crash or something causing the restart of that service.

        P 1 Reply Last reply Reply Quote 0
        • Topic has been marked as a question  nebulon nebulon 
        • P
          phsc @nebulon last edited by

          @nebulon said in Configuring External Directory causes Cloudron to reboot:

          /home/yellowtent/platformdata/logs/box.log

          Not a whole lot from what I can see.

          log.PNG

          Although I have realised I can't ping local netbios names. I tried to get that going but have so far been unsuccessful (mucking around with winbind).

          1 Reply Last reply Reply Quote 0
          • nebulon
            nebulon Staff last edited by

            I don't know what winbind is, but seems like there is a dns resolving crash in the code, although with a surprising small stacktrace.

            P 1 Reply Last reply Reply Quote 0
            • P
              phsc @nebulon last edited by

              Given that the error said it couldn't find mydomain.local, I attempted to ping it, with no response. I was then taking a stab in the dark assuming that if I could get a response via a ping, it might then find the server and successfully connect. Google has told me that Ubuntu by default doesn't resolve windows hostnames, and that everyone else on the internet (except me) has resolved it using winbind. Example Here

              1 Reply Last reply Reply Quote 0
              • nebulon
                nebulon Staff last edited by

                I don't have any experience with Windows and local DNS names also note that Cloudron uses unbound on the instance as a DNS resolver, not sure how winbind plays with that. If the local IP of that directory server does not change, then you could also add a line for it in the /etc/hosts file

                P 1 Reply Last reply Reply Quote 0
                • P
                  phsc @nebulon last edited by

                  Yes, modifying the hosts file was my last option, which was successful - thanks for your suggestion. Once the hostname was found, I was able to save the configuration. Not sure why I couldn't get overall hostname resolution working, but at the end of the day it wont really matter. I guess this is still a bug, since I assume it should tell the user "server URL not found" and not reboot. Being able to resolve local hostnames out of the box would be great, even if the use case is probably the minority. I did discover that you can just use the IP address for the server URL - I didn't think that this was an option initially because it didn't work for me (because I had other settings wrong). Which leads me onto my next comment - there is very little feedback when you get the settings wrong. When your a top tier noob like me, it takes a lot of trail and error. For example, getting the Base DN wrong leads to the Server URL being highlighted red (even though the server url and credentials are correct). Looking at the log shows that the object wasn't found. For anyone else having issues getting the settings right, my example is below.
                  settings.PNG
                  Thanks @nebulon for your help. 😃

                  1 Reply Last reply Reply Quote 0
                  • nebulon
                    nebulon Staff last edited by

                    The crash is fixed with https://git.cloudron.io/cloudron/box/-/commit/41b03e3fefca5559c6db58a29399d97ae312a4f3 for the next release.

                    1 Reply Last reply Reply Quote 1
                    • Topic has been marked as solved  nebulon nebulon 
                    • First post
                      Last post
                    Powered by NodeBB