Lemmy Support

4762 readers

12 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

dessalines@lemmy.ml

Error when upgrade to 0.18 (lemmy.ml)

submitted 2 years ago* (last edited 2 years ago) by skariko@lemmy.ml to c/lemmy_support@lemmy.ml

6 comments fedilink hide all child comments

hi, I installed a year ago lemmy via Ansible, then all the upgrades I always did by changing only the docker-compose.yml file.

Today I tried to upgrade from version 0.17.4 to 0.18 by changing the docker-compose.yml file but the site doesn't work.

The only error I have is:

Starting http server at 0.0.0.0:8536
lemmy_1 | the thread 'actix-rt|system:0|arbiter:0' panicked for 'No auth header for picture access', crates/routes/src/images.rs:138:8
lemmy_1 | note: run with environment variable `RUST_BACKTRACE=1` to display a backtrace
lemmy_1 | thread 'actix-rt|system:0|arbiter:0' panicking about 'No auth header for picture access', crates/routes/src/images.rs:138:8
lemmy_1 | thread 'actix-rt|system:0|arbiter:0' panicking over 'No auth header for picture access', crates/routes/src/images.rs:138:8

Thanks.

top 3 comments

sorted by: hot top controversial new old

[–] mxh@lemmy.mxh.nu 1 points 2 years ago (1 children)

The lemmy-ansible repository has quite a few commits over the last year other than just bumping the version. Maybe try a git pull first?

[–] skariko@lemmy.ml 2 points 2 years ago* (last edited 2 years ago) (1 children)

I actually only used Ansible for the first installation, all subsequent ones I manually updated only the docker file and following the various instructions that were given only in this update it didn't work.

If it helps I can post my current configuration file docker-compose.yml

edit:

maybe I need to try again to do an update through Ansible now?

Since it had always worked to update the docker-compose.yml file it seemed easier and more functional to do it this way but I don't want to think that maybe the installation is now "tied" to Ansible.

[–] skariko@lemmy.ml 1 points 2 years ago* (last edited 2 years ago)

It seems to have been resolved: the problem was the private instance setting, as soon as I edited in the database and it worked again 🙈

load more comments