[GH-ISSUE #748] cant open existing 1remote mysql db from running in visual studio #614

New issue

Closed

opened 2026-02-26 11:59:01 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 11:59:01 +03:00

Owner

Originally created by @chuckgmthompson on GitHub (Oct 31, 2024).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/748

Originally assigned to: @VShawn on GitHub.

I installed 1remote on one computer. connected to a mysql instance, and imported a bunch of connections. works fine on that installed version. on another machine I open the source code and connect to that same mysql db and I get an error:

your database is encrypted by a third-part build 1Remote_Debug, this app can not read your data correctly

I then installed 1Remote on yet another machine and connect to that mysql and see everything fine.
It just seems to be an issue if connecting from a debug environment.
Any suggestions?

Originally created by @chuckgmthompson on GitHub (Oct 31, 2024). Original GitHub issue: https://github.com/1Remote/1Remote/issues/748 Originally assigned to: @VShawn on GitHub. I installed 1remote on one computer. connected to a mysql instance, and imported a bunch of connections. works fine on that installed version. on another machine I open the source code and connect to that same mysql db and I get an error: your database is encrypted by a third-part build 1Remote_Debug, this app can not read your data correctly I then installed 1Remote on yet another machine and connect to that mysql and see everything fine. It just seems to be an issue if connecting from a debug environment. Any suggestions?

kerem

2026-02-26 11:59:01 +03:00

closed this issue
added the
question
label

kerem commented

2026-02-26 11:59:02 +03:00

Author

Owner

@VShawn commented on GitHub (Nov 1, 2024):

The issue you're experiencing is due to the version on GitHub being built with a random encryption salt , which is generated on the GitHub action server. This means that any databases created by the official release cannot be read correctly by local development builds.

If you would like to use a locally compiled version, here's the solution:

use the official release exe to export existing data, then import them using your own compiled version. Additionally, ensure that all machines are running the same locally compiled version for compatibility.

Let us know if you have any further questions!

@VShawn commented on GitHub (Nov 1, 2024): The issue you're experiencing is due to the version on GitHub being built with a random encryption salt , which is generated on the GitHub action server. This means that any databases created by the official release cannot be read correctly by local development builds. If you would like to use a locally compiled version, here's the solution: use the official release exe to export existing data, then import them using your own compiled version. Additionally, ensure that all machines are running the same locally compiled version for compatibility. Let us know if you have any further questions!

kerem referenced this issue

2026-02-28 12:04:33 +03:00

[GH-ISSUE #614] 1.0.0 BETA: Custom SFP Runners not working #1457

kerem referenced this issue

2026-03-01 17:20:23 +03:00

[GH-ISSUE #614] 1.0.0 BETA: Custom SFP Runners not working #2417

kerem referenced this issue

2026-03-13 11:23:24 +03:00

[GH-ISSUE #614] 1.0.0 BETA: Custom SFP Runners not working #3413