Problems with new version

[spukijcd]

Thanks for the new version. I am also backing up to gdrive with rclone and that works. The funny thing is that the CLOUD_REMOTE is only working with the rclone name alone. I am putting the path in the CLOUD_REMOTE_PATH and it is working. To be honest I don't understand that we needs both.
My problem is that then I try to restore it doesnt prompt me to use primary or cloud backups. I only get access to the primary bacckups
Cheers

Jens

[tis24dev]

OK, thank you for letting me know. I'll check it out right away.

[tis24dev]

You're right, we saw the big one, we've fixed it now.

We await your confirmation feedback, thank you for reporting it!

[spukijcd]

Thanks Now I can choose the cloud storage but it cant find any backups. I attached my log file because I also got some strange errors. By the way. I tried to restore with the old version with a dummy proxmox installation. I restored everything succesfully but the hostname and ip was not changed. Is that not part of the backup ? Thanks in advance. Cheers Jens

…

________________________________ Fra: tis24dev ***@***.***> Sendt: 5. december 2025 16:12 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) You're right, we saw the big one, we've fixed it now. We await your confirmation feedback, thank you for reporting it! — Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N7VOBRBGJSJ7MEPXS34AGOHLAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJXGM3TMNA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tis24dev]

Hi, I have rewritten the logic and implemented new controls and checks.
Let me know if this has solved the problem you reported to me.

For a more thorough check, you can use:

proxsave --restore --cli -log-level debug

[spukijcd]

Thanks When I run the proxsave --restore I get this: [cid:3163914c-3018-4773-be9d-c5e75001d8d5]

…

________________________________ Fra: tis24dev ***@***.***> Sendt: 5. december 2025 20:24 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) Hi, I have rewritten the logic and implemented new controls and checks. Let me know if this has solved the problem you reported to me. For a more thorough check, you can use: proxsave --restore --cli -log-level debug — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5NZ3D4GGDAOSFC5P3D34AHLYPAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJXGU4TIMI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tis24dev]

To better understand what’s happening, could you please run this full command and send me the complete output as text (copy/paste), rather than a screenshot?

proxsave --restore --cli --log-level debug

If any log file is generated, please also attach it or paste its contents. This will help me pinpoint exactly where the restore process is failing.

[tis24dev]

if you have telegram:

https://t.me/tis24dev

your screenshot isn't visible here

[spukijcd]

I dont use telegram I attached what you asked me to do. I also attached the log file from the backup command proxsave. Don't you have the same problems. I can see the backup tar file both on gdrive and on local storage but unable to start a restore.

…

________________________________ Fra: tis24dev ***@***.***> Sendt: 5. december 2025 21:46 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) if you have telegram: https://t.me/tis24dev your screenshot isn't visible here — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N2QVEIG66S2IPWRXQL4AHVJPAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJXGY2DIMY>. You are receiving this because you authored the thread.Message ID: ***@***.***> ***@***.***:~# proxsave --restore --cli -log-level debug =========================================== ProxSave - Go Version Version: 0.11.8 Build Signature: 03e2891* (2025-12-05T20:21:14+01:00) hash=00a8b84ce8189c9d =========================================== Detecting Proxmox environment... ✓ Proxmox Type: pve Version: 9.0.9 Loading configuration from: /opt/proxsave/configs/backup.env ✓ Configuration loaded successfully Restore log: /tmp/proxsave/restore-proxmox1-20251206-001533.log [2025-12-06 00:15:33] INFO Restore log: /tmp/proxsave/restore-proxmox1-20251 206-001533.log [2025-12-06 00:15:33] DEBUG Update check: current version (0.11.8) is up to d ate (latest: 0.11.8) [2025-12-06 00:15:33] INFO CPU profiling enabled: /mnt/pve/tis24dev-backup/l og/cpu-proxmox1.lan-20251206-001533.pprof [2025-12-06 00:15:33] INFO Environment: pve 9.0.9 [2025-12-06 00:15:33] INFO Backup enabled: true [2025-12-06 00:15:33] INFO Debug level: DEBUG [2025-12-06 00:15:33] INFO Compression: xz (level 9, mode ultra) [2025-12-06 00:15:33] INFO Base directory: /opt/proxsave (configured in back up.env) [2025-12-06 00:15:33] INFO Configuration file: /opt/proxsave/configs/backup. env (default path) [2025-12-06 00:15:33] DEBUG Identity: detected 36 MAC addresses (primary: 06: 6d:3e:2b:e7:40) [2025-12-06 00:15:33] DEBUG Identity: loaded existing server ID 4262020897061 042 from /opt/proxsave/identity/.server_identity [2025-12-06 00:15:33] INFO Server ID: 4262020897061042 [2025-12-06 00:15:33] INFO Server MAC Address: 06:6d:3e:2b:e7:40 [2025-12-06 00:15:33] INFO Server Telegram: Telegram disabled [2025-12-06 00:15:33] STEP Security preflight checks [2025-12-06 00:15:33] DEBUG Security options: auto_fix=true, auto_update_hash es=true, continue_on_issues=false, check_network=false, firewall=false, open_por ts=false, suspicious_processes=7, safe_bracket=13 [2025-12-06 00:15:33] INFO Checking dependencies... [2025-12-06 00:15:33] DEBUG Dependency tar: present (tar at /usr/bin/tar) - r equired for archive verification and bundle handling [2025-12-06 00:15:33] DEBUG Dependency xz: present (xz at /usr/bin/xz) - comp ression type set to xz [2025-12-06 00:15:33] DEBUG Dependency rclone: present (rclone at /usr/bin/rc lone) - cloud storage uploads enabled [2025-12-06 00:15:33] DEBUG Dependency sendmail: present (sendmail at /usr/sb in/sendmail) - email relay fallback to sendmail enabled [2025-12-06 00:15:33] DEBUG Dependency zpool: present (zpool at /usr/sbin/zpo ol) - ZFS configuration collection enabled [2025-12-06 00:15:33] DEBUG Dependency zfs: present (zfs at /usr/sbin/zfs) - ZFS configuration collection enabled [2025-12-06 00:15:33] DEBUG Dependency pveversion: present (pveversion at /us r/bin/pveversion) - Proxmox VE command availability [2025-12-06 00:15:33] DEBUG Dependency pvecm: present (pvecm at /usr/bin/pvec m) - PVE cluster management command [2025-12-06 00:15:33] INFO Dependencies check completed: all required depend encies available [2025-12-06 00:15:33] INFO Security checks completed: 0 warning(s), 0 error( s) [2025-12-06 00:15:33] INFO Restore mode enabled - starting CLI workflow... =========================================== ProxSave - Go - 03e2891* (2025-12-05T20:21:14+01:00) hash=00a8b84ce8189c9d =========================================== EXTRA STEP - IF YOU FIND THIS TOOL USEFUL AND WANT TO THANK ME, A COFFEE IS ALWAYS WELCOME! https://buymeacoffee.com/tis24dev Commands: proxsave (alias: proxmox-backup) - Start backup --help - Show all options --dry-run - Test without changes --install - Re-run interactive installation/setup --new-install - Wipe installation directory (keep env/identity) then run installer --env-migration - Run installer and migrate legacy Bash backup.env to Go template --env-migration-dry-run - Preview installer/migration without writing files --upgrade - Update proxsave binary to latest release (no config changes) --newkey - Generate a new encryption key for backups --decrypt - Decrypt an existing backup archive --restore - Run interactive restore workflow (select bundle, decrypt if needed, apply to system) --upgrade-config - Upgrade configuration file using the embedded template (run after installing a new binary) --support - Run backup in support mode (force debug log level and send email with attached log to ***@***.***) PANIC: runtime error: invalid memory address or nil pointer dereference panic: runtime error: invalid memory address or nil pointer dereference goroutine 1 [running]: runtime/debug.Stack() /opt/hostedtoolcache/go/1.25.5/x64/src/runtime/debug/stack.go:26 +0x5e main.run.func2() /home/runner/work/proxsave/proxsave/cmd/proxsave/main.go:78 +0x48 panic({0x949460?, 0xed3f20?}) /opt/hostedtoolcache/go/1.25.5/x64/src/runtime/panic.go:783 +0x132 internal/sync.(*Mutex).Lock(...) /opt/hostedtoolcache/go/1.25.5/x64/src/internal/sync/mutex.go:63 sync.(*Mutex).Lock(...) /opt/hostedtoolcache/go/1.25.5/x64/src/sync/mutex.go:46 github.com/tis24dev/proxsave/internal/logging.(*Logger).logWithLabel(0x0, 0x3, {0x0, 0x0}, {0x0, 0x0}, {0x9ec269, 0x1d}, {0xc000256380, 0x2, ...}) /home/runner/work/proxsave/proxsave/internal/logging/logger.go:128 +0x79 github.com/tis24dev/proxsave/internal/logging.(*Logger).log(...) /home/runner/work/proxsave/proxsave/internal/logging/logger.go:124 github.com/tis24dev/proxsave/internal/logging.(*Logger).Warning(...) /home/runner/work/proxsave/proxsave/internal/logging/logger.go:259 github.com/tis24dev/proxsave/internal/orchestrator.discoverRcloneBackups({0xb3ba40, 0xc0003b0150}, {0xc0003ac4c0?, 0x17?}, 0x0) /home/runner/work/proxsave/proxsave/internal/orchestrator/backup_sources.go:140 +0x7e5 github.com/tis24dev/proxsave/internal/orchestrator.buildDecryptPathOptions(0xc000113108) /home/runner/work/proxsave/proxsave/internal/orchestrator/backup_sources.go:55 +0x32b github.com/tis24dev/proxsave/internal/orchestrator.selectDecryptCandidate({0xb3b9d0, 0xc0000225f0}, 0xc0007080c0, 0xc0002568f0?, 0xc0002841e0) /home/runner/work/proxsave/proxsave/internal/orchestrator/decrypt.go:174 +0x45 github.com/tis24dev/proxsave/internal/orchestrator.prepareDecryptedBackup({0xb3b9d0, 0xc0000225f0}, 0xc0007080c0, 0xc000256a00?, 0xc0002841e0, {0xb3420c, 0x6}) /home/runner/work/proxsave/proxsave/internal/orchestrator/decrypt.go:590 +0x38 github.com/tis24dev/proxsave/internal/orchestrator.RunRestoreWorkflow({0xb3b9d0, 0xc0000225f0}, 0xc000113108, 0xc0002841e0, {0xb3420c, 0x6}) /home/runner/work/proxsave/proxsave/internal/orchestrator/restore.go:41 +0x1cb main.run() /home/runner/work/proxsave/proxsave/cmd/proxsave/main.go:704 +0x315d main.main() /home/runner/work/proxsave/proxsave/cmd/proxsave/main.go:52 +0x13

[tis24dev]

Hi, I've made some changes to the rules, added debugging, and migrated the logic.
Now it works.

Run:

proxsave --upgrade

proxsave --restore --cli --log-level debug

I look forward to your feedback!

[spukijcd]

Thanks Now it is working, but I still get some errors and warnings then I backup I attached: 1. The log from proxsave --restore --cli --log-level debug command 2. The log from proxsave command 3. The status mail Does a restore also change hostname and ip address Cheers Jens

…

________________________________ Fra: tis24dev ***@***.***> Sendt: 6. december 2025 10:35 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) Hi, I've made some changes to the rules, added debugging, and migrated the logic. Now it works. Run: proxsave --upgrade proxsave --restore --cli --log-level debug I look forward to your feedback! — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N7CBN7II7IEB2WT2AD4AKPMTAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJXHEYDSNA>. You are receiving this because you authored the thread.Message ID: ***@***.***> PVE Backup Report - WARNING proxmox1.lan - 2025-12-06 11:21:29 Backup completed with warnings Local Storage ✅ 6/- backups 530.33 GB 6.70 TB free (7.2% used) Secondary Storage ➖ 0/15 backups Cloud Storage ✅ 7/- backups Backup Details Backup File proxmox1.lan-backup-20251206-112129.tar.xz.bundle.tar File Size 330.0 KiB Included Files 729 Missing Files 0 Duration N/A Compression Ratio 66.48 Compression Type xz (level: 9) Backup Mode ultra Server MAC Address 06:6d:3e:2b:e7:40 Server ID 4262020897061042 Telegram Status N/A Local Path /mnt/pve/tis24dev-backup Cloud Storage gdrive Error and Warning Summary Total Issues: 9 Errors: 3 Warnings: 6 Problem Type Count : Attempt 1/3 failed with 1 errors and: directory not found ERROR 1 : Attempt 2/3 failed with 1 errors and: directory not found ERROR 1 : Attempt 3/3 failed with 1 errors and: directory not found ERROR 1 /mnt/pve/tis24dev-backup [cifs] does not support ownership changes; chown/chmod will be skipped WARNING 1 Backup will continue, but Cloud storage may not be updated WARNING 1 Cloud disk space check failed (gdrive): no such file or directory (non-blocking) WARNING 1 Cloud disk space check failed (non-blocking): Cloud disk space check failed (gdrive): no such file or directory WARNING 1 Network filesystem cifs does NOT support Unix ownership WARNING 1 gdrive [rclone-gdrive] does not support ownership changes; chown/chmod will be skipped WARNING 1 Full log available at: /mnt/pve/tis24dev-backup/log/backup-proxmox1.lan-20251206-112129.log This is an automated message from the Proxmox Backup Script. Generated on 2025-12-06 11:21:29 by backup script v0.11.9

[tis24dev]

OK, I've read your logs and made some improvements and fixes. Your user experience should now be better.

PS: IP and hostname changes require a system restart to take effect.

Please give me your feedback

[tis24dev]

Hello! The new release should resolve all the issues you reported.

I look forward to your feedback!

https://github.com/tis24dev/proxsave/releases/tag/v0.11.11

[spukijcd]

Hello Thanks Now I can't do any backup because of a write permission error. Cheers Jens

…

________________________________ Fra: tis24dev ***@***.***> Sendt: 6. december 2025 22:18 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) Hello! The new release should resolve all the issues you reported. I look forward to your feedback! https://github.com/tis24dev/proxsave/releases/tag/v0.11.11 — Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N625BODXBGN2DICWSD4ANB3ZAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJYGIZTGOA>. You are receiving this because you authored the thread.Message ID: ***@***.***> [2025-12-08 14:39:29] STEP Pre-backup validation checks [2025-12-08 14:39:29] ERROR no write permission in /mnt/pve/tis24dev-backup: open /mnt/pve/tis24dev-backup/.permission_test_1374926: input/output error [2025-12-08 14:39:29] INFO ✓ Directories: All required directories exist [2025-12-08 14:39:29] INFO ✓ Disk Space: Sufficient disk space on all configured destinations [2025-12-08 14:39:29] ERROR ✗ Permissions: no write permission in /mnt/pve/tis24dev-backup: open /mnt/pve/tis24dev-backup/.permission_test_1374926: input/output error [2025-12-08 14:39:29] ERROR Pre-backup checks failed: permissions check failed: no write permission in /mnt/pve/tis24dev-backup: open /mnt/pve/tis24dev-backup/.permission_test_1374926: input/output error

[tis24dev]

The permissions message is misleading, and I am now correcting it.

The final part of the message:
open /mnt/pve/tis24dev-backup/.permission_test_1374926: input/output error
is the error returned by the kernel (EIO).
EIO does not indicate a permissions problem, but an I/O problem on the filesystem/mount:
remote storage in error or temporarily unreachable,
mount “broken” or in an inconsistent state,
hardware or backend problems (e.g., NFS/SMB/ceph/zfs over iSCSI responding with EIO).
Therefore: at the system level, there was a real I/O error at that moment. The text “no write permission” is just the generic label that proxsave puts on any os.Create error, and here it is misleading.

https://github.com/tis24dev/proxsave/releases/tag/v0.11.13

run

proxsave --upgrade

[spukijcd]

Hi That sound strange because the script worked only with warnings but now its errors and no backups are taken. I didnt do anything but run the command proxsave --upgrade. Cheers Sendt fra Outlook til Android<https://aka.ms/AAb9ysg>

…

________________________________ From: tis24dev ***@***.***> Sent: Monday, December 8, 2025 4:26:11 PM To: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Subject: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) The permissions message is misleading, and I am now correcting it. The final part of the message: open /mnt/pve/tis24dev-backup/.permission_test_1374926: input/output error is the error returned by the kernel (EIO). EIO does not indicate a permissions problem, but an I/O problem on the filesystem/mount: remote storage in error or temporarily unreachable, mount “broken” or in an inconsistent state, hardware or backend problems (e.g., NFS/SMB/ceph/zfs over iSCSI responding with EIO). Therefore: at the system level, there was a real I/O error at that moment. The text “no write permission” is just the generic label that proxsave puts on any os.Create error, and here it is misleading. — Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N6BDB5OBE2RJGKVVL34AWKBHAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJZHA4DMMY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tis24dev]

I don't understand what you've done now. Where are you at?

I explained that the error comes from your server and that I've improved the alerts anyway, and I asked you to update again to the latest release. Have you installed 0.11.13? You didn't tell me.

[spukijcd]

Yes I updated to ver. 0.11.13 and that was the only thing I did. Stange it comes from my server because I didnt do anything except upgrading I wrote that the only thing I did was the command proxsave --upgrade.

…

________________________________ Fra: tis24dev ***@***.***> Sendt: 8. december 2025 22:42 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) I don't understand what you've done now. Where are you at? I explained that the error comes from your server and that I've improved the alerts anyway, and I asked you to update again to the latest release. Have you installed 0.11.13? You didn't tell me. — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N6OLRX2K72XVBSQKZD4AXWFFAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRQGI2TGNI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tis24dev]

Okay, have you updated? Are you still having problems?
If you are still having problems, what kind of problems?
Please give me more information so I can understand the situation. With fragmented information, I can't help you.

[spukijcd]

Hi I were able to acces all my shares from my nas box so I couldnt see any errors. But you told me it had something to do with my server so I booted the nas and it helped so now its working. Very strange. So thanks a lot 🙂 Earlier I tried to restore my backup from my physical host to a vm. As you told me I could see in the terminal it changed ip and hostname, but I were not able to access the website. Maybe it has something to do with the nic name is not the same. I will troubleshoot and come back to you. Have you tried to make a full restore test yourself. Cheers

…

________________________________ Fra: tis24dev ***@***.***> Sendt: 9. december 2025 00:07 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) Okay, have you updated? Are you still having problems? If you are still having problems, what kind of problems? Please give me more information so I can understand the situation. With fragmented information, I can't help you. — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N7GNIYWLKZFEPPGQOT4AYABXAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRQGI4TINQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[spukijcd]

Hi Now I tried with a NFS share but still got some errors. I changed the ownership to root:root that solved the first warning. I also got this warning: Security warning: incorrect permissions on /mnt/pve/tis24dev-backup-nfs/proxmoxbackup/proxmox1 (current 75, expected 755) The funny thing is that I changed it from 755 to 75 and now I got the opposite warning. Cheers

…

________________________________ Fra: tis24dev ***@***.***> Sendt: 9. december 2025 00:07 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) Okay, have you updated? Are you still having problems? If you are still having problems, what kind of problems? Please give me more information so I can understand the situation. With fragmented information, I can't help you. — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N7GNIYWLKZFEPPGQOT4AYABXAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRQGI4TINQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tis24dev]

ProxSave automatically corrects permissions by default, so permissions should no longer be reported as incorrect on the second run.
Manual changes should not be necessary.

[spukijcd]

I have been running it a lof of times but still have some warnings Cheers

…

________________________________ Fra: tis24dev ***@***.***> Sendt: 9. december 2025 09:12 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) ProxSave automatically corrects permissions by default, so permissions should no longer be reported as incorrect on the second run. Manual changes should not be necessary. — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N7PNN6JG5E7MZPDZVT4A2AAHAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRQGU4DENQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tis24dev]

Please send me the errors that appear. In data 10 dicembre 2025 14:10:33 spukijcd ***@***.***> ha scritto:

…

I have been running it a lof of times but still have some warnings Cheers ________________________________ Fra: tis24dev ***@***.***> Sendt: 9. december 2025 09:12 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) ProxSave automatically corrects permissions by default, so permissions should no longer be reported as incorrect on the second run. Manual changes should not be necessary. — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N7PNN6JG5E7MZPDZVT4A2AAHAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRQGU4DENQ>. You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[spukijcd]

Hi Its the same warnings I have seen before around permissions. I am running the latest version. Cheers

________________________________ Fra: tis24dev ***@***.***> Sendt: 10. december 2025 14:28 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) Please send me the errors that appear. In data 10 dicembre 2025 14:10:33 spukijcd ***@***.***> ha scritto:

I have been running it a lof of times but still have some warnings Cheers ________________________________ Fra: tis24dev ***@***.***> Sendt: 9. december 2025 09:12 Til: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Emne: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) ProxSave automatically corrects permissions by default, so permissions should no longer be reported as incorrect on the second run. Manual changes should not be necessary. — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N7PNN6JG5E7MZPDZVT4A2AAHAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRQGU4DENQ>. You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N3AVDQVLZPN2SYKR2D4BANYNAVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRSGAZDMNI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tis24dev]

Hi, have you installed 0.11.14?

If you have installed 0.11.14, please copy the warning you are receiving here.

[spukijcd]

You can see the version in my log file and yes its the newest Sendt fra Outlook til Android<https://aka.ms/AAb9ysg>

…

________________________________ From: tis24dev ***@***.***> Sent: Tuesday, December 16, 2025 2:09:33 PM To: tis24dev/proxsave ***@***.***> Cc: spukijcd ***@***.***>; Author ***@***.***> Subject: Re: [tis24dev/proxsave] Problems with new version (Discussion #79) Hi, have you installed 0.11.14? If you have installed 0.11.14, please copy the warning you are receiving here. — Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGJY5N2DF5UOI3SZEL3BKML4CAAA3AVCNFSM6AAAAACOE3QF46VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRWHEZTEMI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tis24dev]

You can see the version in my log file and yes its the newest

Could you kindly send me the new log?
P.S. I do not save the logs I receive after analyzing them.