Can connect to printer via fluidd.local but not via IP

General Discussion
1

Basic Information:

Printer Model: E3V2
MCU / Printerboard: 4.2.2 stock MB, RPi zero 2 w
klippy.log (25.3 KB)

Describe your issue:

As in title. Klipper worked great for me on my 8GB SD card, but now that i upgraded onto a 32GB card formatted to FAT32 i’m struggling to have the Pi show up via IP. I can connect to klipper using fluiddpi.local but not via IP anymore. This sucks as I need to have the IP work in order to connect via ssh.
When scanning via AngryIP e.g. it says that the previously used IP is no longer in use. no fluidd showing up.
I’m super newbie material so go easy with me!

thanks in advance

2

You don’t need the IP to connect via ssh, at least not from a terminal. As for finding the IP, I know in Mainsail it’s shown in the machine tab as part of the Host information. It’s probably shown somewhere similar in Fluidd.

3

This is very strange and close to impossible since a domain name cannot exist without an IP and the IP is always the first thing a network device needs to obtain. Without it no connection is possible at all.

I recommend:

  1. Shutdown the RPi and wait a bit
  2. Reboot your router
  3. Start the RPi
4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.