Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    Kopano Installation failed on Ubuntu 18.04

    Kopano Groupware Core
    2
    4
    582
    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.
    • nils50122
      nils50122 last edited by

      Hi guys,

      i have a problem with the installation of the kopano-server on my clean installed ubuntu 18.04.

      The installer doesn’t create the *.cfg files in /etc/kopano. So the problem is i can’t start the server. There is also no log file under /var/log/kopano.

      This is the important output from dpkg -i *.deb

      chmod: cannot access '/etc/kopano/server.cfg': No such file or directory
      chown: cannot access '/etc/kopano/server.cfg': No such file or directory
      
      1 Reply Last reply Reply Quote 0
      • fbartels
        fbartels Kopano last edited by

        Hi @nils50122 ,

        this has already been discussed in https://forum.kopano.io/topic/1448/no-config-files-created-during-install

        Regards Felix

        Resources:
        https://kopano.com/blog/how-to-get-kopano/
        https://documentation.kopano.io/
        https://kb.kopano.io/

        Support overview:
        https://kopano.com/support/

        1 Reply Last reply Reply Quote 0
        • nils50122
          nils50122 last edited by nils50122

          Thanks. Now the service state is running.

          But there comes the next problem. I want to create a new admin user but i get the output “too many options given.”

          This is my command (xxx replaced by real values)

          kopano-admin -c xxxxx -p xxxxxx -e admin@xxxx.de -f „xxxxxx“ -a1```
          1 Reply Last reply Reply Quote 0
          • nils50122
            nils50122 last edited by

            Update: solved.

            replace the “xxx” with 'xxx"

            1 Reply Last reply Reply Quote 0
            • First post
              Last post