rutherford

<face palm> I didn't! I'll do it, do a restart and see we go, and post here. Thanks so much @JorgeB

Made the two changes to bios: Global C-state Control: Disabled Power Supply Idle Control: Typical Current Idle Did a btrfs scrub on the one cache drive I have (nvme0n1p1), rebooted, errors persist. I'll attach a few screen grabs, and a log. Ah here my latest system log https://hastebin.com/share/saleyadehi.yaml Ah yeah, the cache drive has some uncorrectable errors. Perhaps I did that "scrub" incorrectly? I checked the Fix It box, errors persisted. I didn't see any documentation/wiki on this Scrub operation.

rubble-diagnostics-20230322-0708.zip

Looks like I'm getting some BTRFS errors on my nvme0n1p1 https://hastebin.com/share/wifurixani.yaml I saw on another post that bad memory was sometimes a culprit there. I'll do a memtest86 USB boot and see if that turns anything up. Getting an appdata backup done here... SMART test from the ssd https://hastebin.com/share/caleferado.yaml

I seem to remember it being a little more stable for like months at a time. Recently, I'll notice one or two of my dockers aren't responsive. When I go to restart them, they fail and red square, with general error message. Other green running dockers, when restarted will also fail and not come back up after being restarted. I restart the whole server, that seems to sort stuff out. Just hoping a guru out there could take a peek at my diagnostics and we can anticipate a failure before it all comes crashing down. thanks! rubble-diagnostics-20230314-2102.zip

When you first run the Roon client, you are presented with a screen that says "Choose your Roon Core" where it will try and find a running Roon Core on the network, or you can "Set up a Roon Core on this PC" If you've already selected the Set up a Roon Core on this PC, then you can get into the software and start listening to music: BUT that wasn't the right move. As you've set up your Roon Core on the network already, you need to backup the local installation process. Open your Roon Software, go to Settings, then logout. Close the software. Re-run the software and hopefully it'll find your Roon Core on the network. After you hit Connect to core, you'll be presented with the username/password to get authenticated with Roon registration software. You've already started the free trial (I can see that from your screen shot up there).

ah oh yeah, I see that up there now. So the Roon docker isn't even running. It shows a red box on the icon under Dashboard. Red box = not running. If the window closes immediately and nothing happens, I suggest nuking it and reinstalling. There are two steps to this. You gotta delete the docker, and image. Then you need to delete the folders associated with Roon in your appdata/ folder. For me it's: /mnt/user/appdata/roonserver Huh, there used to be in in there called raat or something, but I don't see it anymore. I suppose it's only that one folder "roonserver/" Delete that also. Reinstall and see if that gets better.

@VIthe3rd can you give us more to go from? how about a screen shot of the running Docker. And the Settings of the room Docker page. Are you logged in with your room credentials? Do you see anything when you run the local software? also check Docker > Roon > Logs. See if there are any errors in there. Ha! I have errors. Here’s my Roon Log screen

I was hoping to get some help with a docker I've recently added that I'd like to route through SWAG. I had to setup the Docker manually, here are the results of that Docker run: -d --name='conduit' --net='proxynet' (<----- the unRaid Network I use for all my SWAG ssl connections) -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="rubble" -e HOST_CONTAINERNAME="conduit" -e 'CONDUIT_SERVER_NAME'='matrix.mydomain.com' (<---obfuscated) -e 'CONDUIT_DATABASE_BACKEND'='rocksdb' -e 'CONDUIT_ALLOW_REGISTRATION'='true' -e 'CONDUIT_ALLOW_FEDERATION'='true' -e 'CONDUIT_MAX_REQUEST_SIZE'='100000000' -e 'CONDUIT_TRUSTED_SERVERS'='["matrix.org"]' -e 'CONDUIT_MAX_CONCURRENT_REQUESTS'='100' -e 'CONDUIT_LOG'='warn,rocket=off,_=off,sled=off' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/mozilla/fxemoji/gh-pages/svgs/nature/u26A1-bolt.svg' -p '8448:6167/tcp' -v '/mnt/user/appdata/matrix-conduit':'/var/lib/matrix-conduit':'rw' 'matrixconduit/matrix-conduit:latest' c9a300cad404e7a5e9d4298ec7a2413fd3e6c5650aa7deafdcb60e411501254c I'm getting the "502 Bad Gateway nginx" error when I hit my subdomain, and that's an error with the SWAG conf. /mnt/user/appdata/swag/nginx/proxy-confs/conduit.subdomain.conf ## Version 2023/02/05 # REMOVE THIS LINE BEFORE SUBMITTING: The structure of the file (all of the existing lines ) should be kept as close as possible to this template. # REMOVE THIS LINE BEFORE SUBMITTING: Look through this file for <tags> and replace them. Review other sample files to see how things are done. # REMOVE THIS LINE BEFORE SUBMITTING: The comment lines at the top of the file (below this line) should explain any prerequisites for using the proxy such as DNS or app settings. # make sure that your <container_name> container is named <container_name> # make sure that your dns has a cname set for <container_name> server { listen 443 ssl; listen [::]:443 ssl; server_name conduit.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth (requires ldap-location.conf in the location block) #include /config/nginx/ldap-server.conf; # enable for Authelia (requires authelia-location.conf in the location block) #include /config/nginx/authelia-server.conf; # enable for Authentik (requires authentik-location.conf in the location block) #include /config/nginx/authentik-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable for ldap auth (requires ldap-server.conf in the server block) #include /config/nginx/ldap-location.conf; # enable for Authelia (requires authelia-server.conf in the server block) #include /config/nginx/authelia-location.conf; # enable for Authentik (requires authentik-server.conf in the server block) #include /config/nginx/authentik-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app conduit; set $upstream_port 8448; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } # REMOVE THIS LINE BEFORE SUBMITTING: Some proxies require one or more additional location blocks for things like API or RPC endpoints. # REMOVE THIS LINE BEFORE SUBMITTING: If the proxy you are making a sample for does not require an additional location block please remove the commented out section below. # location ~ (/<container_name>)?/api { # include /config/nginx/proxy.conf; # include /config/nginx/resolver.conf; # set $upstream_app <container_name>; # set $upstream_port <port_number>; # set $upstream_proto <http or https>; # proxy_pass $upstream_proto://$upstream_app:$upstream_port; # # # REMOVE THIS LINE BEFORE SUBMITTING: Additional proxy settings such as headers go below this line, leave the blank line above. # } } conduit.subdomain.conf lines 19-62/62 (END) Conduit is an implementation of Matrix chat server. There is no SWAG template for it; so I've been doing the best I can repurposing a different domain template over into this one, but I'm striking out. My end goal here is to bring iMessage, Whatsapp, Signal, FB Messenger, IG Messenger, and SMS all into one chat app that will work on: iPhone, android, and my windows laptop. Probably with Element app. Some notes so far https://forums.unraid.net/topic/135799-love-to-1-ditch-iphone-2-keep-imessage-and-3-combine-all-messengers/#comment-1235564

Going to see about setting this up using Beeper self hosted inside a Macmini I think https://github.com/beeper/self-host

Run the matrix docker once docker install > advanced remove the "generate" from the Post Argument field Get SWAG reverse proxy going /mnt/user/appdata/swag/nginx/proxy-confs cp synapse.subdomain.conf.sample synapse.subdomain.conf some help with this step https://discourse.linuxserver.io/t/help-needed-with-synapse-matrix-behind-swag-server/3815/2 edit SWAG docker settings to include "matrix" in the list of comma-seperated Subdomain(s). edit Matrix docker Network Type to Custom: proxynet edit /mnt/user/appdata/swag/nginx/proxy-confs/synapse.subdomain.conf from: set $upstream_app synapse; to: set $upstream_app Matrix-Synapse; Our docker Name: is Matrix-Synapse, that needs to match this piece so SWAG can figure it out. carry on here: https://community.nethserver.org/t/install-matrix-synapse-including-whatsapp-bridge-using-docker-compose/21214 to start adding bridges. ?how do I connect to my home server via Element app, web app, or windows app? How do I start adding bridges? Go into the Docker CLI, run commands in there I think, to grab GIT stuff

Friggin Tim Cook and the Apple monster finally had me give in and switch to an iPhone. It hasn’t been all bad, the apple AirPods I never would have tried, and wow are they terrific. I’d love to get the functionality of iMessage on a web interface AND a phone of my choosing (android Pixel). Looks like Beeper is doing exactly that. The creator blog mentions being at their work laptop and not wanted to pull out iPhone for messaging. I have a whole pile of apps that are “messaging apps”: Signal, iMessage, WhatsApp, FB Messenger, and Discord. And Instagram. Facepalm. I already have a NAS (unRaid) 24/7 home server with Docker. There IS a Matrix chat how-to for unRaid, which is probably where I’ll start and participate. I’m ready to get a Mac mini (how I hear Beeper is making iMessage work). I’ve tried several times to get a Macinabox VM going but for one reason or another it’s been like pulling teeth. I’m also going to require damn near 100% uptime for this project. And what a good opportunity to combine all those messengers. Otherwise I’ll have to add Blue Bubbles or We Message as yet ANOTHER messenger app to keep track of. And then what do I use as my primary messenger app or actual SMS? So, I’d like to see a more robust wiki how-to for the setup that Beeper is doing. So I’ll write it. At $10/mo I’d like to figure out the self hosting thing! I’d be happy for any additional resources you folks know of. Especially someone that’s done it before wink https://github.com/beeper/self-host https://forums.unraid.net/topic/127917-guide-matrix-synapse-w-postgres-db-chat-server-element-web-client-coturn-voice/ https://blog.beeper.com/p/were-building-the-best-chat-app-on https://www.macrumors.com/2021/01/21/beeper-brings-imessage-to-android-and-windows/ my reddit post in /selfhosted https://www.reddit.com/r/selfhosted/comments/11fa14l/stick_it_to_apple_imessage/

Yeah, mine looks the same as yours. have you tried several different episodes? Sometimes the encoding that’s used for specific episodes doesn’t fly with our gpu. I think it’s something like the NVEC or color depth I think? I have noticed that several episodes go over to the cpu for encoding, but most are the (hw) in there. And you want to make sure on your test player, you turn down the kbps for the stream, and double check that’s what you’re seeing, the lower kbps version. sorry I can’t be of more help!

@elmuziko I went back to the Plex docker. It’s been okay, and it’s paid for. it was working for me when I wrote that post, using the screen shots I’d grabbed; but like Mik3 said up there: more things have likely changed and the instructions might not be concise or even correct at this point!

Anyone made any progress or tried getting a self-hosted Beeper going? https://github.com/beeper/self-host im primarily interested in getting all my messengers (including WhatsApp, Signal, iMessage, SMS, IG, FB) all in one app, and available via ssl webpage. I signed up for a beeper.com account, but still haven’t been contacted about onboarding. Guess they don’t want my money. at $10/mo, the self-hosted hassle just might be worth it! Even purchasing a MacBook or something to relay iMessages… I tried getting a MacOS VM going a year ago, it was finicky even with Spaceinvader Macinabox! I also tried Macinabox again last month, 1/2023: still finicky. And: even when I did get it going once, I still had to call up Apple and convince them I’d purchased a used Mac to get iMessage running. 🤷‍♀️ beeper.com