Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Problem with Start page

    Scheduled Pinned Locked Moved Unsolved
    Duet Web Control
    3
    7
    372
    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.
    • JBiscundefined
      JBisc
      last edited by JBisc

      Hey guys,

      since 3.2 i got a strange problem with DWC. The "website" is not accessable.
      The RPI4 is in my network and accessible via SSH.
      If i try to access over DNS (e.g. http://duet3/) or directly over the IP address the Apache server on the RPI is showing me the following message.

      alt text

      pi@duet3:~ $ sudo journalctl -u duetcontrolserver -f
      -- Logs begin at Tue 2021-01-12 13:17:01 GMT. --
      Jan 12 13:26:51 duet3 DuetControlServer[427]: Written by Christian Hammacher for Duet3D
      Jan 12 13:26:51 duet3 DuetControlServer[427]: Licensed under the terms of the GNU Public License Version 3
      Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] Settings loaded
      Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] Environment initialized
      Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] Connection to Duet established
      Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] IPC socket created at /var/run/dsf/dcs.sock
      Jan 12 13:26:52 duet3 systemd[1]: Started Duet Control Server.
      Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] Starting macro file config.g on channel Trigger
      Jan 12 13:26:53 duet3 DuetControlServer[427]: [info] Finished macro file config.g
      Jan 12 13:29:57 duet3 DuetControlServer[427]: [info] System time has been changed
      
      

      Setup

      RPI4 via USB and ribbon cable connected to Duet3_MB6HC

      hostname: duet3
      browser: chrome

      Software:

      pi@duet3:~ $ apt list 2>/dev/null | grep duet
      duetcontrolserver/stable,now 3.2.0 armhf [installed]
      duetruntime/stable,now 3.2.0 armhf [installed]
      duetsd/stable,now 1.1.0 all [installed]
      duetsoftwareframework/stable,now 3.2.0 armhf [installed]
      duettools/stable,now 3.2.0 armhf [installed]
      duetwebcontrol/stable,now 3.2.0 all [installed]
      duetwebserver/stable,now 3.2.0 armhf [installed]
      

      Any Ideas?

      My Setup: Duet 3 MB6HC Main Board with attached RPI

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        I would start with a fresh image of duet pi and then update with sudo apt update, etc

        https://pkg.duet3d.com/DuetPi-lite.zip

        https://pkg.duet3d.com/DuetPi.zip

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 1
        • JBiscundefined
          JBisc
          last edited by JBisc

          Thanks for the hint. I have done a reinstall with a new SD-card - it worked

          My Setup: Duet 3 MB6HC Main Board with attached RPI

          1 Reply Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator
            last edited by

            Oh it worked now? what changed?

            Z-Bot CoreXY Build | Thingiverse Profile

            JBiscundefined 1 Reply Last reply Reply Quote 1
            • JBiscundefined
              JBisc @Phaedrux
              last edited by JBisc

              @Phaedrux I thought that it helped to reinstall everything. First everthing worked well, but after configuring my RPI in the way I typically use it, i got the same problem again.

              But I was able to find the point where something is going wrong.

              What I have done:

              Completly new image on SD card (v3.2). Everything worked correctly: DWS webpage is shown correctly in my network.

              I want to run another Singlepage-Application an the RPI therefor I install nodejs with the following command

              sudo apt-get install -y nodejs npm
              

              and after finishing the installation, something is wrong with the Appache-Server (?).

              Results:
              And I get my old error message: "Apache2 default message"

              Question:
              Is there an Apache expert who has an idea?
              How is it possible that the installation of nodejs is changing something that leads to my problem with the Apache?

              My Setup: Duet 3 MB6HC Main Board with attached RPI

              chrishammundefined 1 Reply Last reply Reply Quote 1
              • chrishammundefined
                chrishamm administrators @JBisc
                last edited by

                @JBisc Something must be pulling apache2 in as a dependency. That isn't a problem as long as it isn't started or at least configured for a different port. Try running

                sudo systemctl stop apache2.service
                sudo systemctl disable apache2.service
                sudo systemctl restart duetwebserver
                

                if you don't use apache with npm. If you do, either configure DWS or Apache for a different port. The corresponding DWS config is /opt/dsf/conf/http.json.

                Duet software engineer

                JBiscundefined 1 Reply Last reply Reply Quote 1
                • JBiscundefined
                  JBisc @chrishamm
                  last edited by

                  @chrishamm Thanks I will try that!

                  My Setup: Duet 3 MB6HC Main Board with attached RPI

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Unless otherwise noted, all forum content is licensed under CC-BY-SA