TNAP-6 Image Discussion

I think you are missing a piece of the puzzle. The path has to be exactly this: /media/usb/ServiceScan
Or exact path: /media/FTA/ServiceScan
Or exact path: /hdd/ServiceScan
If none of those paths can be found, then the reports are dumped into /tmp, and there is no folder provision for /tmp
Also understand the /tmp folder is dumped during a reboot and that is why I call it the temporary folder!

It has been like this for years. Normally when you stick an usb drive into the receiver, you automatically get: /media/usb
And the name of the Folder has to be exactly ServiceScan
Here is what one of my receiver's looks like:
Code:
root@sf8008:~# ls -lh /media/usb/ServiceScan/
-rw-r--r--    1 root     root        1.3K Sep 21 21:13 100.9W_Ku-band_113ch_1tp_09-21-2025_21-13-52.xml
-rw-r--r--    1 root     root        1.4K Oct  2 00:24 100.9W_Ku-band_114ch_1tp_10-02-2025_00-24-55.xml
-rw-r--r--    1 root     root        1.4K Oct  2 00:26 100.9W_Ku-band_114ch_1tp_10-02-2025_00-26-01.xml
-rw-r--r--    1 root     root        1.3K Sep 20 15:38 100.9W_Ku-band_11ch_1tp_09-20-2025_15-38-25.xml
-rw-r--r--    1 root     root        1.3K Sep 21 07:50 100.9W_Ku-band_17ch_1tp_09-21-2025_07-50-29.xml
-rw-r--r--    1 root     root        1.3K Sep 21 07:51 100.9W_Ku-band_17ch_1tp_09-21-2025_07-51-49.xml
-rw-r--r--    1 root     root        1.3K Sep 20 21:32 101.0W_Ku-band_113ch_1tp_09-20-2025_21-32-09.xml
-rw-r--r--    1 root     root        1.3K Sep 20 21:33 101.0W_Ku-band_113ch_1tp_09-20-2025_21-33-30.xml
-rw-r--r--    1 root     root        1.3K Sep 20 21:35 101.0W_Ku-band_113ch_1tp_09-20-2025_21-35-47.xml
-rw-r--r--    1 root     root        1.3K Sep 20 21:41 101.0W_Ku-band_113ch_1tp_09-20-2025_21-41-28.xml
-rw-r--r--    1 root     root        1.3K Sep 20 21:51 101.0W_Ku-band_113ch_1tp_09-20-2025_21-51-27.xml
-rw-r--r--    1 root     root        1.3K Sep 20 22:27 101.0W_Ku-band_113ch_1tp_09-20-2025_22-27-22.xml
-rw-r--r--    1 root     root        1.3K Sep 20 22:30 101.0W_Ku-band_113ch_1tp_09-20-2025_22-30-43.xml
-rw-r--r--    1 root     root        1.3K Sep 21 21:14 101.0W_Ku-band_113ch_1tp_09-21-2025_21-14-35.xml
-rw-r--r--    1 root     root        1.3K Oct 28 09:07 101.0W_Ku-band_114ch_1tp_10-28-2025_09-07-08.xml
-rw-r--r--    1 root     root        1.3K Sep 20 15:39 101.0W_Ku-band_11ch_1tp_09-20-2025_15-39-59.xml
-rw-r--r--    1 root     root        1.3K Sep 20 19:20 101.0W_Ku-band_11ch_1tp_09-20-2025_19-20-11.xml
-rw-r--r--    1 root     root        1.3K Sep 20 20:21 101.0W_Ku-band_11ch_1tp_09-20-2025_20-21-41.xml
-rw-r--r--    1 root     root        1.3K Sep 20 21:00 101.0W_Ku-band_11ch_1tp_09-20-2025_21-00-27.xml
-rw-r--r--    1 root     root        1.3K Sep 20 21:05 101.0W_Ku-band_11ch_1tp_09-20-2025_21-05-43.xml
-rw-r--r--    1 root     root        1.3K Sep 20 21:09 101.0W_Ku-band_11ch_1tp_09-20-2025_21-09-03.xml
-rw-r--r--    1 root     root        1.3K Sep 20 21:37 101.0W_Ku-band_11ch_1tp_09-20-2025_21-37-25.xml
-rw-r--r--    1 root     root       16.4K Sep 20 20:42 101.0W_Ku-band_166ch_16tp_09-20-2025_20-42-15.xml
-rw-r--r--    1 root     root       16.5K Sep 21 00:20 101.0W_Ku-band_168ch_16tp_09-21-2025_00-20-13.xml
-rw-r--r--    1 root     root       16.6K Oct 28 08:21 101.0W_Ku-band_168ch_16tp_10-28-2025_08-21-59.xml
-rw-r--r--    1 root     root        1.3K Sep 20 23:06 101.0W_Ku-band_17ch_1tp_09-20-2025_23-06-45.xml
-rw-r--r--    1 root     root        1.3K Sep 20 23:10 101.0W_Ku-band_17ch_1tp_09-20-2025_23-10-08.xml
-rw-r--r--    1 root     root        1.3K Sep 20 23:32 101.0W_Ku-band_17ch_1tp_09-20-2025_23-32-53.xml
-rw-r--r--    1 root     root        1.3K Sep 20 23:38 101.0W_Ku-band_17ch_1tp_09-20-2025_23-38-48.xml
-rw-r--r--    1 root     root        1.3K Sep 21 00:07 101.0W_Ku-band_17ch_1tp_09-21-2025_00-07-55.xml
-rw-r--r--    1 root     root        1.3K Sep 21 06:43 101.0W_Ku-band_17ch_1tp_09-21-2025_06-43-21.xml
-rw-r--r--    1 root     root        1.3K Sep 21 07:52 101.0W_Ku-band_17ch_1tp_09-21-2025_07-52-39.xml
-rw-r--r--    1 root     root        1.3K Sep 21 20:51 101.0W_Ku-band_17ch_1tp_09-21-2025_20-51-03.xml
-rw-r--r--    1 root     root        1.6K Sep 21 19:33 101.1W_C-band_16ch_1tp_09-21-2025_19-33-04.xml
-rw-r--r--    1 root     root        1.6K Sep 30 21:51 101.1W_C-band_16ch_1tp_09-30-2025_21-51-29.xml
-rw-r--r--    1 root     root      191.2K Oct  8 02:05 105.1W_C-band_2097ch_18tp_10-08-2025_02-05-01.xml
-rw-r--r--    1 root     root        2.3K Oct 30 11:42 105.1W_C-band_24ch_1tp_10-30-2025_11-42-42.xml
drwxrwxr-x    2 root     root        4.0K Apr 23  2025 105w-pid-test
-rw-r--r--    1 root     root       24.3K Sep 29 00:03 117.0W_Ku-band_296ch_30tp_09-29-2025_00-03-01.xml
-rw-r--r--    1 root     root        5.6K Oct 26 08:33 127.1W_C-band_63ch_7tp_10-26-2025_08-33-59.xml
-rw-r--r--    1 root     root        9.3K Oct 25 11:55 133.1W_C-band_113ch_9tp_10-25-2025_11-55-54.xml
-rw-r--r--    1 root     root        3.0K Oct 20 10:37 87.1W_Ku-band_11ch_12tp_10-20-2025_10-37-31.xml
-rw-r--r--    1 root     root        3.2K Oct 18 13:20 87.1W_Ku-band_13ch_13tp_10-18-2025_13-20-09.xml
-rw-r--r--    1 root     root        3.6K Oct 20 11:02 87.1W_Ku-band_19ch_13tp_10-20-2025_11-02-07.xml
-rw-r--r--    1 root     root        3.7K Oct 23 12:36 87.1W_Ku-band_20ch_14tp_10-23-2025_12-36-10.xml
-rw-r--r--    1 root     root        2.0K Oct 28 19:45 87.1W_Ku-band_4ch_9tp_10-28-2025_18-45-39.xml
-rw-r--r--    1 root     root         735 Oct 17 20:20 89.1W_C-band_1ch_1tp_10-17-2025_20-20-33.xml
-rw-r--r--    1 root     root         734 Oct 19 11:03 89.1W_C-band_1ch_1tp_10-19-2025_11-03-36.xml
-rw-r--r--    1 root     root        1.5K Oct 14 17:04 89.1W_C-band_2ch_6tp_10-14-2025_17-04-30.xml
-rw-r--r--    1 root     root        1.7K Nov  6 20:49 89.1W_C-band_4ch_7tp_11-06-2025_20-49-06.xml
-rw-r--r--    1 root     root        1.7K Oct 17 20:19 89.1W_C-band_5ch_6tp_10-17-2025_20-19-14.xml
-rw-r--r--    1 root     root        1.7K Oct 17 20:24 89.1W_C-band_5ch_6tp_10-17-2025_20-24-53.xml
-rw-r--r--    1 root     root        1.7K Oct 25 09:28 89.1W_C-band_8ch_4tp_10-25-2025_09-28-22.xml
-rw-r--r--    1 root     root         512 Oct 19 13:55 91.0W_Ku-band_Scan-Report_19-10-2025_13-55-55
-rw-r--r--    1 root     root       14.5K Nov  8 11:32 97.1W_C-band_160ch_11tp_11-08-2025_11-32-03.xml
-rw-r--r--    1 root     root       11.4K Sep 26 00:04 99.2W_Ku-band_107ch_18tp_09-26-2025_00-04-10.xml
drwxrwxr-x    2 root     root       26.9M Sep 20 00:54 Archive
drwxr-xr-x    2 root     root        4.0K Apr 24  2024 Factory Driver Test
drwxr-xr-x    4 root     root        4.0K Apr 22  2024 OpenATV
drwxr-xr-x    4 root     root        4.0K Apr 22  2024 OpenVix
-rw-r--r--    1 root     root        7.9K Oct 25 20:16 _ATSC_51ch_35tp_10-25-2025_20-16-08.xml
-rw-r--r--    1 root     root        8.2K Nov  3 12:08 _ATSC_57ch_35tp_11-03-2025_11-08-38.xml
-rw-r--r--    1 root     root        8.3K Sep 21 21:43 _ATSC_58ch_35tp_09-21-2025_21-43-00.xml
-rw-r--r--    1 root     root         985 Sep 20 01:43 _ATSC_6ch_1tp_09-20-2025_01-43-24.xml
-rw-r--r--    1 root     root         987 Oct 20 00:28 _ATSC_6ch_1tp_10-19-2025_23-28-43.xml
drwxrwxr-x    2 root     root        4.0K Apr 22  2024 sf8008-Supreme
root@sf8008:~#
 
... Just change line 255 and 256 in the attached file.

Original lines:
Python:
                        if os.path.exists("/media/usb/ServiceScan"):
                            self.xml_dir = "/media/usb/ServiceScan"

As an example, change to:
Python:
                        if os.path.exists("/media/MASTER/ServiceScan"):
                            self.xml_dir = "/media/MASTER/ServiceScan"
Got it working! I edited 'usb' to 'MASTER'. The reports are now writing into ServiceScan in MASTER. And I can use Dream-Explorer plugin to review the scans using just my remote as I used to do. Very convenient.
 
I'm curious why the SNR values are all wrong in the ServiceScan reports? For example, attached shows SNR=2.13 or 2.18. But the transponder was actually SNR 9.7 dB as reported by Signal Finder.
Each of the various drivers for Edision output a different value that has to be calibrated. This has been done before, then an addition or upgrade causes problems. Put in a simple way, time is needed to sort this. At least it can be fixed.


The backup completed this morning. It reported taking 33.35 minutes. I probably never waited long enough before.
The Backupsuite works. It is that simple. What Backupsuite does is not very complex, but to make it work correctly took a very talented individual. I would allow that it is possible where Backupsuite would work on one receiver and not another due to a coding issue, but that is not very likely.

Two things will greatly influence Backupsuite.
(1) Device that will be written to. Cheap usb drives are usually junk. Old drives may not work the same way they used to work. Make sure you have at least a decent quality drive for Backupsuite to use as there are thousands of files that have to be copied. A slow or compromised drive will add considerable time, may cause the process to fail, or even cause a No Boot situation when being reinstalled in the receiver. Junk In = Junk Out!
(2) Files that are being backed up. In general people are lazy and will use auto restore repeatedly when loading new images. Or they will simply have a lot of things installed that causes bloat. Backupsuite shows the size of file to be backed up and also shows other information that few users ever look at.

The Bottom Line here is what is being backed up as compared to what it is being backed up ON. If you have a bunch of junk to backup and are using a compromised drive to write the junk to, then the backup process will run for a long time. It's that simple.

Here is a backup starting on my OSMIo4k today:
MIO-backup-start-0251109141948.webp

And here is the backup completed some minutes later:
mio-backup-complete_20251109142534.webp

I do not have a thousand dollar usb drive, but it is working correctly. Check the two things mentioned above and study the screenshot examples. Let me know if you continue to have backup problems and we will look at more in depth. But it stands to reason if it works for me, it should work for you.
 
Each of the various drivers for Edision output a different value that has to be calibrated. This has been done before, then an addition or upgrade causes problems. Put in a simple way, time is needed to sort this. At least it can be fixed.
For comparison, I did blind scans using the No T2MI (my favourite), the T2MI and the T2MI Low SR drivers. The No T2MI driver showed a low reading as shown in my last message, and the T2MI and T2MI Low SR drivers showed very high readings around 60 dB. So I'll stick with my favourite for now since it's the fastest and most accurate in my experience.
The Backupsuite works...
I am using a USB memory stick (SanDisk 3.2Gen1 w/113GB free) only temporarily until I decide on and order an external USB drive. It's for backup and to timeshift programs which I erase after watching. The first drive ordered was damaged in transit, returned and could not be replaced by the seller. So I'm back to square one. I won't be doing more backups until I get my permanent drive. I just wanted to have something as a backup in the interim.
 
IMO, you need to see what you are backing up. Backupsuite shows this at the start. If you are trying to backup 600-800 MB then find out WHY. I think my backups are usually less than 500MB. This is something to look at. A drive is a moot point if you are backing up garbage. That should be a very capable backup drive you have, and it is also possible the usb port on the receiver is causing a bottleneck. Maybe try a different usb port.
 
IMO, you need to see what you are backing up...
Backupsuite reports backup size is 669 MB. I notice that rootfs.tar in the media/bi folder is almost 102 GB. I keep one downloaded image at 145 GB. I have two fullbackups that each include a rootfs.tar at 144 GB and 156 GB respectively. No reason to keep two perhaps. I only need to keep one image backup instead of two. The osmio4kplus folder shows a 156 GB rootfs.tar (again). Maybe the same one as above. I suppose these very large files don't get backed up if the USB backup is only 669 MB.

I don't mind waiting for a longer backup if I know it's working. I just go away and do something else. Even with a small memory stick, there's still lots of free space. And the hope is we'll never need to use the backups anyway. When I do a new major installation like TNAP 6, I always do it without restoring old stuff. I create satellite scans fresh and the bouquets too to help clean things up occasionally. The new Copy to a Bouquet feature makes this much easier.
 
Pardon me if this has already been discussed: I am unable to set https for webif under TNAP 6. I turn it on and then save but it doesn't retain the setting. The webif config is the same as for TNAP 5.1 and https works fine on 5.1 but https won't set on TNAP 6. http works fine on TNAP 6 though.
 
There are about 35 versions that have been released for TNAP 6. Which version are you running? (Menu--->Information--->About).
Need the Build Date and Last update

Also, what are you trying to do with either HTTP or HTTPS in OpenWebif? I think turning either one of these settings ON opens a port to the World when you connect to the Internet.
 
There are about 35 versions that have been released for TNAP 6. Which version are you running? (Menu--->Information--->About).
Need the Build Date and Last update

Also, what are you trying to do with either HTTP or HTTPS in OpenWebif? I think turning either one of these settings ON opens a port to the World when you connect to the Internet.
Build date 2018-03-09
Last update 2025-11-13

My osmios are behind a router so they're not open to the WAN except via my personal VPN. If I do want to connect to the boxes via the WAN I'll be using a personal VPN server that is running on my router.
 
It gives me an insecure page, but it works:
https-openwebif- 2025-11-20 22-45-03.webp
Maybe it needs a certificate installed for the browser to declare it "secure"?
 
We have to install those certificates for our websites. And I am sort of mixed on whether you need an elaborate HTTPS certificate for a FTA receiver. Internet security in general is something that has to be dealt with our websites too, and I know what works or seems to work for them. The idea of taking a router installed VPN and opening your entire network with it is not something I am even remotely interested in doing because I see it as a security liability waiting to happen.

Instead, put the VPN on the FTA receiver, then if your security fails, pretty much only the FTA receiver is compromised. If the VPN is installed on the router, then the entire network, every computer, every device, can be compromised. So if you want, add a self signed certificate or even purchase one. But I do not see HTTPS providing much more security over HTTP when using a correctly installed VPN. Running the firewall would be different.

AI's make mistakes, but they are pretty knowledgeable in security. A pretty lengthy read of the AI's point of view in the VPN-HTTPS security area is attached. The AI estimates maybe 5% more security using HTTPS and mostly does not suggest using it. The attached report is generated using a paid AI that is actually working on our VPN project. There is also a bit of overhead with HTTPS when compared to HTTP which is something else to consider. Again, using the firewall instead of the VPN would IMO be different.
 

Attachments

The HTTPS certificate would probably only be needed if you do not want the login aggravation. The HTTPS will still work without the certificate, and the we browser should only complain about it one time.

With the wireguard-tnap VPN installed on the receiver, I use neither HTTP or HTTPS in the OpenWebif menus. Both are set to off. Once the phone or remote computer has wireguard turned on, it is like being on your local network. Simply type the ip address into the web browser and access webif. Exact same procedure as being on the local network.

The wireguard-tnap VPN is set by default to access anything on your network using openwebif, but you are not going to access much except maybe another FTA receiver that is on the local network and maybe some shares if you have them setup. The wireguard-tnap VPN is Free and runs very well.
Screenshot_20251121_084933_Chrome.webp
 
Here is a screencap of the wireguard-tnap VPN being used to access the MIO receiver on the local network.
The wireguard-tnap VPN is installed on the SF8008, so the connection to the MIO receiver runs thorugh the SF8008 in this example.
Screenshot_20251121_093135_Chrome.webp
 

Attachments

  • afterSave.webp
    afterSave.webp
    33.8 KB · Views: 6
  • beforeSave.webp
    beforeSave.webp
    45.5 KB · Views: 5
  • osmioInfo.webp
    osmioInfo.webp
    57.4 KB · Views: 3
HTTPS works. It should work for you too....
Attach your receiver's settings file and let's see how things are set. (/etc/enigma2/settings)

Also see if there are any software updates for the receiver (Menu--->Setup--->Software update).
 
HTTPS Is active in your settings file:
config.OpenWebif.https_enabled=True
config.OpenWebif.vpn_access=True
config.OpenWebif.webcache.screenshot_refresh_auto=true
config.OpenWebif.webcache.screenshot_refresh_time=3
config.OpenWebif.webcache.theme=dark-hive
config.OpenWebif.webcache.zapstream=true


Most likely reason HTTPS is not working for you: Your system does not have the certificate files (/etc/enigma2/key.pem and /etc/enigma2/cert.pem).

Carefully check for these files and see if they are missing: /etc/enigma2/key.pem and /etc/enigma2/cert.pem

Possible causes for these files to be missing:
Deleted the certificate files
Restored settings from backup without certificate files
Edited settings file manually without going through UI
System has permission issues preventing certificate creation
Fresh install where certificates were never generated

Check and see if those two files exist...
 
Back
Top