You generating 2 different IP’s now. Which is which?
volumio@192.168.1.10
volumio@192.168.1.180
Hey @PluggedIn,
I am watching this thread from the shadows with the quiet reverence of a wildlife documentary narrator. Community members are helping. Unprompted. In the wild. I dare not type too loudly in case the magic dissipates like morning fog on a Scottish loch. My keyboard is clicking impatiently, each key twitching with unsolicited opinions, and I must resist with every fibre of my being because this - this right here - is what a community forum is supposed to look like.
I do need to interject on one thing before I retreat back into the undergrowth, because @Wheaten spotted it and it matters:
You are using two different IP addresses.
- 192.168.1.180 - your Volumio (FileZilla attempt, and everywhere else in this thread)
- 192.168.1.10 - something else entirely (your SSH attempt)
That is why SSH refused the connection. It is not a configuration problem. You are knocking on the wrong door. Fix the IP, and also make sure SSH is enabled first via http://volumio.local/dev - it is disabled by default.
Now if you will excuse me, I need some me time. I have thousands of ideas all pulling on my last remaining grey brain cell, demanding attention like seagulls fighting over a chip. The rest of them melted down years ago - some from staring at logs that were never provided, some from explaining the difference between config.txt and userconfig.txt for the four hundredth time, and one particularly promising cluster simply handed in their resignation after spending six hours on a problem that turned out to be a loose USB cable.
Kind Regards,
1 Like
Well, don’t I feel stupid… although not surprised, my brain have been having these glitches for a few years.
But what I am surprised is that when I read this, I obviously thought “Ok, that was the problem” so I do
ssh volumio@192.168.1.180
and I get:
ssh: connect to host 192.168.1.180 port 22: Connection refused
So now I’m confused. I just confirmed that the IP is still Volumio’s, just in case because it’s set to always have that IP.
Didi you enable ssh in 192.168.1.180/dev ?
if your IP is 192.168.1.180, this command is ok:
ssh volumio@192.168.1.180
You’re an writer, right? With a focus on comedy I would guess?
Oh, gotcha. Now it works.
And now I have to remember what did I need this for.
Hey @PluggedIn,
Not a writer. Not a comedian. Hard core techie. Logic, facts, no speculation. If the results happen to be dramatic, that is because reality is dramatic when you stop decorating it and just describe what is actually happening. A fact delivered with precision is funnier than any joke because it is true and nobody can argue with it. Comedy is just tragedy plus accurate observation minus the social filter most people leave enabled.
Good - SSH works. That was the IP. 192.168.1.180 is your Volumio. 192.168.1.10 is not. Mystery solved. Now you have it in your back pocket for when you actually need it, which - based on your enthusiasm for “under the hood stuff” - about few hours before you are in there poking around voluntarily.
Kind Regards,
Yeah, but I’ve never seen a tech nerd with your writing skills, it’s just not normal. I don’t mean that nerds can’t write at all, but certainly not at your level.
Hey @PluggedIn,
It is not writing skill. It is obsessive clarity.
When you spend decades debugging systems where a single misplaced character causes silent failure, you develop an unhealthy relationship with precision. Every word gets the same treatment as every line of code - does it do what I think it does, does it do anything I did not intend, and can it be misinterpreted by “not a smart person” at 3am. If the answer to the third one is yes, rewrite it.
Most technical writing is bad not because engineers cannot write, but because they tolerate ambiguity in language that they would never tolerate in code. They will spend four hours tracking down a race condition but happily fire off a paragraph that could mean three different things depending on which word you stress. That is not a writing problem. It is a debugging problem applied to the wrong medium.
Good writing is just refactored English. Remove the dead code. Eliminate redundant variables. Make the logic flow in one direction. Stop nesting conditionals seven levels deep when a flat structure will do. If your sentence needs to be read twice to be understood, it has a bug.
The humour is a side effect. When you strip away every unnecessary word and say exactly what is true with no padding, the result is frequently funny because most communication is 70% padding, 20% hedge, and 10% content. Remove the first 90% and what is left tends to hit rather hard.
Kind Regards,
1 Like
Yeah and still you can’t do it in just a one-liner 
2 Likes
Hey @Wheaten,
Fair point. Brevity is a work in progress - much like Volumio since day one.
Kind Regards,
1 Like