I think this is a fine community, but as a question, is there a reason you aren’t considering building a server? You could fit those requirements into a normal desktop chassis and likely still have some pci slots free for future upgrades.
I don’t use Immich, but if you open a feature request I’d suggest asking for open street maps, which offers a self hosted tile service https://www.maptiler.com/server/
Least you got it working again!
Whatever you are using that provides the brains of the network (like dhcp) in your setup probably the router or controller? I’ve never needed to move past an all in one but it seems like an intermittent routing issue. Have you u checked device logs to see if part of your network equipment is crashing or rebooting during these outages?
The only thing I see linking those devices are loosely speaking being Linux based.
Does the local connection work? Or are you unable to ping other devices on the lan?
I would guess it’s a switch issue assuming they can’t talk on the lan to each other.
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
GitHub has the option of emailing you on releases etc. by email.
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.
About a year ago now, it is possible they’ve changed things since.
The one time i published on the play store I just skipped that part and hit publish. I think it took several days to go live the first time but otherwise didn’t seem to matter.
This appears to be correct. See:
EncoderAppPath was simply not present at all in encoding.xml! There was only the display value: My own installation was completely fixed by adding /usr/local/bin/ffmpeg
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!
You can look at things like
https://www.newegg.com/tools/custom-pc-builder
To see some ideas of what would work, and I hope you feel free to ask around as you look at things! We all had to learn somehow and once you know what you’re looking for it’s just a small puzzle.
Quick suggestion is to decide on the cpu (I’m partial to amd so I’d pick something ryzen based if you want processing power) first then compatible motherboard, as after those two you should be able to just look at spec sheets and see things like the kind of ram you need case type etc.