If a controller is still connected (Bluetooth?) it may be a controller order issue, you can try reordering them.
ostsjoe
joined 1 year ago
No, the browser would still send YouTube.com as the host header. While yewtu.be could be configured to allow this to work, the TLS cert would not and the browser would get upset.
Also the alternator absolutely takes more power from the engine in proportion to how much energy it's putting out.
Jellyfin is very conveniently packaged in docker, so while it may seem daunting, I highly recommend at least trying that route.
Running an nfs mount, docker or not, should be perfectly fine. Jellyfin just uses normal storage so won't care if it's nfs. No real special considerations with proxmox either, especially without worrying about a dedicated GPU. Just spin up a Debian guest and go.
Fortunately that's not how it works when you have all the access points controlled centrally, like with unifi. Yes there is limited frequency space, but this is much less of an issue on 5ghz. There will also only be one ssid, and handoff between access points is pretty seamless.
3-4 is probably overkill, but the attenuation situation sounded pretty dire. I run two in my house for redundancy mostly, just standard American stud and drywall construction.
If you have the ability to easily add wires, I would go with a system that allows you to wire everything together, rather than depending on a purely wifi mesh. Personally I'm running unifi ceiling mounted access points for this. They run on power over Ethernet, so you just need to get one cable to each. You can control them with their free software controller if you are into that, or something like their dream router.
Run 3-4 of those access points placed throughout the house and you'll never have a weak signal again.
Sand, sand, and sand some more. When you think you are done sanding, sand some more.
If you have a free pcie 4x or higher slot, you can throw in a cheap card to adapt to m.2 nvme, like 12 bucks. I'm running one in my older hp desktop that doesn't have m.2 and it's been working great.
For a quick test you could set it to 777, if that fixes it, check which user new files are being assigned to, adjust permissions back down accordingly.
We need more info on your permissions. 755 would mean anyone can read files there, but only the owner can write. If the owner isn't the same user that mediawiki is running as, then uploads won't work.
I have no way to test this with the equipment I have, but what about opnsense on an x86-64 box and throw an sfp+ pcie card in there. You could then in theory turn off auto negotiation and set it to 2.5g. Has anyone out there tried this?
I've been running opnsense with my CenturyLink 1g setup, though I'm still using their ont to convert to copper, and been very happy with it.
view more: next ›
Try booting something different on proxmox like an ubuntu live desktop, just to make sure networking is working there. Seems like haos can't talk to the Internet.