Uhh, this might be true for WebRTC, except not much uses WebRTC other than for realtime streaming/calling. Jellyfin for example is just an mp4 stream over http; and http(s) will only use the IP in the DNS record. I’d like to see a packet capture if you are certain something is switching IP.
I’m pretty sure QWERTY telegraph keyboards post-date typewriters.
Yeah they do! Actually a Japanese research paper (and this video) also theorises that they also grouped similar sounding letters in American Morse Code together (e.g. Z ∙ ∙ ∙ ∙ & SE ∙ ∙ ∙ ∙, or C ∙ ∙ ∙ & S ∙ ∙ ∙)
Yeah, YunoHost explains why http://localhost:8536/ wouldn’t be working. If cloudflared and Lemmy are in separate containers you have to put an actual IP in, since localhost points to the container itself.
How are you accessing it without Cloudflare? How do you know that Lemmy is actually listening?
What’s the URL you using to access it without Cloudflare?
Edit: Also that curl tells me it’s not listening on that IP/port.
Can you access it without Cloudflare?
Does curl http://localhost:8536/ work?
You are using cloudflared right? Because normal (non-cloudflared) Cloudflare doesn’t support port 8536.
With dynamic DNS? Yeah it always has, as long as you can host a http server.
With a dynamic IP? It should do, the certs are only valid for 6 days for that reason.
I know this seems pretty much solved, but I just wanted to point out:
Frigate doesn’t need a TPU, OpenVINO is quite performant even on decade old Haswells, or if you’ve got a GTX 750 or higher you might be able to use that as well.
No it’s real! I can’t verify the exact rating since it OL’s my meter, but with some circuitry it can power my Pi for a few minutes. I got them from element14, so it’s unlikely to be a fake product.
You can host a page with an iframe, but you can’t directly change the DNS record to point to something that isn’t GitHub.
Guys you’re not gonna believe this:
I think they were trying to say that the cage in front with the AP behind, acts as a directional antenna. Similar to how Yagi antennas have metal elements that aren’t connected in front of the actual antenna.
But I don’t know enough antenna theory to know if that’s correct.
Thanks TIL! Although I prefer this diagram that has all the wifi channels on it, instead of just the 3 common ones.
Perhaps there was an easier lighter-weight way of doing this?
Yeah, SSH tunneling. What I would do (and have done in the past) is something like:
ssh -L 8080:192.168.0.1:80 myserver
That will forward port 8080 on your host to port 80 on 192.168.0.1, so you can access your router’s web UI with http://localhost:8080/ in your own web browser.
You can also setup full tunneling with SSH, but that requires messing around with SOCKS and I usually can’t be bothered.
You can always install activate-linux, and it even works on Windows.
Ahh sorry, I thought you meant you plugged it into the input side. If that’s the case then are you running anything that measures CPU usage? I run the TIG stack, it might be able to give you some hits. Also back to my original point which is already unlikely, if it’s a modified sinewave UPS, it can confuse some measuring devices while it’s on battery.
It’s weird to do this daily, but it’s possible that the UPS is doing a self test, which would drain the battery a little and the load is from charging it back up.
I never mentioned vulnerabilities, I just wanted to point out that, RDP doesn’t really work without a graphical session, Windows Server Core gets around this by being a graphical session (although very basic).
Also I’m not sure, but I don’t think Windows handles RDP on the kernel level, it’s just nicely tied in with DWM and doesn’t have to deal with the multitude of window managers on Linux.
Handling RDP on the kernel level does sound like a bad idea security wise, but there should be a better way.
Windows Server Core still has a window manager, just all it does show a command prompt very similar to the one in the usual Windows recovery environment.
Cert pinning is pretty uncommon in the self hosting community though, especially when both Cloudflare and Let’s Encrypt have a 90 day validity period and often renews after 60 days.