selfhosted

This magazine is from a federated server and may be incomplete. Browse more on the original instance.

jelloeater85, in Private and/or cheap places to register a domain
@jelloeater85@lemmy.world avatar

NameCheap.com

MigratingtoLemmy, in Alternative to Home Assistant for ESPHome Devices

Why aren’t you using Node-red and ntfy/MQTT brokers? HA is feature-bloat for me

TCB13,
@TCB13@lemmy.world avatar

I wasn’t aware that node-red existed until this post :P

MigratingtoLemmy,

Have fun!

MP3Martin, (edited ) in Question: Best UI to manage VMs and containers?
@MP3Martin@programming.dev avatar

I don’t think it can natively do VMs but I’m using CapRover to deploy Docker images on my server

possiblylinux127, in Question: Best UI to manage VMs and containers?

What’s wrong with ssh?

hperrin,

Nothing. I’ve been using SSH. I’d like to have both options, SSH and a web UI.

MangoPenguin, in Question: Best UI to manage VMs and containers?
@MangoPenguin@lemmy.blahaj.zone avatar

Dockge or Portainer are both good options.

For VMs you’ll need to find something else, you could use Cockpit for that.

RootBeerGuy,
@RootBeerGuy@discuss.tchncs.de avatar

Thanks for mentioning Dockge, hadn’t heard of it yet. Already use portainer but it seems a bit overkill for me and my few containers. Will try Dockge.

antrosapien,

Do they work with podman? Or anything for podman?

egeres, in Does anyone else harvest the magnets and platters from old drives as a monument to selfhosting history?
@egeres@lemmy.world avatar

What are they made of anyways?? Could one see any etching marks with a microscope?

brlemworld,

Bunch of tiny magnets either north or south.

Morphit,
@Morphit@feddit.uk avatar

Usually aluminium or glass. There’s a metallic coating applied to the outside surfaces that stores the data. That layer is very thin though, so most of the material is the substrate.

olmium, in Does anyone else harvest the magnets and platters from old drives as a monument to selfhosting history?

Considering they’re covered in toxic shit, nope.

Piatro, in Actual: How to import data with proper readable payee?

Personally I rename them to something meaningful and they get merged if there are no other references. PayPal is especially bad for completely meaningless rubbish in the payee field and they tend to be ad-hoc purchases so I don’t fiddle with them much. The category is the most relevant bit for me.

Atemu,
@Atemu@lemmy.ml avatar

Yeah, I’ve noticed the PayPal issue aswell.

Faceman2K23, in Private and/or cheap places to register a domain
@Faceman2K23@discuss.tchncs.de avatar

With Google domains transferring to Squarespace I’ll be transferring my one remaining domain with them to something else soon enough.

I already moved all of my other domains over to a local provider I use for work that has treated me well, but this one last google domain address has my self hosted services on it and I was using some features that I didn’t want to have to transfer so I kept it with google. I was using their ddns service too but my IP is now sticky (effectively static but can change in some rare circumstances) and it has only changed once in the last 3 years so I think I’ll just manually manage the A records if needed until I either go fully static or use a third party ddns provider. I also use email aliasing to use me@mydomain with gmail.

RIP_Cheems, in Does anyone else harvest the magnets and platters from old drives as a monument to selfhosting history?
@RIP_Cheems@lemmy.world avatar

I wish I got that many hard drives just so I could do this.

aldalire, in Does anyone else harvest the magnets and platters from old drives as a monument to selfhosting history?

This man self-hosts

Che_Donkey, in Does anyone else harvest the magnets and platters from old drives as a monument to selfhosting history?
@Che_Donkey@lemmy.ml avatar

I havest them for the BlooDisk God Linuxathor, we are not the same.

possiblylinux127, in Does anyone else harvest the magnets and platters from old drives as a monument to selfhosting history?

I use SSDs

Oisteink, in [solved] Nginx proxy server - strange behavior

As you can forward by ip but not by name it sounds like resolver issue.

tubbadu,

how can I find out more about this?

Oisteink, (edited )

On the host of the nginx rev proxy or in nginx config files. Something seems to block the lookup from name to ip, as ip works you know the proxy works. Check dns config and nginx config on that host

tubbadu,

here’s the configuration file for jellyfin:


<span style="color:#323232;"># ------------------------------------------------------------
</span><span style="color:#323232;"># jellyfin.tubbadu.duckdns.org
</span><span style="color:#323232;"># ------------------------------------------------------------
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">map $scheme $hsts_header {
</span><span style="color:#323232;">https   "max-age=63072000; preload";
</span><span style="color:#323232;">}
</span><span style="color:#323232;">
</span><span style="color:#323232;">server {
</span><span style="color:#323232;">set $forward_scheme http;
</span><span style="color:#323232;">set $server         "192.168.1.13";
</span><span style="color:#323232;">set $port           8096;
</span><span style="color:#323232;">
</span><span style="color:#323232;">listen 80;
</span><span style="color:#323232;">listen [::]:80;
</span><span style="color:#323232;">
</span><span style="color:#323232;">listen 443 ssl;
</span><span style="color:#323232;">listen [::]:443 ssl;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">server_name jellyfin.tubbadu.duckdns.org;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;"># Let's Encrypt SSL
</span><span style="color:#323232;">include conf.d/include/letsencrypt-acme-challenge.conf;
</span><span style="color:#323232;">include conf.d/include/ssl-ciphers.conf;
</span><span style="color:#323232;">ssl_certificate /etc/letsencrypt/live/npm-18/fullchain.pem;
</span><span style="color:#323232;">ssl_certificate_key /etc/letsencrypt/live/npm-18/privkey.pem;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;"># Block Exploits
</span><span style="color:#323232;">include conf.d/include/block-exploits.conf;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">proxy_set_header Upgrade $http_upgrade;
</span><span style="color:#323232;">proxy_set_header Connection $http_connection;
</span><span style="color:#323232;">proxy_http_version 1.1;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">access_log /data/logs/proxy-host-5_access.log proxy;
</span><span style="color:#323232;">error_log /data/logs/proxy-host-5_error.log warn;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">location / {
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">proxy_set_header Upgrade $http_upgrade;
</span><span style="color:#323232;">proxy_set_header Connection $http_connection;
</span><span style="color:#323232;">proxy_http_version 1.1;
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;"># Proxy!
</span><span style="color:#323232;">include conf.d/include/proxy.conf;
</span><span style="color:#323232;">}
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;"># Custom
</span><span style="color:#323232;">include /data/nginx/custom/server_proxy[.]conf;
</span><span style="color:#323232;">}
</span>
tubbadu,

on the server host myserverhostname correctly resolves, but if I enter the container (docker exec -it nginx-app-1 bash) it does not work anymore:


<span style="color:#323232;">[root@docker-11e3869f946f:/app]# host tserver
</span><span style="color:#323232;">Host tserver not found: 3(NXDOMAIN)
</span>

(I had to install dnsutils before)

it seems a nginx issue then

Oisteink,

Could also be docker network-config. Docker should by default use the hosts resolver config if there’s nothing in /etc/resolve.conf

You can also supply dns server on the docker command or in your compose file if you’re using compose.

As a last resort you can enter server and ip i the container’s /ets/host file if the ip is static. But that’s gone once you rebuild the image.

Or maybe there’s env on the container you use for dns

tubbadu,

I found a solution: use myserverhostname.station instead of just the hostname. I really have no idea why, on the previous installation it worked well with just the hostname… ahh, whatever.

thank you very much for the help!

epyon22, in GameStreaming from UbuntuServer

I guess what problems are you having? I’ve used steam link before perfectly fine but it’s going to have some loss over the network. Are both computers connected to a gigabit lan? Balder’s gate 3 is a newer game, and while you aren’t on minimum requirements you are on mid tier hardware using proton to run a windows game, so there are a few reasons you may be having problems. Best way to run it down is isolate things and see how they go. Try running game directly on the computer with monitor ect.

RandomLegend,
@RandomLegend@lemmy.dbzer0.com avatar

It appears as if you misunderstood my post…

I currently DONT have gamestreaming from my Ubuntu Server to the minisforum. I WANT to have it but i don’t know how to properly set it up. I tried several installs of sunshine but it fails everytime on encoders… and the docker support is very manual at the moment.

The performance issues i have on BG3 are running directly on the minisforum thats why i want to run it on the server instead.

So basically my post is asking for help on setting up sunshine on my ubuntu server

epyon22,

Ah I don’t know much about sunshine and your specific setup. But I know docker can be a pain getting access to devices like graphics cards. Maybe try running natively?

RandomLegend,
@RandomLegend@lemmy.dbzer0.com avatar

I’ve got my GPU running in docker when i wanted to use hw transcoding on my Plex docker. So this is already cleared.

I’ve researched a bit since posting and found that using sunshine directly is not the easiest route to pick here since their docker installation is still in early development and involves a lot of manual config and setup.

I’ll go with games-on-whales.github.io/gow/running.html as they use sunshine but deliver a nearly completely configured docker-compose environment.

I ordered a HDMI dummy plug that i can use.

redcalcium,

If you’re using Sunshine on an nvidia system, you’ll have to patch your nvidia driver to be able to use nvenc and nvfbc without restriction. Check out this repo for more info: github.com/keylase/nvidia-patch

RandomLegend,
@RandomLegend@lemmy.dbzer0.com avatar

What would my advantages be here after using the patches?

I plan to only connect one single client to my host at any given moment. So i don’t think i need the restrictions lifted i guess?

redcalcium, (edited )

Iirc sunshine still need nvfbc to grab the rendered frames.

Use NVIDIA Frame Buffer Capture to capture direct to GPU memory. This is usually the fastest method for NVIDIA cards. For GeForce cards it will only work with drivers patched with nvidia-patch or nvlax.

docs.lizardbyte.dev/…/advanced_usage.html

RandomLegend,
@RandomLegend@lemmy.dbzer0.com avatar

Got it, thanks!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • selfhosted@lemmy.world
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #