get10101/start9-itchysats-wrapper

Unable to open UI after restoring from backup

Closed this issue · 6 comments

What did I do:

  1. Install itchysats service from itchysats.s9pk
  2. Create backup of itchysats service
  3. Uninstall itchysats service
  4. Restore from backup

The restore completes and the /data is properly added, i.e. the files are correct and the service starts up correctly (checked the logs).
But the configuration does not seem to be correct, because the LAUNCH UI button points to an outdated / incorrect link. So I am unable to access the UI.

When cat /etc/nginx/sites-enabled/itchysats_main_443.conf I can see the correct address (through which I am able to access the UI).

A restart may fix this problem, i.e. the link to the UI was correct afterwards, but I also had cases where it did not, i.e. the link remained wrong.

Todo: Understand if this is a problem of how the backup+restore is configured or a different issue.

have you tested to see if this is a local browser caching issue?

have you tested to see if this is a local browser caching issue?

Thanks for the quick reply!

🤔 How is the browser cache involved here?

I press the LAUNCH UI button after the restore and the link that is opened is opened in a new tab points to a different link address than the entry configured in the nginx config file (/etc/nginx/sites-enabled/itchysats_main_443.conf).
Note: The links in the Interface section are also outdated.

I will see to reproduce the issue later and clear the cache to see if it helps. Currently afk.

Browser: Firefox

  1. Install itchysats service
  2. configure, startup
  3. create backup
  4. uninstall
  5. delete browser cookies for `embacy-..-.local
  6. refresh the tab, login
  7. restore from backup
  8. The LAUNCH UI link is still incorrect
  9. Switched to Chrome, login, same result

Clearing cookies and site data has not resolved the issue. Is that what you meant @islandbitcoin ?
I don't think it's a problem of resolving the link, but the link is actually incorrect.

I wonder if that is related to backing up the app's config - at the moment I only back up the /data folder with the app data, but not the config.

yes, clearing cookies and site data is what I meant, looks like that did not work.

Here's a video that shows the whole process and the problem:

https://drive.google.com/file/d/1IgRGCJAlP4g7_2eXxOIkAGSJSBZxeEuy/view?usp=sharing

Tried to record it in a GIF but it exceed GitHub's max file size of 10MB, so link to GDrive after all... 😬

This problem was resolved by backing up main volume and the data volume. Note that after that I still had trouble with name resolution, but that is unrelated, capture in #11