Skip to main content

Network Connection Troubleshooting

1. My IP address shows up as 0.0.0.0 on the printer's LCD

1.1 Your WiFi information is missing or incorrect

  • Double check your SSID (wifi name) and password.

  • For Raspberry Pi, you'll have to re-image your SD card using Raspberry Pi Imager. In the 'advanced settings' make sure the SSID (WiFi name) and password is correct.

  • For Print Farm Hub, double check the wifi.txt file. Make sure there are no spaces after the colon or at the end of your SSID/password.

    Example wifi.txt:

    Put your wifi information below, it is case sensitive. Type it directly after the colon:like this.

    network-name:ExampleNetworkName password:ExamplePassword

2. I can't find my IP address

2.1 Try using an ethernet connection instead of WiFi

Ethernet is the most reliable way to connect your Pi / Hub to your network. If you have an ethernet cable, try connecting your Pi / Hub to your router directly. If you can access the dashboard with an ethernet connection, then you know the issue is related to Wifi. We strongly recommend using ethernet if possible.

If you need to use WiFi, then make sure your Pi / Hub is close to your router, and double check your Wifi name and password were entered correctly.

2.2 Scan your network to manually find your IP

Download Angry IP Scanner and scan your network to find the IP of your Raspberry Pi / Print Farm Hub (Rock64). IP addresses usually start with 192.168.1.x 10.1.10.x, or 10.0.x.x.

If Angry IP scanner doesn't show anything named rock64 or raspberrypi , then log into your router and you should be able to find the IP address of your Pi / Hub.

Finally, you can try running the command arp -a in the command prompt (Windows) or terminal (Mac/Linux) to find the IP address of your Pi / Hub. It will list out all the devices connected to your network. Check for any devices with a dynamic IP address.

Once you find your IP address, type in https://<YOUR_IP_ADDRESS>:8080 into your browser. For example: https://192.168.1.123:8080. If you see the AutoFarm3D dashboard, then you're good to go!

2.3 Check to see if your Raspberry Pi is underpowered. Ensure your RPi power supply is rated for at least 3 amps

  • If you're using a print farm Hub (Rock64), then you can skip this step.
  • You can tell your Pi is underpowered if it continuously cycles through reboot (flickers rapidly for 5-10s, turns off, and repeats the flicker).
  • If your power supply cannot supply at least 3 amps, then performance can be unstable. Your Pi may appear to work fine with a 2 amp supply, but under heavy load, it will require more power. Invest in a high-quality 3 amp power supply to avoid future headaches.

2.4 Ensure the RPI is booting properly

You can check the green LED lights on the RPi near the power cable. You will be able to see a red solid light at all times, and a green one that may flicker.

  • When SD not read properly, solid green for 15s, blink 4 times, solid green again
  • When no SD card/ not pushed in all the way, it will blink green, then solid green
  • Good SD card, flickers green rapidly on boot, occasional flicker of green after (no solid green at all)
  • If your SD card is corrupt, it will blink green 8 times.
  • Solid red + no green at all: Turn off all 3D printers connected to the Pi. Turn off the Pi. Wait 10 seconds. Turn on the Pi. Turn on the 3D printers.
  • Tried everything and still not working? Re-image your SD card following the instructions in the Raspberry Pi Setup Guide.

3. I found my IP, but AutoFarm3D does not load when trying to access (IP):8080

It can take a minute or two for AutoFarm3D to boot, especially for the first time. Wait 5-10 minutes and try again. Try accessing <IP>:3030 instead of <IP>:8080. E.g.: 192.168.1.123:8080 This will show you the debug page where you will be able to contact us and send logs so we can help you troubleshoot.

3.1 Update timezone

If your printer LCD displays an IP, but the UI does not display when you are trying to access, it may be that the timezone of your RPi / Hub is incorrect.

  1. Open the command prompt/ terminal of your computer.
  2. 2 For Raspberry Pi, type ssh pi@<your_ip> (eg. ssh [email protected]).
  3. For Print Farm Hub, type ssh rock64@<your_ip> (eg. ssh [email protected]).
  4. Type in yes to connect.
  5. Enter 3dque for your password.
  6. Type in date and check to see if your date matches your local time.
  7. If it does not, type in sudo raspi-config
  8. ‍Navigate down to 'Localization Options'
  9. Go to ‘Change Time Zone' and select your region followed by your city.
  10. Once that has been completed, use your left and right arrows to head back and finish.
  11. You should see on your command prompt/terminal that it has updated to the correct time zone.
  12. Once completed, try accessing the UI once again on your local browser.

3.2 Check for firewalls

Check to see if your network has a firewall that prevents you from accessing the RPI remotely.

  • Look in your router settings for either “Wifi Isolation” or “Network Isolation”.
  • It’s often enabled to prevent wifi devices from seeing each other or from wifi devices accessing the rest of the local network.
  • It will likely be under Wireless > Advanced Settings, it will need to be disabled.
  • You may have to contact your internet service provider to help with configuring settings for your router.

Corporate networks commonly have firewalls in place. Contact 3DQue for help if you need help with network setup on a corporate network.

4. I connected my printer to the Pi / Hub, but it's not showing up in the dashboard

4.1 Check if your printer is detected by the Pi / Hub

  • Go to <IP>:3030 the software center of the Hub that your printer is plugged into.
    • E.g. 192.168.1.123:3030
    • If you don't know the IP of your hub, you can find it by following these steps.
  • Scroll down and check to see if your printer is shown in the list under Devices & Ports.
  • If no devices are shown, or the only entry is "Unrecognized device", then there is a USB connection issue.
    • Please note that AutoFarm3D is not compatible with printers running Klipper or Duet/RepRap firmware.

4.2 USB Connection Issue: Check the USB cable connecting your printer to your Pi / Hub

  • Make sure it is plugged in on the Pi/Hub side, as well as the printer side.
  • Make sure it supports data transfer. Some cables are only for charging.
  • Make sure the cable isn't broken.
  • If in doubt, try a different USB cable. The cable that came with your printer should work.

4.3 Printer shows up on the Hub Configuration Center (IP:3030) but not on the main dashboard (IP:8080)

  • If your Hub is in Worker mode, then you will need to connect to your Command Hub's dashboard <Command Hub IP>:8080 to see the dashboard.
  • Try doing a hard refresh on your browser. Hold "ctrl" and click the refresh button on your browser.
  • Try rebooting your hub. Click on the Reboot button under the Quick Controls section of the Hub Configuration Center.

5. I can access the dashboard for a while, but then it freezes or stops working

  • Use an IP scanner, such as, Angry IP Scanner or log in to your router to check if your router is changing your Raspberry Pi / Print Farm Hub's IP address.
  • To solve this issue, you will have to set a static IP for your RPi / Hub. This varies from router to router, so you may need to look up directions on how to do so.

6. The IP address shows up as 127.0.0.x

You may have set a static IP for your RPi or Print Farm Hub, but something else is connected to that IP address.

  • Use an IP scanner, such as, Angry IP Scanner or log in to your router to check if something else is taking that IP address.
  • If so, set a different static IP for your Pi / Hub.

7. Prints stop halfway through for no reason. Connection to the printer is unstable

This can be for a variety of reasons. Please go through the following checklist. The solutions near the top of the list are most likely to be the cause of the instability.

  • Make sure your Raspberry Pi power supply is rated for at least 3 amps.
  • Make sure the SD card in your Pi / Hub is at least 16GB, and rated as 'Class 10'.
  • Make sure the SD card is from a reliable brand. Sandisk is the only brand we recommend using.
  • Make sure your Raspberry Pi / Print Farm Hub is plugged into a power outlet with a stable power supply. If you're running a high-power appliance on the same circuit (e.g. refrigerator, AC, toaster, kettle, microwave, multiple 3D printers heating up at the same time) this can cause a momentary dip in power, which can interrupt the power to the Raspberry Pi or Print Farm Hub, causing instability issues.
  • Your printer is running a really old version of Marlin firmware. Update to Marlin 2 as it fixes many USB communication stability issues.
  • Your printer firmware occasionally sends malformed responses to gcode commands. This is usually fixed by reflashing firmware.
  • The USB cable connecting your Pi / Hub to your printer may have a loose connection. Try a new USB cable.
  • The USB port on your 3D printer might be broken / loose. You may need a new motherboard. (or you can try re-soldering the USB port if you have the skills & equipment for it)
  • Your SD card may be corrupted. Re-flash AutoFarm3D onto your SD card. If the issue persists, try a new SD card (16 GB, Class 10, Reliable brand).
  • "Just turn it off and on again". Reboot your Pi / Print Farm Hub.

8. Temperatures of the printer show at the wrong temperature. The printer doesn't wipe when it cools down

Some people report that the temperature displayed in the browser is different than the temperature displayed on the printer LCD. There can be a few reasons for this.

  1. Communication between the printer and Pi / Hub got interrupted. Please see troubleshooting section 8 above.

  2. Some Creality printers have a bug in the firmware where temperatures are not displayed properly. If you go to the gcode console, and the temperature looks like this:

    tt::25.9125.91 //0.000.00 bb::33.7533.75 //0.000.00 @@::00 bb@@::00\n\n

Then your machine is affected with the firmware bug. Your temperatures should look like this:

t:19.63 /0.00 b:19.47 /0.00 @:0 b@:0\n

The solution for this bug is to update your printer's firmware to the latest version of Marlin.