ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Unable to turn up ScreenConnect server on Fedora 28

    Scheduled Pinned Locked Moved Solved IT Discussion
    screenconnectinstallfedora28
    16 Posts 6 Posters 1.9k Views
    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.
    • JaredBuschJ
      JaredBusch @hobbit666
      last edited by

      @hobbit666 said in Unable to turn up ScreenConnect server on Fedora 28:

      Strange, I've got it running on a Fedora 28 machine.

      Give me 10 or so and i'll try and dig out my instructions I made while installing it.

      I had no issues on CentOS 7 previously.

      I did not expect any issues here.

      Haven't had troubleshooting time yet.

      I installed Fedora 28 minimal. installed tar and wget. Disabled selinux. Ran the installer and had problems.

      So I installed Fedora 28 Server. Same result on install. no packages needed installed though.

      I'm visiting my dad, so I'll do more troublshooting tonight or tomorrow.

      1 Reply Last reply Reply Quote 0
      • hobbit666H
        hobbit666
        last edited by

        Just had a look and looks like I didn't do a "install guide" for ScreenConnect when I re-did all my Linux servers on HyperV host 😞

        I think I had some issues but I think the solutions were on the ConnectWise Forums.

        1 Reply Last reply Reply Quote 0
        • dbeatoD
          dbeato
          last edited by

          Apparently is an issue with the Mono package as below:
          https://github.com/mono/mono/issues/6752

          1 Reply Last reply Reply Quote 2
          • RomoR
            Romo
            last edited by

            @jaredbusch said in Unable to turn up ScreenConnect server on Fedora 28:

            System.Exception: Magic number is wrong: 542

            Searching for the error leads to a mono bug https://github.com/mono/mono/issues/6752#issuecomment-365212655

            Which supposedly you can get working by exporting an enviromental variable

            export TERM=xterm
            

            According to the last comment on the thread https://github.com/mono/mono/issues/6752#issuecomment-404527450 the issue fix should already be backported on fedora which makes it strange as the error is happening on fedora 28 for jared.

            JaredBuschJ 1 Reply Last reply Reply Quote 4
            • JaredBuschJ
              JaredBusch @Romo
              last edited by JaredBusch

              @romo said in Unable to turn up ScreenConnect server on Fedora 28:

              export TERM=xterm

              This did resolve my problem. Sorry for not posting sooner.

              @romo said in Unable to turn up ScreenConnect server on Fedora 28:

              According to the last comment on the thread https://github.com/mono/mono/issues/6752#issuecomment-404527450 the issue fix should already be backported on fedora which makes it strange as the error is happening on fedora 28 for jared.

              The comment said it was backported by Fedora, but I saw no links, just the comment saying it was backported.

              @scottalanmiller tag his post as the answer.

              1 Reply Last reply Reply Quote 0
              • JaredBuschJ
                JaredBusch
                last edited by

                Once it was working with the above fix, I hadn'thad time to take our systemdown and move it.

                Just did that today. Working perfectly.

                1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller
                  last edited by

                  Answer marked.

                  1 Reply Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch
                    last edited by

                    Just went to upgrade the install today to the current version and had this error again.

                    Again, setting up the TERM variable prior to running ./install.sh resolved the issue.

                    1 Reply Last reply Reply Quote 1
                    • JaredBuschJ
                      JaredBusch
                      last edited by

                      Still an issue with ScreenConnect 19.1

                      1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller
                        last edited by

                        Recently posted this...

                        https://mangolassi.it/topic/20124/has-anyone-got-a-guide-to-installing-screenconnect-on-fedora-30-with-let-s-encrypt/

                        So anyone that wants to configure Nginx in front of it can do that, too.

                        1 Reply Last reply Reply Quote 2
                        • 1 / 1
                        • First post
                          Last post