spotizerrphoenix/spotizerr-phoenix

Fork 6

Missing 'version' in data/config/main.json #1

New issue

Closed

opened 2025-11-28 03:44:46 +00:00 by Krunox · 5 comments

Krunox commented

2025-11-28 03:44:46 +00:00

Is there a fix? Or do I need to manually update the version in main.json?

2025-11-28 03:41:39 [ERROR] Configuration file not found at data/config/main.json
2025-11-28 03:41:39 [ERROR] Error during migration: Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0.
Traceback (most recent call last):
  File "/app/routes/migrations/runner.py", line 51, in run_migrations_if_needed
    MigrationV3_3_0.assert_config_version_is_3_3_0()
  File "/app/routes/migrations/v3_3_0.py", line 44, in assert_config_version_is_3_3_0
    raise RuntimeError(
RuntimeError: Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0.
2025-11-28 03:41:39 [ERROR] Database migration step failed early in startup: Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0.
Traceback (most recent call last):
  File "/app/app.py", line 35, in <module>
    run_migrations_if_needed()
  File "/app/routes/migrations/runner.py", line 51, in run_migrations_if_needed
    MigrationV3_3_0.assert_config_version_is_3_3_0()
  File "/app/routes/migrations/v3_3_0.py", line 44, in assert_config_version_is_3_3_0
    raise RuntimeError(
RuntimeError: Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0.

Is there a fix? Or do I need to manually update the version in main.json? ``` 2025-11-28 03:41:39 [ERROR] Configuration file not found at data/config/main.json 2025-11-28 03:41:39 [ERROR] Error during migration: Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0. Traceback (most recent call last): File "/app/routes/migrations/runner.py", line 51, in run_migrations_if_needed MigrationV3_3_0.assert_config_version_is_3_3_0() File "/app/routes/migrations/v3_3_0.py", line 44, in assert_config_version_is_3_3_0 raise RuntimeError( RuntimeError: Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0. 2025-11-28 03:41:39 [ERROR] Database migration step failed early in startup: Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0. Traceback (most recent call last): File "/app/app.py", line 35, in <module> run_migrations_if_needed() File "/app/routes/migrations/runner.py", line 51, in run_migrations_if_needed MigrationV3_3_0.assert_config_version_is_3_3_0() File "/app/routes/migrations/v3_3_0.py", line 44, in assert_config_version_is_3_3_0 raise RuntimeError( RuntimeError: Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0. ```

spotizerrphoenix commented

2025-11-28 05:13:20 +00:00

Owner

oh interesting is this for a fresh install? i haven't tried it yet. i did change the version so not sure if that's affecting it. works fine for me on an existing instance.

are you pulling the latest image?

thanks for reporting this, i'll have to check it out

oh interesting is this for a fresh install? i haven't tried it yet. i did change the version so not sure if that's affecting it. works fine for me on an existing instance. are you pulling the latest image? thanks for reporting this, i'll have to check it out

Krunox commented

2025-11-28 05:27:44 +00:00

Author

oh interesting is this for a fresh install? i haven't tried it yet. i did change the version so not sure if that's affecting it. works fine for me on an existing instance.

@spotizerrphoenix Yes, fresh install on another machine. My existing instance still works fine after switching to your image.

There is a similar issue at the spotizerr repo (spotizerr/spotizerr#2), but you can bypass it using the fix suggested here spotizerr/spotizerr#2 (comment)

are you pulling the latest image?

I am now using spotizerrphoenix/spotizerr:latest

> oh interesting is this for a fresh install? i haven't tried it yet. i did change the version so not sure if that's affecting it. works fine for me on an existing instance. @spotizerrphoenix Yes, fresh install on another machine. My existing instance still works fine after switching to your image. There is a similar issue at the spotizerr repo (https://lavaforge.org/spotizerr/spotizerr/issues/2), but you can bypass it using the fix suggested here https://lavaforge.org/spotizerr/spotizerr/issues/2#issuecomment-158 > are you pulling the latest image? I am now using `spotizerrphoenix/spotizerr:latest`

👍 2

spotizerrphoenix commented

2025-11-28 19:34:34 +00:00

Owner

got it, if memory serves me correctly i believe there was an issue with directory permissions before when switching to rootless.

seems like manually making the directories first is needed (to inherit correct permissions):

mkdir -p data logs downloads (in linux/mac)
touch .cache
create the .env depending on your setup
related to: spotizerr/spotizerr#4

can you give that a try and see if that works?

got it, if memory serves me correctly i believe there was an issue with directory permissions before when switching to rootless. seems like manually making the directories first is needed (to inherit correct permissions): - `mkdir -p data logs downloads` (in linux/mac) - `touch .cache` - create the `.env` depending on your setup - related to: https://lavaforge.org/spotizerr/spotizerr/pulls/4 can you give that a try and see if that works?

middaymoon commented

2025-11-28 22:55:34 +00:00

can you give that a try and see if that works?

Just tried that. No dice, getting the same error Krunox is getting above.

``` can you give that a try and see if that works? ``` Just tried that. No dice, getting the same error Krunox is getting above.

spotizerrphoenix referenced this issue from a commit

2025-11-29 20:36:52 +00:00

Merge pull request 'dev' (#1) from dev into main

spotizerrphoenix referenced this issue

2025-11-29 22:11:07 +00:00

hotfix: skip v3.3.0 migration check for fresh installs #4

spotizerrphoenix commented

2025-11-29 22:38:32 +00:00

Owner

@Krunox @middaymoon

new fix for this just merged/built: #4

repull image with the latest tag with: spotizerrphoenix/spotizerr:latest or just spotizerrphoenix/spotizerr
should fix this issue for new instances of spotizerr (existing instances remain unaffected)

will close this issue for now but give it a try and reopen if you run into anything 👍🏻

@Krunox @middaymoon new fix for this just merged/built: https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/pulls/4 - repull image with the latest tag with: `spotizerrphoenix/spotizerr:latest` or just `spotizerrphoenix/spotizerr` - should fix this issue for **new instances** of spotizerr (existing instances remain unaffected) will close this issue for now but give it a try and reopen if you run into anything 👍🏻

❤️ 1 🎉 2 🚀 2

spotizerrphoenix closed this issue

2025-11-29 22:38:55 +00:00

spotizerrphoenix self-assigned this

2025-11-29 22:39:26 +00:00