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.8k 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.
    • J
      JaredBusch
      last edited by

      The instructions for spinning up ScreenCOnnect on "Linux" are simplistic.

      https://docs.connectwise.com/ConnectWise_Control_Documentation/On-premises/Get_started_with_ConnectWise_Control_On-Premise/Install_ConnectWise_Control_On-Premise/Install_ConnectWise_Control_On-Premise_on_Linux

      But my problem is that it does not work on Fedora 28.

      Is there some missing hidden dependency? I installed this on CentOS 7 years ago and it runs mostly fine.

      wget -O sc.tar.gz "https://www.screenconnect.com/Download?Action=DownloadLatest&Platform=Linux&PreRelease=false"
setenforce 0
tar xzf sc.tar.gz
ScreenConnect_6.7.19388.6796_Install/install.sh

      Results in this

      unning 'Create service script at /etc/init.d/screenconnect'...
Running 'Create startup links in /etc/rcX.d/ directories'...
Running 'Copy files into /opt/screenconnect'...
Running 'Transform configuration files'...

Unhandled Exception:
System.TypeInitializationException: An exception was thrown by the type initializer for System.Console ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.ConsoleDriver ---> System.Exception: Magic number is wrong: 542
  at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00000] in <filename unknown>:0 
  at System.TermInfoReader..ctor (System.String term, System.String filename) [0x00000] in <filename unknown>:0 
  at System.TermInfoDriver..ctor (System.String term) [0x00000] in <filename unknown>:0 
  at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <filename unknown>:0 
  at System.ConsoleDriver..cctor () [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00000] in <filename unknown>:0 
  at System.Console..cctor () [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at Mono.Xml.XPath.XPathParser..ctor (IStaticXsltContext context) [0x00000] in <filename unknown>:0 
  at Mono.Xml.Xsl.Compiler.Compile (System.Xml.XPath.XPathNavigator nav, System.Xml.XmlResolver res, System.Security.Policy.Evidence evidence) [0x00000] in <filename unknown>:0 
  at System.Xml.Xsl.XslCompiledTransform.Load (System.Xml.XPath.XPathNavigator stylesheet, System.Xml.Xsl.XsltSettings settings, System.Xml.XmlResolver stylesheetResolver) [0x00000] in <filename unknown>:0 
  at System.Xml.Xsl.XslCompiledTransform.Load (System.String stylesheetUri, System.Xml.Xsl.XsltSettings settings, System.Xml.XmlResolver stylesheetResolver) [0x00000] in <filename unknown>:0 
  at Xsl.Program.Main (System.String[] args) [0x00000] in <filename unknown>:0 
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for System.Console ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.ConsoleDriver ---> System.Exception: Magic number is wrong: 542
  at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00000] in <filename unknown>:0 
  at System.TermInfoReader..ctor (System.String term, System.String filename) [0x00000] in <filename unknown>:0 
  at System.TermInfoDriver..ctor (System.String term) [0x00000] in <filename unknown>:0 
  at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <filename unknown>:0 
  at System.ConsoleDriver..cctor () [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00000] in <filename unknown>:0 
  at System.Console..cctor () [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at Mono.Xml.XPath.XPathParser..ctor (IStaticXsltContext context) [0x00000] in <filename unknown>:0 
  at Mono.Xml.Xsl.Compiler.Compile (System.Xml.XPath.XPathNavigator nav, System.Xml.XmlResolver res, System.Security.Policy.Evidence evidence) [0x00000] in <filename unknown>:0 
  at System.Xml.Xsl.XslCompiledTransform.Load (System.Xml.XPath.XPathNavigator stylesheet, System.Xml.Xsl.XsltSettings settings, System.Xml.XmlResolver stylesheetResolver) [0x00000] in <filename unknown>:0 
  at System.Xml.Xsl.XslCompiledTransform.Load (System.String stylesheetUri, System.Xml.Xsl.XsltSettings settings, System.Xml.XmlResolver stylesheetResolver) [0x00000] in <filename unknown>:0 
  at Xsl.Program.Main (System.String[] args) [0x00000] in <filename unknown>:0 

Unhandled Exception:
System.TypeInitializationException: An exception was thrown by the type initializer for System.Console ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.ConsoleDriver ---> System.Exception: Magic number is wrong: 542
  at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00000] in <filename unknown>:0 
  at System.TermInfoReader..ctor (System.String term, System.String filename) [0x00000] in <filename unknown>:0 
  at System.TermInfoDriver..ctor (System.String term) [0x00000] in <filename unknown>:0 
  at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <filename unknown>:0 
  at System.ConsoleDriver..cctor () [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00000] in <filename unknown>:0 
  at System.Console..cctor () [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at Mono.Xml.XPath.XPathParser..ctor (IStaticXsltContext context) [0x00000] in <filename unknown>:0 
  at Mono.Xml.Xsl.Compiler.Compile (System.Xml.XPath.XPathNavigator nav, System.Xml.XmlResolver res, System.Security.Policy.Evidence evidence) [0x00000] in <filename unknown>:0 
  at System.Xml.Xsl.XslCompiledTransform.Load (System.Xml.XPath.XPathNavigator stylesheet, System.Xml.Xsl.XsltSettings settings, System.Xml.XmlResolver stylesheetResolver) [0x00000] in <filename unknown>:0 
  at System.Xml.Xsl.XslCompiledTransform.Load (System.String stylesheetUri, System.Xml.Xsl.XsltSettings settings, System.Xml.XmlResolver stylesheetResolver) [0x00000] in <filename unknown>:0 
  at Xsl.Program.Main (System.String[] args) [0x00000] in <filename unknown>:0 
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for System.Console ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.ConsoleDriver ---> System.Exception: Magic number is wrong: 542
  at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00000] in <filename unknown>:0 
  at System.TermInfoReader..ctor (System.String term, System.String filename) [0x00000] in <filename unknown>:0 
  at System.TermInfoDriver..ctor (System.String term) [0x00000] in <filename unknown>:0 
  at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <filename unknown>:0 
  at System.ConsoleDriver..cctor () [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00000] in <filename unknown>:0 
  at System.Console..cctor () [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at Mono.Xml.XPath.XPathParser..ctor (IStaticXsltContext context) [0x00000] in <filename unknown>:0 
  at Mono.Xml.Xsl.Compiler.Compile (System.Xml.XPath.XPathNavigator nav, System.Xml.XmlResolver res, System.Security.Policy.Evidence evidence) [0x00000] in <filename unknown>:0 
  at System.Xml.Xsl.XslCompiledTransform.Load (System.Xml.XPath.XPathNavigator stylesheet, System.Xml.Xsl.XsltSettings settings, System.Xml.XmlResolver stylesheetResolver) [0x00000] in <filename unknown>:0 
  at System.Xml.Xsl.XslCompiledTransform.Load (System.String stylesheetUri, System.Xml.Xsl.XsltSettings settings, System.Xml.XmlResolver stylesheetResolver) [0x00000] in <filename unknown>:0 
  at Xsl.Program.Main (System.String[] args) [0x00000] in <filename unknown>:0

      Yet, it still says this, but the setup wozard page does not load.

      Running 'Start screenconnect service'...

Installation complete!

Trying to figure out the best URL for you to use...

To access your new ScreenConnect installation, open a browser and navigate to:
http://localhost:8040/Host
      1 Reply Last reply Reply Quote 0
      • R
        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.

        J 1 Reply Last reply Reply Quote 4
        • J
          JaredBusch
          last edited by JaredBusch

          Yes, I opened port 8040 on the firewall.

          [jbusch@sc ~]$ firewall-cmd --add-port=8040/tcp --permanent
success
[jbusch@sc ~]$ firewall-cmd --reload
success
          1 Reply Last reply Reply Quote 0
          • B
            black3dynamite
            last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • B
              black3dynamite
              last edited by

              The installer depends on zlib.
              I found it in the redhat.sh file, located in ScreenConnect_6.7.19388.6796_Install/Installer/Distributions/ directory

              J 1 Reply Last reply Reply Quote 0
              • J
                JaredBusch @black3dynamite
                last edited by

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

                The installer depends on zlib.
                I found it in the redhat.sh file, located in ScreenConnect_6.7.19388.6796_Install/Installer/Distributions/ directory

                zlib is already installed, so that is not it.

                1 Reply Last reply Reply Quote 1
                • H
                  hobbit666
                  last edited by

                  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.

                  J 1 Reply Last reply Reply Quote 0
                  • J
                    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
                    • H
                      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
                        • R
                          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.

                          J 1 Reply Last reply Reply Quote 4
                          • J
                            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
                            • J
                              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
                                • J
                                  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
                                  • J
                                    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