joplin

I have an arc for transcoding, and I had to set the device to /dev/dri without the renderD128 part. If I were you, I would just use the 2060. If it’s there for llama or something I’d still try it and see how it does doing both at once, as it should be separate parts of the gpu handling that.

Yeah, I like it too. My only issue is ollama’s lack of intel support. I have been looking at issue 1590 on their GitHub. For now I have a 1050ti in a cardboard box PC with other hardware being 10+ years old and a mixed set of RAM totalling 12G. It also has a 100Mbit nic, so I can’t take advantage of full internet speed when downloading models. The worst part is they can support intel, but haven’t merged the solution because of an issue with the windows intel drivers. Linux is fine but I can 't have it. I wasn’t planning to rant, but I already typed it so… enjoy?

But it isn’t. It sends me an nginx error. The nginx is on that server, so that server isn’t completely down.

So then… maybe try being direct with your answer.

I don’t think it is a hardware issue. I have decent hardware that’s fairly new. I unfortunately can’t say much, though another commenter let me know the SSH failure message is relevant. It see connection closed, which means that it is probably failing to boot. I think an update or something may have broken it, though it is debian stable, so Idk. I’m going to try to call my sister and see if I can get a picture of an error message or something.

It says connection closed. There is no message beyond that. I think it is likely that it is failing to boot. I might video call my sister and have her try to boot it so I can see any errors.

Edit: Also, thanks very much for your response. It was very detailed and informative.

Proxy is on the same machine though. I just use it for subdomains and rate limiting.

Yeah, I would think docker is broken, but that wouldn’t explain the SSH, which is bare metal and doesn’t go through nginx.

It has a network connection, I am able to get to the nginx error, the services themselves are down. What’s really weird is everything is down, even SSH.

My sister is there, but I can’t do much diagnosis. It is weird that SSH would go down with it though, so I thought someone might have an idea.

I know it’s bad gateway. I just don’t know what caused it, or why it happened when SSH went down. Thanks, though.

I use nginx for reverse proxy. You can get certbot working to automate ssl fairly easily. There is a learning curve, but most services I use have documentation for hosting their stuff with it.

You can do that with pihole and basically any reverse proxy. The process is the same, so you can follow tutorials, you just have to set up your domain through your pihole instance instead of a registrar. You can set pihole as your dns for specific devices, or you can set it as the default dns for your network through the router.

Cool, thanks.

Did you have to use a display to flash? Some of them don’t seem to have a display output and I don’t know if that will be an issue. The apple thing concerns me. There are a few macs and iPhones on the network, but the macs are m1, and the oldest iphone would be a 12. Do you think that would be an issue? Also, which R3 router are you using specifically?

They said they want a local backup so they don’t have to redownload because bandwidth is expensive. I think a RAID makes more sense. I also don’t think btrfs is a great idea for a boat. Power failures will probably be somewhat common, and btrfs is not the most stable, so I don’t think I would trust it in weird conditions. Documentation is definitely a great idea though.

For hardware, I would go with sata ssds for storage. I also would recommend a separate boot drive as it makes re installing without loosing data a breeze. You could go with a new processor from intel or amd, and make sure it has onboard graphics. You should also go into the BIOS, enable xmp (always do that. It’s free performance), and look for power saving settings. You could go for arm, but most arm computers lack expansion options and that can mean you use USB for drives which is unreliable. I think dc atx power supplies are a thing, but I know nothing about them. I would recommend doing ext4 and a raid, ideally 6 or 10. That will give you stability (from filesystem issues) and good reliability. I know RAID is not a backup, but in this case it may be what you want. RAID is for uptime, and it would be able to usually buy you enough time to finish your trip, or you could even have spare drives onboard and fix it while you’re out in like 10 minutes. Also, I would highly recommend researching how to power it well. Starting an engine can mess with the power and could fry a computer. I don’t know if a dc ups is a thing, but if it is, get it.

For software, use whatever you want, mostly. I always use debian for servers, but proxmox would probably be fine. You can use powertop to make sure it runs efficiently.

You can. I am lucky enough to not have been hacked after about a year of this, and I use a server in the living room. There are plenty of guides online for securing a server. Use common sense, and also look up threat modeling. You can also start hosting things locally and only host to the interwebs once you learn a little more. Basically, the idea that you need cloudflare and aws to not get hacked is because of misleading marketing.

Openhab is a project like HomeAssistant. Both are basically websites that offer pre made smart home functionaility and can run on your own server. Openhab doesn’t set a password by default (iirc), and when people expose it to the internet they end up with random bored people in another country somewhere flipping their lights on and off or adjusting their thermostat, though they could also get hacked. The openhab example was one of what not to do. I could have been more clear about that.

Security is an issue that people in this community are fairly opinionated on. Try to build up a practical knowledge of every tool you use (like tools for remotely managing your server). Think about how much access that tool gives you, and how easy it is to get. Ssh gets you basically full access to the system, except for bios level settings and things, but it is generally quite secure, and you can use keys instead of passwords. Cockpit, a remote management tool you can access from your browser, offers you a full terminal, so functionally the same access as ssh. However, hackers nearly got a back door into openssh (ssh is the protocol, openssh is the software on linux that implements that protocol), and cockpit is much less thoroughly looked at. Also cockpit doesn’t let you use keys.

You’re website will be static, which decreases the complexity and makes it easier to make it secure, so don’t worry too much. Here are some links that might be useful: https://www.digitalocean.com/community/tutorials/how-to-configure-ssh-key-based-authentication-on-a-linux-server

https://www.cyberciti.biz/tips/linux-security.html (this one seems to be geared more towards enterprise stuff, so not all of it is relevant, but a decent amount is.)

Edit: This one is good too. I recommend at least skimming it before the one above this. It will help you figure out which of the points in the link above are worth paying much attention to. https://owasp.org/www-community/Threat_Modeling