gaylord_fartmaster @ gaylord_fartmaster @lemmy.world

Posts

0

Comments

421

Joined

2 yr. ago

I did this once to install a different distro on a free oracle VPS lol

My theory is that the RTSP port (554) is for streaming and that when I go to the local address (that is on 80), the site ITSELF initiates a connection to port 554 in the background. However, this apparently does not happen when I connect remotely.

I think you're on the right track here. The DVR is probably telling your browser to connect to http://192.168.1.222:554 for the stream, which on LAN is fine because you have a route to 192.168.1.222, but when connecting externally you won't be able to get to 192.168.1.222.

You can probably check the network connections in dev tools in the browser to confirm that.

Edit: Editing this to also stress the importance of the advice given by @SteveTech@programming.dev. My home cameras are also only accessible from outside my network via wireguard.

Overwatch did not invent playing a character that has abilities on a cooldown. It's much more like fast-paced dota with guns.

FPS, but mostly because I no longer have the free time to finish a 50-100 hour RPG.

I use Nextcloud with Nginx Proxy Manager and just use NPM to handle the reverse proxy, nothing in Nextcloud other than adding the domain to the config so it's trusted.

I use Plex instead of Jellyfin, but I stream it through NPM with no issues. I can't speak to the tunnel though, I prefer a simple wireguard tunnel for anything external so I've never tried it.

Edit: unless that's what you mean by tunnel, I was assuming you meant traefik or tailscale or one of the other solutions I see posted more often, but I think one or both of those use wireguard under the hood.

I have a feeling the people making fiber internet faster aren't the same people installing it in neighborhoods.

Credit card charge back, demand letter written by an attorney, or small claims court.

Those are pretty much your options.

I've never used Native Alpha, but from what I saw at a glance, Firefox does have that same functionality built in through the "Add to Home Screen" option, but only if the site is a PWA. Otherwise the home screen icon will just open the site in the browser like it normally would.

The product was an LLM.

I never switched to Proton for exactly this reason. I'd much rather use a service that does one thing really well than one that does 20 things okay.

It's all just to keep you locked into your subscription. Now they want you to keep other money tied up in it too.

I guess we're starting to run out of video game titles already?

The issue is that the docker container will still be running as the LXC's root user even if you specify another user to run as in the docker compose file or run command, and if root doesn't have access to the dir the container will always fail.

The solution to this is to remap the unprivileged LXC's root user to a user on the Proxmox host that has access to the dir using the LXC's config file, mount the container's filesystem using pct mount, and then chown everything in the container owned by the default root mapped user (100000).

These are the commands I use for this:

    
find /var/lib/lxc/xxx/rootfs -user 100000 -type f -exec chown username {} +;
find /var/lib/lxc/xxx/rootfs -user 100000 -type d -exec chown username {} +;
find /var/lib/lxc/xxx/rootfs -user 100000 -type l -exec chown -h username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type f -exec chown :username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type d -exec chown :username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type l -exec chown -h :username {} +


  

(Replace xxx with the LXC number and username with the host user/UID)

If group permissions are involved you'll also have to map those groups in the LXC config, create them in the LXC with the corresponding GIDs, add them as supplementary groups to the root user in the LXC, and then add them to the docker compose yaml using group_add.

It's super confusing and annoying but this is the workflow I'm using now to avoid having to have any resources tied up in VMs unnecessarily.

I've been doing this for at least a decade now and the drives are just as reliable as if you bought them normally. The only downside is having to block one of the pins on the SATA connector with kapton tape for it to work.

We do, standard contract law. If your contract says you should be getting credit, and you aren't given credit, that's an enforcable contract violation.

Damn I forgot no content existed online and could be profitable before YouTube came along and saved us all from the dark ages.

Exactly, then it could have just been a text list on a webpage and we'd all be better off.

Acts as a wildcard for any directories that exist between arteries and clot.

You'd be surprised how often none of that is touched, and I really doubt any repackers are bothering to block any network calls if the original scene release didn't. I've used some equivalent of OpenSnitch that prompts on all network requests that I haven't explicitly allowed already for the past decade, and at least 90% of all games I downloaded during that time tried to phone home.

ALWAYS set firewall rules to block internet access to any software you pirate.