

We’ve tried talking, we’ve tried percussive maintenance, now it’s time to take things up a notch and let these silly little machines know who’s boss.
Languages: Français, English
Pronouns: They/them
Communities:
We’ve tried talking, we’ve tried percussive maintenance, now it’s time to take things up a notch and let these silly little machines know who’s boss.
Damn, either you were a really smart 13 year old, or you must have been super desperate and then amazed that that actually worked.
I think this might actually be the dumbest. My fear of electricity is one of the main reasons I focus my tech shenanigans on the software side of things rather than the hardware.
This kind of hacky dumb workaround is exactly what I wanted to read when I posted this thread, haha. It’s kind of genius but also I’m horrified to imagine how things got to that point.
That’s not stupid, that’s one of the first steps of any sane troubleshooting.
I can’t say I’ve never been confused by keystrokes from objects laying on my keyboard, but I do usually figure it out within a couple of seconds at most.
I just spent the better part of the day trying to get a “music archival tool” to work, but I wasn’t able to get my Spotify account to connect.
The eventual solution I ended up with was to spin up a Windows VM, get the tool connected to my Spotify account there and copy over the config file from the Windows installation to my (Linux BTW) actual computer.
Of course, I’ve never really dabbled in emulation past old video game consoles, so getting a Windows VM up and running involved its own troubleshooting… The whole thing felt absurd, especially since there are so many easy ways to download music, but this was one of those times where I didn’t want to let the computer best me.
Any ports used in docker will be open on your computer and accessible to any device in your network.
However, to open up a port to the internet, you’d have to do port-forwarding on your router. If you haven’t done that, any incoming connections will just be dropped at the router-level.
That’s actually so cool and the more I think about it the more it’s making me really want to host my own Lemmy instance. Can I ask what sort of hardware resources you’re running it on?
Grocery stores are not billionaires, seeing as they’re not people.
I’m reading it so I’d say it works!
Honestly, you might just have to wait until she’s done with puberty. This just sounds like a typical teenager whose brain is addled with hormones. It’ll die down with time.
They meant pinging your server from another device, I assume.
What error(s) do you get when you try to SSH into your server?
By “can’t access containers”, I assume you mean via devices you’re trying to connect to the server with? Can you still access the stuff you’re running in the containers directly on the server via localhost?
I’ll echo what the other commenter’s have said and you need to give us more info. “I added two containers” is pretty much useless if that’s all we have to go off of to start troubleshooting. More details on what exactly you did, any troubleshooting steps you’ve already tried, what specific errors you get, etc.
I can only assume it’d be a bridge for Nextcloud Talk.
I was having issues getting my Android device to use my local DNS server over VPN, what worked for me was setting it up through RethinkDNS. There’s a setting to prevent DNS leaks by capturing all traffic on port 53 and directing it to the DNS server you set. It doesn’t feel like an elegant solution but hey, it works.
Note, you’ll have to make sure your private DNS setting is off, in the internet section of the system settings.
From a quick Lemmy search, I’ve seen Njalla and 1984.hosting being recommended for these kinds of uses.
I’d rather not open ports I don’t have to. I don’t see why I’d have to open a port when Unbound works on my local network and I have access to my local network via Wireguard. I can access a whole slew of services through that one Wireguard port, why wouldn’t Unbound work?
Thanks anyway for trying to help, bud.
I could do that, but I want to avoid opening ports on my router’s firewall apart from the one necessary for Wireguard. I can access all my other stuff through Wireguard, but I can’t wrap my head around why it seemingly can’t access Unbound on the local host.
The reason for the VPN is to have access to my Unbound DNS on my phone from anywhere, not only my local network. If I just wanted to configure the DNS on my local network, I’d set up static IP for my network in Android’s settings and input the DNS server manually. This works fine when I set it up, but like I said I want to use Unbound on my phone anywhere via Wireguard.
I’m not sure what’s the second thing you want me to clarify! Sorry for the confusion, I appreciate you trying to help out :)
Sticks were maybe the first human technology and we’ve yet to top it to this day.