mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 12:56:59 +00:00
[GH-ISSUE #8480] [Bug] TLS 1.3 + Firefox: login issues #3876
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#3876
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jbhanks on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8480
Bug Description
I just posted this to the Appflowy forum bug report section, but then I noticed it wasn't very active so I decided to also post here.
I just managed to start self-hosting AppFlowy Cloud in a Podman pod behind nginx and ran into a TLS issue that I’m trying to understand. I’m hoping someone here can confirm whether this is expected/known/something worth investigating.
Setup
What I’m seeing
When nginx is configured to only allow TLS 1.3:
ssl_protocols TLSv1.3;The login request returns me to the login page without any visible error.
No requests appear in nginx access logs at all. I am however logged in, as going to the main login page gives me my workspace.
tcpdumpdoes show a TCP/TLS handshake attempt from the client, followed by an immediate close.If I change nginx to allow TLS 1.2 + TLS 1.3:
ssl_protocols TLSv1.3 TLSv1.2;Why I’m confused
Everything I’ve read suggests:
So I am uncertain whether:
I was able to get TLS 1.3–only working previously for a few minutes, but I haven’t been able to reliably reproduce it via automation yet.
Questions
I’m happy to provide nginx config snippets or packet traces if helpful.
Thanks in advance — I’d like to run TLS 1.3–only if possible, but don’t want to fight undefined behavior.
Also, it took a bit of doing to get the Podman set up work, is that something people here would be interested in a post about?
How to Reproduce
Set up Appflowy self-hosted behind nginx with TLS 1.3 only. Try logging in from Firefox. If you want to try to reproduce my setup, the entire deployment is here: https://github.com/jbhanks/appflowy-on-vps-setup
Expected Behavior
Correct login credentials should take me to my workspace.
Operating System
Alma Linux
AppFlowy Version(s)
AppFlowy Cloud version:0.12.1
Screenshots
No response
Additional Context
No response