1.5.11 HTTP Server Error 500 (downgrade solves issue) #2893
Comments
|
please provide logs |
|
This has happened to me also. Logs posted below. I can't see anything odd in them, though |
|
is debug enabled? have you tried clearing the browser cache? any messages in browser console? |
|
I've got the same thing here. Looks like I was hit by this AND the keycloak allauth deprecation (with no breaking change in the patch notes, :( ) So I was trying to debug two things at once it turns out. Nothing notable in the logs with debug turned on. The curious bit is, once I reset my django admin pass and fixed the OIDC config, a browser with an old session was functional, but a browser that had never logged in, and a private session both gave the 500 error and landed me here. |
|
I did not mean to deprecated anything, must have been something in the changelog of django all Auth that I missed. Will take a look later |
|
Sorry for the passive aggressive response the culprit is FWIIW their changes make sense, and updating auth libraries is always a good idea in general was just cuag off guard and had to go digging Only an issue if already using Keycloak specifically, swapping was easier than I thought, but this 500 error bug made me think the oauth switch wasn't working |
|
So does that mean you got it up an working again @danieljkemp? I don't use keycloak but I had Authentik in the past but I disabled it maybe 6-9 months ago. |
|
Keycloak works with the openid_connect allauth plugin. But currently only in a tab that previously had a valid session due to the above bug? Private browser session and it gives the 500 as above and I haven't seen why in the logs (with debug on). But hey at least I am 80% sure that keycloak is working right ;) |
Keycloak was deprecated in the allauth library. |
|
Ok so has this been resolved? I cannot really help here since for me the update works fine and without any debug logs I cant see any error. If you are still having issues please set |
|
I also added a note to the changelog regarding keycloak |
@anytimesoon @nicedevil007 Are you folks using OIDC plugins? I am still seeing the issue after updating keycloak to use OIDC directly in allauth. In a session with existing cookies the page loads with no errors, but it throws the 500 in a session without a session. I don't get much from the debug logs. Things fail before they can hit an oauth provider at all This is all I get in the debug logs, nothing is seen from the keycloak side, the browser does not show any requests other than these either. |
|
I'm not using any special auth service. Just whatever is provided by tandoor. So, I don't think this was related to auth in my case. I dont have access to my laptop this week, so can't help much more than that at the moment, I'm afraid. If this issue is ongoing next week, I'll chime in again. Sorry about that |
|
I removed the OIDC part with authentik months ago, I guess more than 2-3 Updates are gone since that. <html>
<body>
<!--StartFragment--><h1 style="padding: 0px; margin: 0px; font-weight: normal; color: rgb(0, 0, 0); font-family: sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">ProgrammingError at /</h1><pre class="exception_value" style="padding: 0px; margin: 10px 0px; font-size: 1.5em; white-space: pre-wrap; word-break: break-word; font-family: sans-serif; color: rgb(87, 87, 87); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">column cookbook_space.space_theme does not exist
LINE 1: ...kbook_space"."name", "cookbook_space"."image_id", "cookbook_...
^
</pre>
Request Method: | GET
-- | --
https://xxxxxxxxxxxxx
4.2.7
ProgrammingError
column cookbook_space.space_theme does not exist LINE 1: ...kbook_space"."name", "cookbook_space"."image_id", "cookbook_... ^
/opt/recipes/venv/lib/python3.10/site-packages/django/db/backends/utils.py, line 89, in _execute
cookbook.views.views.index
/opt/recipes/venv/bin/python
3.10.13
['/opt/recipes', '/opt/recipes/venv/bin', '/usr/local/lib/python310.zip', '/usr/local/lib/python3.10', '/usr/local/lib/python3.10/lib-dynload', '/opt/recipes/venv/lib/python3.10/site-packages']
Mon, 22 Jan 2024 21:30:32 +0100
<!--EndFragment-->
</body>
</html> |
|
can you provide the container logs starting at initial boot? |
|
Sure, have to restore a backup right now because I'm testing other stuff as well. I just took the whole compose and created a complete new environment, deleted the old one, all volumes deleted etc. version: "3.9"
services:
db_recipes:
restart: always
image: postgres:15-alpine
container_name: tandoor_db
volumes:
- ./data:/var/lib/postgresql/data
- ./backup:/backup
environment:
- TZ=${TZ}
- POSTGRES_PORT=${POSTGRES_PORT}
- POSTGRES_USER=${POSTGRES_USER}
- POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
- POSTGRES_DB=${POSTGRES_DB}
web_recipes:
restart: always
image: vabene1111/recipes:1.5.11
container_name: tandoor_web
environment:
- ALLOWED_HOSTS=${ALLOWED_HOSTS}
- SECRET_KEY=${SECRET_KEY}
- TZ=${TZ}
- DB_ENGINE=${DB_ENGINE}
- POSTGRES_HOST=${POSTGRES_HOST}
- POSTGRES_PORT=${POSTGRES_PORT}
- POSTGRES_USER=${POSTGRES_USER}
- POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
- POSTGRES_DB=${POSTGRES_DB}
- FRACTION_PREF_DEFAULT=${FRACTION_PREF_DEFAULT}
- COMMENT_PREF_DEFAULT=${COMMENT_PREF_DEFAULT}
- SHOPPING_MIN_AUTOSYNC_INTERVAL=${SHOPPING_MIN_AUTOSYNC_INTERVAL}
- EMAIL_HOST=${EMAIL_HOST}
- EMAIL_PORT=${EMAIL_PORT}
- EMAIL_HOST_USER=${EMAIL_HOST_USER}
- EMAIL_HOST_PASSWORD=${EMAIL_HOST_PASSWORD}
- EMAIL_USE_TLS=${EMAIL_USE_TLS}
- EMAIL_USE_SSL=${EMAIL_USE_SSL}
- DEFAULT_FROM_EMAIL=${DEFAULT_FROM_EMAIL}
- ACCOUNT_EMAIL_SUBJECT_PREFIX=${ACCOUNT_EMAIL_SUBJECT_PREFIX}
- ENABLE_SIGNUP=${ENABLE_SIGNUP}
- ENABLE_PDF_EXPORT=${ENABLE_PDF_EXPORT}
- SOCIAL_DEFAULT_ACCESS=${SOCIAL_DEFAULT_ACCESS}
- SORT_TREE_BY_NAME=${SORT_TREE_BY_NAME}
- GUNICORN_MEDIA=${GUNICORN_MEDIA}
- DEBUG=${DEBUG}
- DISABLE_TREE_FIX_STARTUP=${DISABLE_TREE_FIX_STARTUP}
volumes:
- ./staticfiles:/opt/recipes/staticfiles
- ./nginx_config:/opt/recipes/nginx/conf.d
- ./mediafiles:/opt/recipes/mediafiles
depends_on:
- db_recipes
nginx_recipes:
image: nginx:mainline-alpine
restart: always
container_name: tandoor_nginx
ports:
- 8070:80
depends_on:
- web_recipes
volumes:
- ./nginx_config:/etc/nginx/conf.d:ro
- ./staticfiles:/static:ro
- ./mediafiles:/media:ro
volumes:
nginx_config: null
staticfiles: null
mediafiles: null
postgresql: null
networks: {}this one the .env file for this stack: ALLOWED_HOSTS="*"
SECRET_KEY=###############
TZ=Europe/Berlin
DB_ENGINE=django.db.backends.postgresql
POSTGRES_HOST=db_recipes
POSTGRES_PORT=5432
POSTGRES_USER=djangouser
POSTGRES_PASSWORD=###############
POSTGRES_DB=djangodb
FRACTION_PREF_DEFAULT=1
COMMENT_PREF_DEFAULT=1
SHOPPING_MIN_AUTOSYNC_INTERVAL=5
EMAIL_HOST=###############
EMAIL_PORT=587
EMAIL_HOST_USER=###############
EMAIL_HOST_PASSWORD=###############
EMAIL_USE_TLS=1
EMAIL_USE_SSL=0
DEFAULT_FROM_EMAIL=###############
ACCOUNT_EMAIL_SUBJECT_PREFIX="###############"
ENABLE_SIGNUP=1
ENABLE_PDF_EXPORT=1
SOCIAL_DEFAULT_ACCESS=0
SORT_TREE_BY_NAME=1
GUNICORN_MEDIA=0
DEBUG=1
DISABLE_TREE_FIX_STARTUP=1This leads to a not accessible webui at all. I can't even do the normal localipadress:port stuff to get access to it. I will post docker stuff from the previous installation in a few minutes, this here was all done with a fresh new installation |
|
is that full log or did you truncate it? those migrations don't look complete. |
that was ofc truncated, but for this evening I will stop here, I did the roleback to backup where 1.5.10 was working and updated to 1.5.11 and here is the complete log after a fresh start of the 1.5.11 with the files from a previous 1.5.10 installation: |
|
duplicate #2894 |
here the not truncated one with a complete fresh docker compose (I just added _test to all names of the containers etc.) |
|
ok, so we wait for the fix :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tandoor Version
1.5.11
Setup
Docker / Docker-Compose
Reverse Proxy
Nginx Proxy Manager (NPM)
Other
No response
Bug description
I updated my environment on docker compose with the following docker compose file:
It doesn't matter if I use local IP or DNS to access the IP.
If I use the tag on the docker image to revert back to 1.5.10 everything works.
Relevant logs
This leads instant to the error:
The text was updated successfully, but these errors were encountered: