![]() On most Linux-distros, after re-mount of micro-SD-card, run: ```touch /media/$user/boot/ssh```. Create or copy a file called ssh in /boot. This will currently only work with 64-bit capable Raspberry Pi and Pi OS that is 64-bit.įor security reasons, as of the November 2016 release, Raspbian OS has the SSH server disabled by default. ![]() odinb/bash-plexamp-installer/blob/main/README.md # PlexAmp-installer for Raspberry Pi with ARM64 HW.įor more information and hardware used, see here: Ĭurrently installs/upgrades to: Plexamp Headless v4.2.2īurn the OS-image to the Micro-SD card using Raspberry pi imager, etcher (or app of your choice). If anyone has any suggestions for a solution or has any context for what may be causing it would be greatly appreciated. I have tried it with both my Raspberry Pi 3B and Pi 3B+ using Debian Bullseye Lite 64 Bit. I have attached the Audio+ V2 up to my AV Receiver and a set of powered bookshelf speakers I have and changing between them appears to have no affect. The problem exists both with the test sound when first installing the driver for raspberry pi in addition to how I am playing the audio from my plex library, linked below. The problem I am facing now is that the audio works but sounds like a box is put in front of my speakers with how muffled they sound. If anyone has any insight into how that ipv6 address got into /etc/nf I’d be interested to hear.I purchased a coupled of Audio+ V2 shields with the intention of getting them set up to as an alternative to Sonos for streaming audio from my plex media server in my house. I confirmed /etc/nf looks the same on another of my rpis with Tailscale, though not on my Mac which just lists my router IP as the nameserver.Īnd now Plex works as expected! Locally and remotely, both with the Tailscale IP and the Tailscale hostname. Which I didn’t expect, but my guess is this is how MagicDNS works (I do have that enabled), so I guess makes sense. Now /etc/nf seems to have been generated by Tailscale! # Generated by resolvconf I modified it to Google’s DNS servers: static domain_name_servers=8.8.8.8 8.8.4.4Īnd rebooted. I found the relevant setting in /etc/nf was blank: static domain_name_servers= etc/nf is auto-generated (from settings in /etc/nf apparently), so I rebooted (twice) to make sure that setting was current and persistent, and it was. I don’t know why, nor where it came from, nor what that address maps too, as I have ipv6 disabled on the Pi and my router doesn’t have ipv6 enabled. I checked the Pi’s /etc/nf and found it had an ipv6 address for nameserver. So, looks like DNS problems, maybe ipv6 related (those 6s looks suspicious to me). Watching the Plex logs I noticed errors like: 10:54:15.536 WARN - HTTP error requesting GET (6, Couldn't resolve host name) (Could not resolve host: )Īnd 10:35:10.666 ERROR - HTTP -6 downloading url ġ0:35:10.666 INFO - AutoUpdate: error getting data from Writing it up here in case it helps anyone. Should this just work, or is there something else to configure? Have I missed something? Similarly if I use my phone’s hotspot and try from outside my local network - “Something went wrong”. shows a Plex page with the msg “Something went wrong”, and my library, settings etc are not accessible. But that does not work if I use the Tailscale IP, nor the Tailscale hostname. On the same local network as the Pi, if I visit 192.168.1.22:32400 (the Pis local/internal IP) I can browse the Plex UI and see my library etc. However I run Plex on one of the Pis, and I can’t access the web UI over Tailscale. This works whether I am on the same local wifi network, or if I use my phone’s hotspot (ie through my mobile provider, not local network). ![]() I can also ssh etc, everything seems fine - using either the Tailscale hostname or the Tailscale IP. I have it installed on my Mac and a couple of Raspberry Pis.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |