Login issues #794

jc-frosty · 2025-10-25T00:37:22Z

jc-frosty
Oct 25, 2025

I have a grampsweb instance that I updated. I enabled a OIDC custom provider and tried using it (the error was that the email already exists so it is not an issue). When I tried to login with either of my accounts with OIDC on or off (Environment variable) in either safari or Firefox, I would very briefly get a loading bar and then would be dropped at the login screen with blank fields and no error (assuming an "incorrect password error" style of error would be displayed if I entered in the credential properly)

Gramps web should be on 25.10.0.1 as I am using docker compose and latest.

Is this an issue with my setup or is it a bug?

Answered by jonade

Oct 28, 2025

Is this not the issue that was (presumably) fixed in #798 as part of 25.10.1? Your screenshot shows it's still on 25.10.0

View full answer

jc-frosty · 2025-10-28T00:06:08Z

jc-frosty
Oct 28, 2025
Author

I think it is a bug because I had a computer logged in with the admin account and added a temp user which is unable to login on an Firefox.
If you want to see the effect yourself
genealogy.champeaus.org
username: temp
password: grampspass

I was able to get this image

2 replies

jc-frosty Oct 28, 2025
Author

Here is the docker-compose with secrets stripped:
`
services:
grampsweb: &grampsweb
image: ghcr.io/gramps-project/grampsweb:latest
restart: always
ports:
- "5000:5000" # host:docker
environment:
GRAMPSWEB_TREE: "Gramps Web" # will create a new tree if not exists
GRAMPSWEB_CELERY_CONFIG__broker_url: "redis://grampsweb_redis:6379/0"
GRAMPSWEB_CELERY_CONFIG__result_backend: "redis://grampsweb_redis:6379/0"
GRAMPSWEB_RATELIMIT_STORAGE_URI: redis://grampsweb_redis:6379/1
GRAMPSWEB_OIDC_ENABLED: False
GRAMPSWEB_OIDC_ISSUER: "https://id.champeaus.net"
GRAMPSWEB_OIDC_CLIENT_ID: "Removede"
GRAMPSWEB_OIDC_CLIENT_SECRET: "Removed"
GRAMPSWEB_OIDC_NAME: "PocketID"
GRAMPSWEB_OIDC_SCOPES: "openid email profile"
GRAMPSWEB_OIDC_GROUP_MEMBER: "gramps_members"
GRAMPSWEB_OIDC_GROUP_ADMIN: "gramps_admins"
depends_on:
- grampsweb_redis
volumes:
- gramps_users:/app/users # persist user database
- gramps_index:/app/indexdir # persist search index
- gramps_thumb_cache:/app/thumbnail_cache # persist thumbnails
- gramps_cache:/app/cache # persist export and report caches
- gramps_secret:/app/secret # persist flask secret
- gramps_db:/root/.gramps/grampsdb # persist Gramps database
- gramps_media:/app/media # persist media files
- gramps_tmp:/tmp

grampsweb_celery:
<<: *grampsweb # YAML merge key copying the entire grampsweb service config
ports: []
container_name: grampsweb_celery
depends_on:
- grampsweb_redis
command: celery -A gramps_webapi.celery worker --loglevel=INFO --concurrency=2

grampsweb_redis:
image: docker.io/library/redis:7.2.4-alpine
container_name: grampsweb_redis
restart: always

volumes:
gramps_users:
gramps_index:
gramps_thumb_cache:
gramps_cache:
gramps_secret:
gramps_db:
gramps_media:
gramps_tmp:
`

jc-frosty Oct 28, 2025
Author

Some consistency in the logs of an error, though the times are weird.
`grampsweb-1 | (gunicorn:18): Gtk-CRITICAL **: 00:26:45.308: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

grampsweb-1 | [2025-10-25 12:51:53 +0000] [17] [WARNING] Invalid request from ip=138.68.103.103: Invalid HTTP request line: ''

grampsweb-1 | [2025-10-25 18:23:58 +0000] [19] [WARNING] Invalid request from ip=3.131.215.38: Invalid HTTP request line: 'SSH-2.0-Go'

grampsweb-1 | [2025-10-25 22:18:09 +0000] [12] [WARNING] Invalid request from ip=162.142.125.125: Invalid HTTP Version: (2, 0)

grampsweb-1 | [2025-10-25 22:18:13 +0000] [12] [WARNING] Invalid request from ip=162.142.125.125: Invalid HTTP Version: (2, 0)

grampsweb-1 | [2025-10-26 00:40:12 +0000] [19] [WARNING] Invalid request from ip=194.0.234.12: Invalid HTTP request line: '\x03\x00\x00/*à\x00\x00\x00\x00\x00Cookie: mstshash=Administr'

grampsweb-1 | [2025-10-26 03:25:28 +0000] [13] [WARNING] Invalid request from ip=194.0.234.12: Invalid HTTP request line: '\x03\x00\x00/*à\x00\x00\x00\x00\x00Cookie: mstshash=Administr'

grampsweb-1 | [2025-10-26 09:12:16 +0000] [16] [WARNING] Invalid request from ip=167.94.138.122: Invalid HTTP Version: (2, 0)

grampsweb-1 | [2025-10-26 09:12:20 +0000] [19] [WARNING] Invalid request from ip=167.94.138.122: Invalid HTTP Version: (2, 0)

grampsweb-1 | [2025-10-26 19:10:53 +0000] [17] [WARNING] Invalid request from ip=3.131.215.38: Invalid HTTP request line: 'SSH-2.0-Go'

grampsweb-1 | [2025-10-27 09:35:20 +0000] [13] [WARNING] Invalid request from ip=85.208.84.172: Invalid HTTP request line: '\x03\x00\x00/*à\x00\x00\x00\x00\x00Cookie: mstshash=Administr'

grampsweb-1 | [2025-10-27 10:02:32 +0000] [17] [WARNING] Invalid request from ip=66.132.153.133: Invalid HTTP Version: (2, 0)

grampsweb-1 | [2025-10-27 10:02:37 +0000] [15] [WARNING] Invalid request from ip=66.132.153.133: Invalid HTTP Version: (2, 0)

grampsweb-1 | [2025-10-27 10:45:28 +0000] [13] [WARNING] Invalid request from ip=85.208.84.172: Invalid HTTP request line: '\x03\x00\x00/*à\x00\x00\x00\x00\x00Cookie: mstshash=Administr'

grampsweb-1 | [2025-10-27 12:10:07 +0000] [16] [WARNING] Invalid request from ip=85.208.84.172: Invalid HTTP request line: '\x03\x00\x00/*à\x00\x00\x00\x00\x00Cookie: mstshash=Administr'

grampsweb-1 | [2025-10-27 16:34:02 +0000] [17] [WARNING] Invalid request from ip=165.22.25.247: Invalid HTTP request line: ''

grampsweb-1 | [2025-10-27 18:36:42 +0000] [19] [WARNING] Invalid request from ip=3.130.96.91: Invalid HTTP request line: 'SSH-2.0-Go'

grampsweb-1 | [2025-10-27 18:46:46 +0000] [18] [WARNING] Invalid request from ip=185.170.144.3: Invalid HTTP request line: '\x03\x00\x00/*à\x00\x00\x00\x00\x00Cookie: mstshash=Administr'

grampsweb-1 | [2025-10-27 19:31:48 +0000] [15] [WARNING] Invalid request from ip=3.132.23.201: Invalid HTTP request line: 'SSH-2.0-Go'

grampsweb-1 | [2025-10-27 20:15:23 +0000] [17] [WARNING] Invalid request from ip=86.54.25.167: Invalid HTTP request line: '\x03\x00\x00/*à\x00\x00\x00\x00\x00Cookie: mstshash=Administr'

grampsweb-1 | [2025-10-27 20:18:12 +0000] [12] [WARNING] Invalid request from ip=86.54.25.167: Invalid HTTP request line: '\x03\x00\x00/*à\x00\x00\x00\x00\x00Cookie: mstshash=Administr'`

jc-frosty · 2025-10-28T00:31:40Z

jc-frosty
Oct 28, 2025
Author

With OIDC, it there was an issue with using gramps not using https and once I figure that out, I found out (read I forgot) about it not able to link accounts and handling an account with an email already in use with a plain error (It did describe the issue though unlike the error for the OIDC and http).

0 replies

jonade · 2025-10-28T08:03:14Z

jonade
Oct 28, 2025

Is this not the issue that was (presumably) fixed in #798 as part of 25.10.1? Your screenshot shows it's still on 25.10.0

2 replies

DavidMStraub Oct 28, 2025
Maintainer

Indeed. #797 is the issue.

jc-frosty Oct 28, 2025
Author

It was. I pulled when 25.10.0.1 was out so I thought it upgraded to that. Thanks. (Edit: Just realized you typed 25.10.1 and not 25.10.0.1)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Login issues #794

Uh oh!

{{title}}

Uh oh!

Replies: 3 comments 4 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Login issues #794

Uh oh!

jc-frosty Oct 25, 2025

Replies: 3 comments · 4 replies

Uh oh!

jc-frosty Oct 28, 2025 Author

Uh oh!

jc-frosty Oct 28, 2025 Author

Uh oh!

jc-frosty Oct 28, 2025 Author

Uh oh!

jc-frosty Oct 28, 2025 Author

Uh oh!

jonade Oct 28, 2025

Uh oh!

DavidMStraub Oct 28, 2025 Maintainer

Uh oh!

Uh oh!

jc-frosty Oct 28, 2025 Author

jc-frosty
Oct 25, 2025

Replies: 3 comments 4 replies

jc-frosty
Oct 28, 2025
Author

jc-frosty Oct 28, 2025
Author

jc-frosty Oct 28, 2025
Author

jc-frosty
Oct 28, 2025
Author

jonade
Oct 28, 2025

DavidMStraub Oct 28, 2025
Maintainer

jc-frosty Oct 28, 2025
Author