Installation error with permissions “The HTTP server must have write permission”

[p-jones]

I am attempting to install FreshRSS on an up-to-date Ubuntu server.

I spin up the container with no problems using a docker compose stack in Portainer (never mind the following indenting - it is correct in the Portainer stack).

version: '3.3'
services:
    linuxserver:
        container_name: freshrss
        ports:
            - '9009:80'
        environment:
            - PUID=1000
            - PGID=1000
            - TZ=Americas/Toronto
        volumes:
            - '/home/myusername/docker/freshrss:/config'
        restart: always
        image: ghcr.io/linuxserver/freshrss

Step 2 of install, all is green except for

Any help would be much appreciated!

[Alkarex]

Hello,
ghcr.io/linuxserver/freshrss is not one of our official images.
However, I am pretty sure that if you use a Docker volume such as freshrss-data instead of your local folder /home/myusername/docker/freshrss, it should work out of the box.
If you insist on using your local folder, you need to make sure to set the correct access rights on it.

Our official images, e.g. freshrss/freshrss automatically fixes the access rights on startup.

[Alkarex]

Hello @jfromeo,
Upon restart, an image such as freshrss/freshrss will attempt to fix access rights automatically.

docker restart freshrss

Otherwise, you can try more manually with e.g.:

docker exec freshrss chown apache:www-data -R .
docker exec freshrss chmod -R g+r .
docker exec freshrss chmod -R g+w ./data/

[p-jones]

Just out of curiosity (since my FreshRSS instance is now working well thanks to @Alkarex ), I presume using docker exec freshrss… this way will be required every time that the image is updated? That is, the owner and permissions will need to be reset?

[jfromeo]

Thank you a lot for the quick help.

I restarted the docker container, but problem still occurs, so I tried setting manually the read/write permissions:

docker exec -it freshrss /bin/bash

chown apache:www-data -R .

But I got this output:

chown: invalid user: 'apache:www-data'

I listed the users inside the docker container:

cat /etc/passwd

And I only identified www-data (no apache user), so I applied the chown command to it:

chown www-data -R .

The following 2 commands also applied succesfully.

chmod -R g+r .
chmod -R g+w ./data/

I restarted it again after the changes and I could get on with the installation.

[Alkarex]

Ah, sorry, apache:www-data is for Alpine-based images, while www-data:www-data is for Debian-based images.

[jfromeo]

Ah, sorry, apache:www-data is for Alpine-based images, while www-data:www-data is for Debian-based images.

No apologies. You helped me a lot with the set up.

Thank you a lot.

[p-jones]

Understood. Thank you for taking the time to reply! I will try the official image.

…

On Jan 23, 2023, at 15:16, Alexandre Alapetite ***@***.***> wrote: Hello, ghcr.io/linuxserver/freshrss is not one of our official images. However, I am pretty sure that if you use a Docker volume such as freshrss-data instead of your local folder /home/myusername/docker/freshrss, it should work out of the box. If you insist on using your local folder, you need to make sure to set the correct access rights on it. Our official images, e.g. freshrss/freshrss automatically fixes the access rights on startup. — Reply to this email directly, view it on GitHub <#5037 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4AXANP7WZB7IVRG4GRPRVLWT3RJRANCNFSM6AAAAAAUEIR65Y>. You are receiving this because you authored the thread.

[Alkarex]

I have just made an update to better apply access permissions out-of-the-box, also on external volumes #5062