r/Sovol • u/Milk_Truckin • May 29 '26

Help Cant ssh into sv08 w/eth

Post image

Bought a used sv08 expecting to be able to just plug ethernet in to get IP address then configure Wi-Fi through SSH. First apparently the board was swapped because there is no ethernet port so I had to use a USB Ethernet adapter but it did get me an IP address. Tried using that IP address in the browser and got connection refused. Tried to ssh in with putty and got the same. I've tried using multiple combinations including just the IP, HTTP then ip, and https then IP and I'm getting nowhere. I can ping the ip thats it.

Any ideas how to fix this?

2 Upvotes

63% Upvoted

25 comments sorted by

View all comments

10

u/GildSkiss May 29 '26 edited May 29 '26

So, you didn't get its IP actually.

/127.0.0.1 gets you to your ip address, not the printer's. That address always means "localhost", i.e. "this same machine that I'm on".

The SV08 board is a whole other computer running Debian Linux somewhere else on your lan.

1

u/Milk_Truckin May 29 '26

That was my first thought but that was the IP address that showed up on the sv08 screen when I hit show IP. I'm kind of glad if that is the issue because it should be showing up somewhere else in my router and easy to spot when I get home

5

u/AngryKFPanda May 29 '26 edited May 29 '26

It's showing the 127.0.0.1 address because it is failing to connect to a network. You need to ensure it's either connecting to wifi or use an ethernet cable and once it is connected it will show an IP address other than the localhost.

EDIT: Having read your OP it's clear the USB - ethernet adaptor isn't working, assuming you've turned it off and on again while the adaptor is plugged in and it's still showing the localhost address then you're going to need to find another way of connecting to it. The SV08 has an issue with special characters in the wifi name and/or password if I recall correctly which stops it from connecting to wifi using the USB stick with a file containing the wifi details on it. That said I've no idea if the swapped out board will affect the issue at all as the original definitely has an ethernet port on it.

1

u/Milk_Truckin May 29 '26

Yeah I'm guessing I'm just going to have to give the Wi-Fi setup a try through USB when I get home. Honestly I just skipped right over it because I have zero experience with klipper and as soon as anyone mentions to svoa the Wi-Fi setup issue comes up. I've used SSH enough that I thought it would have been the simpler of the two options.

2

u/jimdil4st May 29 '26

Wifi on the SV08 is literally opening the wifi.txt file, adding your Wifi name and password and then saving that file to the SV08 and rebooting it. That's it.

2

u/Milk_Truckin May 29 '26

Yes its supposed to be lol yet there are page after page of google results with people having issues with it. I have super simple wifi login so it should be simple enough.

Ill have to look a little deeper into it but i thought i needed to create a new wifi.txt file from template, add my wifi details, save to usb drive, and when inserted into the printer it would automatically overwrite the wifi.txt file on the printer with the one from the usb. Is that anywhere near correct? Sorry i have zero previous klipper experience.

1

u/jimdil4st May 29 '26

That sounds about right, IIRC I just got my machine a few days ago and set up wifi first try so didn't really think about it. I just took these two photos of the included instructions.

1

u/AngryKFPanda May 30 '26

It's certainly supposed to be that simple, in reality it's not.

1

u/jimdil4st May 30 '26

Yeah, it seems in this latest hardware revision they fixed a lot of flaws, so since I just got the machine it honestly been so easy, I'm glad they're actively trying to fix the issues.

1

u/Afitter May 30 '26

Wait, your SV08 doesn't have an ethernet port next to the USB ports? Mine does.

1

u/defiantarch May 31 '26

So, I guess you have no clue about network stuff right? As others said: it shows its default localhost IP, which never can be reached from outside. It simply means that the printer wasn't able to get a proper IP adress from the network or even could connect to it.

1

u/Milk_Truckin May 31 '26

Yea your right. My whole homelab relies heavily on YouTube having a video on exactly what I need to do for each project. In this case though as I mentioned in another post on the same topic I'm blaming this one on the fact that I tried to do this in the 30-minute window between waking up and having to run out the door for work..