That’s weird destiny 2 has never given me issue, though I don’t play super frequently so maybe I’m just lucky

Which games do that? Running pasthrough gpu on windows for destiny and halo at least gave me 0 issues for years

This seems like a good community for it, as the other commenter said your boot drive is likely dead.

We moved to Colorado and 10 miles takes me about 15 minutes to cross the city we’re in, 30 in traffic. Where we grew up 10 miles around the city was 1-2 hours regardless of time of day (except maybe 2am). The country is just way too diverse for distance to be nearly as meaningful at transit time.

Glad we got to the root issue! As others have said this is a learning process and you picked one of the more complicated ones to start with. Once this is done e everything else will start to feel much easier!

If you are on the raspberry pi with a physical screen/keyboard and mouse you can also try accessing with the ip address “localhost:80” and see if there’s a connection that way as well.

We can get the port list another way. From the terminal on the raspberry pi run the command “nmap localhost”. Let us know what that shows, but I would expect to see either 80, 443, or both.

As a side note, if you did not give the nextcloud container a certificate when you made it, you cannot use https:// on the browser, as it has no way to talk using that security mechanism. It is only capable in that case of using http:// and port 80. You will need to disable forced https to access the site (this is fine on the local network if every device is trusted, and only encrypted vpn service in like zerotier is used imo). This might be your problem here, especially if you are seeing both ports listed as open on the pi.

You would be given a safety risk warning page by your browser if you did the self signed certificate that you’d need to tell it to connect anyway, so that likely isn’t the issue. Looking at ports, how are you trying to connect to the server? If you did not assign a certificate at all, you would want to use port 80, port 443 if you did install a certificate.

For instance, my Nextcloud is on ip 192.168.50.30 With that in mind I would be using:

No certificate: http://192.168.50.30:80 Certificate: https://192.168.50.30:443

Does this look like what you are typing in?

As two additional questions, what is the output of “docker container ls” typed into the terminal? And what operating system did you install on the pi, was it raspbian?

At a glance your first issue is finding the correct ip address, you should only have one local ip address to access it with (inside your home network).

To find your local ip, type “ip a” into the terminal, and look for the address under “eth0“ for a wired connection, or “wlan0” for wireless. This will allow you to connect using the ip and port while on your home network to test the connection and make sure it works right.

After that, I highly recommend the vpn option, it will simplify connecting to it while not at home without creating security issues like setting it up with a domain. I personally use zerotier, that guide will help you get it set up on the raspberry pi. Not the last bit about a “managed ip.” That will be the address to tell your phone to connect too once you have the vpn set up on the phone as well.

This appears to be correct. See:

EncoderAppPath was simply not present at all in encoding.xml! There was only the display value: <EncoderAppPathDisplay /> My own installation was completely fixed by adding <EncoderAppPath>/usr/local/bin/ffmpeg</EncoderAppPath>

From the page

There’s a similar software called zerotier that only routes traffic you want across. You select an IP range (for instance 10.144..) and it gives your computer a new address. For my main computer let’s say it’s 10.144.168.128. The only traffic routed over the vpn is traffic addressed to that address. You can append the port to web traffic like https://10.144.168.128:8010/zm/index.php (zoneminder used as an example) and it would use the vpn for that connection but nothing else.

Docker on its own won’t think to look at that interface unless you tie it to it. Assuming you want to listen to both interfaces an external watchdog would be the call. You’d set the watchdog to look for iptables issues and then run commands if it went down (ie to restart iptables and then restart your containers).

Second the key-password combo. It keeps the keys you have on the flash drive but adds a password component that thieves would need to figure out as well. Just make sure to pick a good password!

They address concentrations varying among sites and comparative to urban areas. They also did other tests besides what you mentioned. Note:

Time- and spatially integrated samples of I/SVOCs were collected during box flight segments (for example, Fig. 1A) and downwind transects and analyzed by means of gas chromatography on both unit-resolution and high-resolution mass spectrometers [gas chromatography–electron ionization–mass spectrometry (GC-EI-MS) and gas chromatography–time of flight (GC-ToF)], which revealed abundant complex mixtures of I/SVOCs near both surface mining and in situ facilities (Figs. 2 and 3). IVOCs (C12 to C18) and SVOCs (C19 to C25) were uncharacteristically abundant relative to VOCs (Fig. 1E) and were observed around various facilities, as shown in selected flight samples in Fig. 2A (additional examples are available in figs. S6 and S7). The relative abundances and composition varied between and around facilities, with maxima ranging from C17 to C22 (Fig. 2A, figs. S8 and S9, and tables S5 and S6), which may suggest varying on-site sources and emissions pathways. There are stark differences in the observed concentrations when compared with that of urban areas.

Emphasis added to the last sentence mine. Why shill for oil at the expense of your own health?

That’s really nice to hear, lineage on a tablet a while back took quite a bit of work to get installed. Nevermind then having to get it able to load apps that needed Google.

Still a bit salty they gave almost no warning before retiring that image though, one month notice that they were getting rid of it was dissapointing to say the least

Hahaha yeah…it’s in many ways unfortunate that if you want to play/enjoy this instrument churches are the only option most of the time :/

Definitely worth the watts though!

It is software (grandorgue) that pretends to be a pipe organ (the instrument). In order to run fast enough it needs to load every sound sample into memory to play, as well as usually multiple kinds of sound endings. I play professionally on a “small to mid sized” pipe organ with 1,438 pipes. The one I load for use at home has more than that!

The instrument was from the 1960s and I rebuilt it with a pi pico that you can see here, and you can hear the before (analog sound cards) versus one of the organs I’ve loaded into it here.

Do you have a link to their store? I haven’t seen one

If these supported phones I actually wanted I’d consider it. Even better if they weren’t a pain in the ass to install.

Man my home server IDLES at 76 watts per hour running x86. Now mind you I need the x86 to perform some of the functions I want. This thing works as an NAS, nextcloud, media server, kiwix, security camera (zoneminder), remote desktop (xrdp), runs home assistant, gpu AI upscaling for photos, and finally screeches along running a virtual pipe organ I built that takes 69 GB of RAM to run.

If I could do that with raspberry pi’s I would in a heartbeat! the power savings alone would eventually pay for them. If it’s doing what you want then don’t worry about them. My pi400 works as a remote desktop client and one day I hope more of this stuff will work well on it/a future generation so I can ditch the tower, energy usage, and noise.