[BUG] paperless-ngx subpath intallation broken with uvicorn 0.26 about paperless-ngx HOT 14 CLOSED

Are you suggesting we lock unicorn to 0.25? I can’t tell if they meant for 0.26 to be a breaking change, surprising if so.

Since you presumably have a ‘bare metal’ install seems like the answer is “don’t install 0.26” in the meantime.

Perhaps some else has a better solution, but…

edit:

from paperless-ngx.

Did you notice your logs say “papeless/accounts”?

from paperless-ngx.

Unfortunately not.

from paperless-ngx.

I would say that currently using uvicorn 0.26 will cause problems in certain scenarios. In my case, I install paperless-ngx from sources on my home server (no docker).

from paperless-ngx.

We still provide the versions we know work, and if you are choosing to install something else, that really is at your own risk.

This doesn't feel like a bug, but just heads up for some future maybe bug.

from paperless-ngx.

And frankly, this seems like a user action is needed. As pointed out above, there is already a setting to configure that uvicorn setting, so this seems not like a bug. If/when we update to 0.26, we can flag that for users to know they need to take action

from paperless-ngx.

1 comment and 1 question:

• In Pipfile you do not restrict uvicorn version, so likely some people will run into trouble (non-docker folks). I have my workaround, so it's up to you to decide what you are going to do with this piece of information.
• So what should be the new configuration with uvicorn 0.26 if you want to provide paperless-ngx under https://example.com/paperless URL? I tried multiple combinations, but none of them worked..

from paperless-ngx.

• Yea, I think locking it for now will be an immediate solution for bare-metal installs like yourself.
• This is a great question and I definitely dont know the answer, I find this rather confusing. You mean you tried different options for PAPERLESS_FORCE_SCRIPT_NAME, correct? Did you also try adjusting the settings at your reverse proxy. Thats the part that I find confusing / unclear how to easily test.

from paperless-ngx.

Yes, I tried to tweak PAPERLESS_URL along with PAPERLESS_FORCE_SCRIPT_NAME and PAPERLESS_STATIC_URL. None of the combinations gave me a landing page :-( I can try experimenting a bit more, but likely we will need a patch or something..

from paperless-ngx.

If a user is following the bare metal installation instructions, they will end up with 0.25 right now anyway, so this seems pretty low priority. We can't really help users who decide not to use the versions we're specifying.

We'll just lock it for now and if anyone every actually understands the new requirement, can unlock and add documentation.

from paperless-ngx.

If a user is following the bare metal installation instructions, they will end up with 0.25 right now anyway

Thanks for clarifying that stumpy, I misunderstood that

from paperless-ngx.

Sounds fair..

from paperless-ngx.

Thanks for the report, I think this is resolved as above.

from paperless-ngx.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. See our contributing guidelines for more details.

from paperless-ngx.