Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Challenge with data lost after "Restore backup". "Proxy Server" column. #421

Open
Francewhoa opened this issue Dec 9, 2024 · 2 comments
Labels
type-bug Bug in code or behaviour

Comments

@Francewhoa
Copy link

Francewhoa commented Dec 9, 2024

Description

I love SmartProxy. Very useful. Well done app. Easy to use. Very nice and clear user interface. Lots of automation.

We found a challenge though.

Summary

After "Restore backup". Under Proxy Profiles vertical tab. Under Always Enabled sub-vertical tab. Under Rules group. Under Proxy Server column, all data is both lost and replaced with Use Active Proxy.

Below is the same as above. But with details for those interested.

Steps to Reproduce

The steps below result in data lost. Before proceeding, I suggest taking appropriate actions.

  1. Under Proxy Servers vertical tab, add a proxy server

    1. Use this Server Name: SN Lorem►Ipsum
  2. Under Smart Profiles vertical tab, under Always Enabled sub-vertical tab, under Rules group, add a rule. Which use the SN Lorem►Ipsum you created up above

    1. On the Rule Details window, double-check that you selected the SN Lorem►Ipsum. The number 3 in this screenshot shows this.
      Screenshot-207
  3. Under Backup/ Restore vertical tab, click on Create full backup button

  4. Still under Backup/ Restore vertical tab, click on Restore backup button

  5. Go back to Smart Profiles vertical tab, under Always Enabled sub-vertical tab, under Rules group. Under Proxy Server column, all data is both lost and replaced with Use Active Proxy. This is the challenge. The number 1 in this screenshot below shows the location of this challenge.
    Screenshot-208

  6. The needed end result is that settings are restored without data lost.


Note

  • For just one entry, this is really not a big deal. But for users with thousands or hundred of entries, this data would be significant.
  • The full data is actually still into the full backup SmartProxy-FullBackup.json file. But from an end-user point of view, after a restore, the data is in fact lost under Proxy Server column. Following this, if the user does another backup, then the data is really fully lost on the next restore. Why? Because I am assuming that after the next restore, the SmartProxy-FullBackup.json file will be replaced with only Use Active Proxy. Thus, really lost.

Speculated Cause

It seems that, on restore, if a rule already exists, this somehow triggers this challenge. In other words, if the rule does not exist, this challenge can't be reproduced. Find the related temporary workaround down below to reproduce this.


Which browsers did you test this on?

Firefox

Affected browser versions

Using Firefox 133 or LibreWolf 133 or Zen 132

Affected SmartProxy versions

1.6.1

Screenshots of the problems or steps to reproduce

No response

Any additional context

For those facing this challenge, we found this temporary workaround

Steps:

  1. Before restoring a full backup, on the destination SmartProxy, delete all rule(s) that are already present into the full backup. Or, if appropriate, on the destination SmartProxy, simply delete all rules.
  2. On the destination SmartProxy, restore your full backup
  3. No data lost. Joy :)

Contributing

If needed, both me and the Ubertus.Org team would be happy to contribute beta testing and documentation. Any volunteer for a patch?

@Francewhoa
Copy link
Author

This ticket #421 seems to be a duplicate of #418 ?

@salarcode
Copy link
Owner

Thank you for your interest and the detailed report.
Yes, the issue reported in #418 has now been fixed.

I’d love to receive contributions; there’s still a lot that can be done for this project. I’m working on it in my free time, but unfortunately, I don’t have much free time left to dedicate to it. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug Bug in code or behaviour
Projects
None yet
Development

No branches or pull requests

2 participants