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

Local Database (with Credentials) is lost after HAOS update to 12.4 #100

Open
FrankGiesecke opened this issue Jun 19, 2024 · 17 comments
Open

Comments

@FrankGiesecke
Copy link

Problem/Motivation

I've updated my HAOS to version 12.4 - all docker containers are restarted.
After the update, all connections to EMQX where canceled with message "invalid login"
I could not log into the dashboard using my admin password.
But the default password works.
Im EMQX I could see a configured Built-In Database but without any users.

Expected behavior

The Built-In Database should survive OS updates.

Actual behavior

The admin password and the Built-In Database are gone

@whc2001
Copy link

whc2001 commented Jul 3, 2024

I just did a full backup migration to a new server (both old and new setup are Supervised), and seems like the data store of this addon is not backed up at all. After restore it's just like a new instance. I bashed into the container and used emqx ctl data import/export to recover the data from the old to the new instance. I believe if you are running HAOS the things will be much more complicated.

@allout58
Copy link

This is critical and has bitten me too

@FrankGiesecke
Copy link
Author

Are there any update to this topic?

@sinclairpaul
Copy link
Member

In summary, if the hostname changes then this would be an issue as the config appears to be placed within a directory based on it.

This explains migrations to other systems, however it doesn't explain why an OS upgrade would cause the issue.

@whc2001
Copy link

whc2001 commented Jul 17, 2024

In summary, if the hostname changes then this would be an issue as the config appears to be placed within a directory based on it.

This explains migrations to other systems, however it doesn't explain why an OS upgrade would cause the issue.

I later also found that, but trying to move the old config files info the directory of new hostname is not working for me somehow. In the end emqx ctl data import/export worked for me.

@FrankGiesecke
Copy link
Author

FrankGiesecke commented Jul 17, 2024

In summary, if the hostname changes then this would be an issue as the config appears to be placed within a directory based on it.

This explains migrations to other systems, however it doesn't explain why an OS upgrade would cause the issue.

Interesting and good to know.
But in my case, the hostname didn't change.

Is there a simple way to export/import the data from the UI to avoid dealing with docker commands in HAOS?

@whc2001
Copy link

whc2001 commented Jul 17, 2024

In summary, if the hostname changes then this would be an issue as the config appears to be placed within a directory based on it.
This explains migrations to other systems, however it doesn't explain why an OS upgrade would cause the issue.

Interesting and good to know. But in my case, the hostname didn't change.

Is there a simple way to export/import the data from the UI to avoid dealing with docker commands in HAOS?

I don't think so. The EMQX WebUI does not seem to provide this functionality.

Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Aug 17, 2024
@whc2001
Copy link

whc2001 commented Aug 17, 2024

Not stale

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Aug 18, 2024
Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Sep 17, 2024
@allout58
Copy link

Not stale

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Sep 18, 2024
Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Oct 18, 2024
@allout58
Copy link

Still needs to be addressed

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Oct 19, 2024
Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Nov 18, 2024
@allout58
Copy link

Can we make it so this doesn't keep going stale? Data loss is kinda a critical in my opinion...

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Nov 19, 2024
Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Dec 19, 2024
@whc2001
Copy link

whc2001 commented Dec 19, 2024

1

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants