You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to self-host AppFlowy Cloud on my home NAS. After setting up and running the Cloud container on my NAS, I went to login to AppFlowy on my desktop (after changing Cloud Settings to point to my NAS' VPN IP address) but every time I try and login, I get a "Something went wrong" error message.
After following another bug report here, I tried navigating to /gotrue/settings for my NAS' VPN IP address and couldn't connect. And I forget what I did in order to get this error popup in the AppFlowy desktop app, but I did end up getting this error (see screenshot).
How to Reproduce
Setup self-hosted AppFlowy Cloud server
Use VPN on the server
Use AppFlowy desktop app with self-hosting settings pointing to VPN server address
Attempt to login with any OAuth provider
Expected Behavior
Expected to be able to login and use AppFlowy.
Operating System
Linux server, Windows client
AppFlowy Version(s)
0.7.0
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Bug Description
I am attempting to self-host AppFlowy Cloud on my home NAS. After setting up and running the Cloud container on my NAS, I went to login to AppFlowy on my desktop (after changing Cloud Settings to point to my NAS' VPN IP address) but every time I try and login, I get a "Something went wrong" error message.
After following another bug report here, I tried navigating to /gotrue/settings for my NAS' VPN IP address and couldn't connect. And I forget what I did in order to get this error popup in the AppFlowy desktop app, but I did end up getting this error (see screenshot).
How to Reproduce
Expected Behavior
Expected to be able to login and use AppFlowy.
Operating System
Linux server, Windows client
AppFlowy Version(s)
0.7.0
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: