cert error message

[gariac]

./MeshStation_v1-1-1.AppImage MeshStation started. [3347919:3347973:0418/000325.457783:ERROR:nss_util.cc(345)] After loading Root Certs, loaded==false: NSS error code: -8018
Linux framework13 6.12.73+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.73-1 (2026-02-17) x86_64 GNU/Linux

[IronGiu]

Does the app work? If it works, it's not a problem, just a warning, unless they're suppressed internally, as many apps do. They're commonplace on Linux given the myriad of distros, drivers, and hardware available. That's a Chromium warning; it shouldn't compromise usability, and I'm unable to reproduce it. It didn't appear on any of the eight distros in four configurations I tested it on. Let me know if the app works and give me more details about the specific distro. If the app works, double-click it instead of launching it from the terminal, and you won't receive any console spam.

[gariac]

Well since it could not find a SDR , I didn't get any further.

[IronGiu]

Does other SDR software detect it? The wiki has a complete guide on how to install SDR drivers and how to get it to work if it encounters permissions issues. But if other software sees it, MeshStation should too.

Take a look here. The wiki exists specifically for this purpose and is also linked when it says it can't find the device. Otherwise, tell me what device you're using. Maybe it's not directly supported by GnuRadio and you'll need to use plugins.

Driver install in the wiki: https://github.com/IronGiu/MeshStation/wiki/English#rtl-sdr-drivers-setup-linux

[gariac]

There is no driver issue. I run dump1090, sdrpp, etc.

[IronGiu]

Try using it in gnuradio, under the hood the app uses gnuradio and osmosdr for the drivers, so if they see it, the app must see it (have you tried starting with "automatic"?) If it is SoapySDR I already tell you that it needs a specific plugin to run, the error you show here has nothing to do with device detection, it is a QT/chromium warning, tell me what device you use.

[gariac]

Soapy is only for the "weird" SDRs, in my case plutos.  Everything else I run on rtlsdr. Meshstation pretty much doesn't go full screen without a connection. I don't have any gnuradio files. I will try one of these. https://github.com/nechry/gnuradio-projects Apr 19, 2026 5:45:10 PM IronGiu ***@***.***>:

…

[https://avatars.githubusercontent.com/u/59703518?s=20&v=4]*IronGiu* left a comment (IronGiu/MeshStation#15)[#15 (comment)] Try using it in gnuradio, under the hood the app uses gnuradio and osmosdr for the drivers, so if they see it, the app must see it (have you tried starting with "automatic"?) If it is SoapySDR I already tell you that it needs a specific plugin to run, the error you show here has nothing to do with device detection, it is a QT/chromium warning, tell me what device you use. — Reply to this email directly, view it on GitHub[#15?email_source=notifications&email_token=AA4FI7F2JR3PYZR7NFTBQID4WVXJJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXG4ZDENRZGA32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4277226907], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AA4FI7FOHLPCGY4KHTNMRPD4WVXJJAVCNFSM6AAAAACX5XVQ42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENZXGIZDMOJQG4]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/AA4FI7C6MUKBBR7F4T4TLID4WVXJJBFCNFSM6AAAAACX5XVQ42WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTX66FGZXJTSMVQXG33OUZQXK5DIN5ZA.gif]

[IronGiu]

Pluto does not have native support with osmosdr, you need to use specific libraries and special bridges, we can't take care of it, you have to ask in the osmosdr reddit to possibly add direct compatibility, otherwise search online how to use it with osmosdr or even better wait for the next update where MeshStation will support rtl_tcp and using this protocol you can perhaps connect pluto via rtl_tcp on the local host and then select rtl tcp in MeshStation and enter 127.0.0.1 as host and the chosen port (default 1234)

[gariac]

I couldn't find one grc file online that ran. I did the gnuradio example and it works.

[IronGiu]

Have you tried starting the connection from meshstation by setting it to "auto detected"? That way osmosdr will manage the driver directly as if you were on gnuradio without going through MeshStation's detection system. Unfortunately, I don't have a pluto device to test with, so try this. If it works, paste the contents of the meshstation log console (you can also find it by exporting the data in the generated file) so if osmo detects it, I'll have more data to work with. Unfortunately, not having a pluto device, we have to rely on the data of whoever owns one.

[gariac]

To be clear here, meshstation is no longer finding my rtlsdr. I haven't tried a Pluto. If you look at the gnuradio screenshot, you will see it is using the rtlsdr. Wasn't that your question? While I have your ear, since you made an app image, should I be running this is in /use/local/bin? And should I try compiling the code? Apr 20, 2026 4:20:08 PM IronGiu ***@***.***>:

…

[https://avatars.githubusercontent.com/u/59703518?s=20&v=4]*IronGiu* left a comment (IronGiu/MeshStation#15)[#15 (comment)] Have you tried starting the connection from meshstation by setting it to "auto detected"? That way osmosdr will manage the driver directly as if you were on gnuradio without going through MeshStation's detection system. Unfortunately, I don't have a pluto device to test with, so try this. If it works, paste the contents of the meshstation log console (you can also find it by exporting the data in the generated file) so if osmo detects it, I'll have more data to work with. Unfortunately, not having a pluto device, we have to rely on the data of whoever owns one. — Reply to this email directly, view it on GitHub[#15?email_source=notifications&email_token=AA4FI7D3WVLAOZKMSDCLSXD4W2WCNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRYGQ4DONZQGU4KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4284877058], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AA4FI7FUDKQ4OJNEV5LPVWT4W2WCNAVCNFSM6AAAAACX5XVQ42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEOBUHA3TOMBVHA]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/AA4FI7BJLBDXLLM4L3ZIPGD4W2WCNBFCNFSM6AAAAACX5XVQ42WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTX7MYEQFJTSMVQXG33OUZQXK5DIN5ZA.gif]

[IronGiu]

I don't understand. What do you mean mesh station don't see your rtlsdr ? What devices are you using? You can put the app in usr/local/bin, then you have to make it executable again with chmod +x. Although it's not recommended, it's better to put it in a dedicated folder or in applications. Compiling the code is complex; it's not a public process and requires good knowledge of the tools to compile it. I don't offer compilation support; it's only included in premium support.

[gariac]

The previous version, that is the one that isn't an app image, worked fine. It found the rtlsdr. The app image version doesn't find the rtlsdr. Unless I didn't understand you, the whole point of proving that gnuradio could find the rtlsdr was to eliminate gnuradio as the issue regarding meshstation not finding the rtlsdr. That is why I "built" the FM radio in gnuradio. Forget I mentioned the Plutos. Apr 20, 2026 9:57:42 PM IronGiu ***@***.***>:

…

[https://avatars.githubusercontent.com/u/59703518?s=20&v=4]*IronGiu* left a comment (IronGiu/MeshStation#15)[#15 (comment)] I don't understand. What do you mean mesh station don't see your rtlsdr ? What devices are you using? You can put the app in usr/local/bin, then you have to make it executable again with chmod +x. Although it's not recommended, it's better to put it in a dedicated folder or in applications. Compiling the code is complex; it's not a public process and requires good knowledge of the tools to compile it. I don't offer compilation support; it's only included in premium support. — Reply to this email directly, view it on GitHub[#15?email_source=notifications&email_token=AA4FI7AKXSOVKTMYRUKKZED4W35UJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRYGYYDCNRRGQ42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4286016149], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AA4FI7EKRALTWMPBX7RIYX34W35UJAVCNFSM6AAAAACX5XVQ42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEOBWGAYTMMJUHE]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/AA4FI7EI4JOGZ27MTCXGJ7L4W35UJBFCNFSM6AAAAACX5XVQ42WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTX7O5VJLJTSMVQXG33OUZQXK5DIN5ZA.gif]