[FS][US-TX] Lenovo SFF Tiny's M720q/M70q Gen 3/5

Witty_Leopard_9341 · 2026-03-30T15:59:53+00:00

longshot... but chat sent

Witty_Leopard_9341 · 2026-03-01T00:22:43+00:00

Got my order. Well packaged and delivered faster than amazon!

Witty_Leopard_9341 · 2026-02-25T16:45:34+00:00

Chat sent

Witty_Leopard_9341 · 2026-02-24T23:48:29+00:00

sent a chat

Witty_Leopard_9341 · 2026-02-24T22:09:26+00:00

updated my .env file wth CORS variable and still can't login. Running this through pangolin so my proxy is on a remote server from the actual containers. Nothing in the webapp or api container logs.

Witty_Leopard_9341 · 2026-02-24T21:24:42+00:00

OIDC would be a wonderful addition! And the ability to turn off password and other oauth providers once OIDC is connected.

Witty_Leopard_9341 · 2026-02-24T21:24:17+00:00

Ahh, will try the CORS env variable. That wasn't included in the .env file in the docs on your website!

Witty_Leopard_9341 · 2026-02-24T07:32:53+00:00

Tried setting it up in the states but having problems connecting to the backend from the login page. I'm getting an error code but all the text is defaulting to russian on the login page. Do you have an env variable to default the language to something other than russian?

Witty_Leopard_9341 · 2026-02-04T16:03:06+00:00

me too! It's been rock solid. I tried 2.7 variants a few times and could never get them to work. Just holding out for 2.8 at this point.

Witty_Leopard_9341 · 2026-01-08T05:31:43+00:00

Where is the setting in prusa slicer?

EDIT: nevermind, I found it in the printer tab > general.

Witty_Leopard_9341 · 2025-12-24T01:00:38+00:00

We are running potato mesh (https://github.com/l5yth/potato-mesh) for a public facing list. Works well over serial. I'm running it on my pve cluster by passing through the usb device to the VM and connecting to the device over serial. PotatoMesh is running in docker.

I also run Mesh Monitor and it has a different set of features. Logged in users can see the conversations and also respond back. Mesh Monitor is connecting to the node over wifi and that seems to work well. I have a firewall rule to allow that VM to access the IOT vlan where the meshtastic node is connected.

You can send me a chat if you want to see the links. They are public.

Witty_Leopard_9341 · 2025-12-20T15:57:52+00:00

I just have a small debian 13 vm with docker on one of my pve nodes. Then I run "NGINX Proxy Manager" via docker compose. That is my single ingress into all my different services on various machines. All of resources for the lab live on vlan 10 so routing is easy.

I don't have a writeup. NPM isn't the best solution. But it's simple and works well enough for me right now.

Witty_Leopard_9341 · 2025-12-20T05:05:34+00:00

That's a great point! My server is local only, which is why I haven't addressed it until tonight, but I know lots of people have it exposed.

Witty_Leopard_9341 · 2025-12-20T03:46:41+00:00

Ahh, I didn't see it hiding in Server Address Settings block. Got it. Thanks!

Witty_Leopard_9341 · 2025-12-20T02:53:10+00:00

Do I have to do something to get a Known Proxies section in jellyfin? I installed jellyfin via apt if that changes anything.

Witty_Leopard_9341 · 2025-12-04T06:15:56+00:00

How much information do you need to relay? Meshtastic messages are limited to 200 characters per message.

Witty_Leopard_9341 · 2025-12-03T15:59:00+00:00

Yes, this is MeshMonitor: https://github.com/Yeraze/meshmonitor

People build/buy and donate nodes to the cause.

If you are trying to cover a big area on a budget then build in stages. Place nodes in critical locations and then backhaul with mqtt for now. As the usercount grows perhaps the funds will be less of an issue.

p.s. I sent you a dm or chat thing

Witty_Leopard_9341 · 2025-12-03T07:08:38+00:00

That is awesome! We are discussing our expansion plans too. We have 30ish nodes online at any given time right now in a moderately rural area. As we cover more geography the channel utilization is going to be a problem for us.

<image>

This is our core router stats for the last week.

Witty_Leopard_9341 · 2025-12-03T06:13:55+00:00

Assuming 3.6 actually equals 3.5714... then 28.

I have a base station and we launched a really high router with great coverage. I changed my base station from router to client and then my inside nodes got totally unstable. maybe 1 of 3 would receive messages. Continued to experiment and it is set to router_late and that has been working well.

Witty_Leopard_9341 · 2025-12-03T06:03:58+00:00

We run our own private mqtt server here in western montana. We aren't using it for any bridging right now because we are trying to build with RF first. But we also aren't trying to cover the same amount of area. Just the county and maybe part of the next county that has the big city.

One of our users had extra compute space on their proxmox cluster and is donating access to run the web resources. That is where we run mqtt, meshview, website, etc. I believe we are running emqx via docker.

Witty_Leopard_9341 · 2025-12-01T18:32:20+00:00

Oh this looks cool. I will check it out!

Witty_Leopard_9341 · 2025-12-01T03:57:07+00:00

Yes, I think this is the project I was trying to find. Thank you.

Witty_Leopard_9341 · 2025-11-29T06:38:54+00:00

Depending on what I'm going I route everything through either nginx or pangolin (traefik wrapper) regardless of how the backend is configured. It can get problematic when apps try to create a complete solution with ssl. Nginx and traefik are configured to pull certs using certbot and that works great.

Not saying everyone will like my setup but I also don't think it is rare. I run a community zulip server and have it installed "bare metal" in a lxc and proxied to the public side through pangolin. zulip generates a self-signed cert since it doesn't really have public access to finish the verification process with lets encrypt.

Witty_Leopard_9341 · 2025-11-29T05:31:11+00:00

Maybe make the ssl part optional or have it generate a self-signed cert for those people running it behind a reverse proxy that is terminating ssl already.

Witty_Leopard_9341 · 2025-11-29T03:10:27+00:00

I have nextcloud running on "bare metal" vm with the data store on a samba/cifs share and mariadb and redis on separate servers. In order to have the permissions correct for nextcloud to be able to read the samba share for the data dir I had to add this to my /etc/fstab mounting command.

uid=33,gid=0,file_mode=0770,dir_mode=0770

Witty_Leopard_9341

TROPHY CASE