8000 Unable to verify session · Issue #733 · girlbossceo/conduwuit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Apr 11, 2025. It is now read-only.

Unable to verify session #733

Closed
OptimoSupreme opened this issue Apr 7, 2025 · 8 comments
Closed

Unable to verify session #733

OptimoSupreme opened this issue Apr 7, 2025 · 8 comments

Comments

@OptimoSupreme
Copy link
OptimoSupreme commented Apr 7, 2025 •
edited
Loading

I am running a Conduwuit + Caddy setup with Podman for both, I 8000 can provide my quadlets & Caddyfile if requested. I am having an issue where I cannot verify a session in the Element client (I've tried mobile and flatpak apps). I looks as though my verification via passphrase is successful, but it doesn't fix anything.

I am repeatedly seeing this log:

2025-04-07T01:18:26.614476Z  WARN ... someurl.com failed to provide backfill ... [403 / M_FORBIDDEN] Host not in room.
2025-04-07T01:18:26.616003Z  WARN ... someurl.com failed to provide backfill ... [403 / M_FORBIDDEN] Host not in room.

Image
Image
@OptimoSupreme
Copy link
Author

Wondering if this might possibly be relevant but not sure.

@ewwwin
Copy link
ewwwin commented Apr 8, 2025

I'm also having this issue lately, with multiple clients - have tried to work around it in nheko, Cinny, Element web, Element iOS, and Element X iOS and none of them seem happy.

@girlbossceo
Copy link
Owner

I just pushed some stuff to main branch to maybe help with this, can you see if it works?

@OptimoSupreme
Copy link
Author

I can test this as soon as the OCI containers update, I think the latest one I’m seeing now is about four days old.

@OptimoSupreme
Copy link
Author

I am pulling ghcr.io/girlbossceo/conduwuit:main and for some reason it's saying the image is 2 weeks old? Very strange. I even pulled ghcr.io/girlbossceo/conduwuit:main@sha256:94a5c9f4e8e9e41fe6be61d12eb95b7c86c24a337fd216a1a5f31cde9bafe292 and it says the same thing, but it must be the new one? I'm not sure what's up with that. Unfortunately though, if it is the new one the problem is not resolved for me :(

@GigiaJ
Copy link
GigiaJ commented Apr 8, 2025

I was having the same issue and have pulled the changes. It does seem to have solved the issue for me at least.
I am using Dockerhub instead of Github container registry, however.

@OptimoSupreme
Copy link
Author

Yayyyyy it's working for me now too! I thought I was gonna have to tell you it didn't work, but something compelled me to remove the app data from my Element flatpak and then I it was good! Thanks @girlbossceo 🎆

@ewwwin
Copy link
ewwwin commented Apr 8, 2025

Fix is working for me as well, thanks! I'd managed to get my sessions in a weird broken state in the meantime so I needed to take a local backup of my keys, sign out and back into all my clients, and reimport the keys in order to get everything working properly.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@GigiaJ @OptimoSupreme @girlbossceo @ewwwin
0