​Unable to sign in / sign up into self-hosted version about affine HOT 22 CLOSED

@NeoHuncho @christianpedersen @HitchRait
Hey guys.

I helped a self-hoster solve a similar problem yesterday because he did not configure AFFINE_SERVER_HOST correctly. This variable defaults to localhost, and he is using ip to access his server. Please ensure that AFFINE_SERVER_HOST and AFFINE_SERVER_PORT are consistent with the url used for browser access.

https://docs.affine.pro/docs/self-host-affine/run-affine-with-custom-options

from affine.

Hi @EYHN!

That fixed it for me, thank you!

from affine.

works，thanks.

"Docker Compose will generate AFFiNE configuration files within the ~/.affine/self-host/config directory on the host system after the initial startup."

This statement should be emphasized in bold; initially, I thought it was written in the shell's environment variables.

from affine.

@attorneyatlaw I've written a tutorial for me, for installing AFFiNE on a VPS server, but I use apache not nginx.
link tutorial

with theses variables environment :

.../...
     AFFINE_SERVER_HOST=localhost
     AFFINE_SERVER_PORT=3010
     AFFINE_SERVER_HTTPS=false
.../...

from affine.

Issue Status: ✅ Answered

✅ Answered

The issue actually turned out to be a question or a misunderstanding, and it has been answered or resolved.

^{_{This is an automatic reply by the bot.}}

from affine.

did you get any suspicious logs from your container?

from affine.

I got the same issue with the latest version. Nothing in logs. In Chrome console the following error appears:

use-current-user.ts:70 {}
(anonymous) @ use-current-user.ts:70
Promise.then (async)
reload @ use-current-user.ts:69
(anonymous) @ sign-in-with-password.tsx:49
await in (anonymous) (async)
(anonymous) @ affine-async-hooks.ts:25
eI @ react-dom.production.min.js:54
eB @ react-dom.production.min.js:54
(anonymous) @ react-dom.production.min.js:55
t7 @ react-dom.production.min.js:55
re @ react-dom.production.min.js:106
(anonymous) @ react-dom.production.min.js:117
oP @ react-dom.production.min.js:274
eM @ react-dom.production.min.js:52
ru @ react-dom.production.min.js:109
nI @ react-dom.production.min.js:74
nO @ react-dom.production.min.js:73

from affine.

I have the same issue, the error is coming from this frontend hook:
use-current-user.ts:70

return mutate().then(e => {
       console.error(e);
     });
   },

The e object is empty.

from affine.

Hi @EYHN, thanks for the quick reply. Is this environment variable new? As I didn't have it in my docker-compose,but v0.12 was working fine without it.

from affine.

Worked for me too, thanks!

from affine.

Hi @EYHN, thanks for the quick reply. Is this environment variable new? As I didn't have it in my docker-compose,but v0.12 was working fine without it.

I honestly don't know why 0.12 works, but I'll add a reminder about this to the selfhost tutorial.

from affine.

Thanks, @EYHN ! It worked.

The last thing to mention: I have a VPN network and so my AFFiNE server has 2 IP's (local and VPN) and this solution doesn't work with another IP not mentioned in AFFINE_SERVER_HOST. Though it worked with my previous version (12).

I have a very specific use case, but hope to see it working regardless of IP address.

from affine.

Could you give me an example code(script, affine.js?) to fix this?
The below is correct? (my environment is ubuntu, arm64)

AFFINE_SERVER_HOST='https://affine.example.com'
AFFINE_SERVER_PORT=3010(right? I am now using affine behind nginx proxy manager)
AFFINE_SERVER_HTTPS=true;

I installed a stable version(self-host) but log-in just close the window and not log-in actually.
So my affine self host is not switched from local to cloud.

from affine.

Could you give me an example code(script, affine.js?) to fix this? The below is correct? (my environment is ubuntu, arm64)

AFFINE_SERVER_HOST='https://affine.example.com' AFFINE_SERVER_PORT=3010(right? I am now using affine behind nginx proxy manager) AFFINE_SERVER_HTTPS=true;

I installed a stable version(self-host) but log-in just close the window and not log-in actually. So my affine self host is not switched from local to cloud.

@attorneyatlaw The configuration here should be consistent with the URL you ultimately access with your browser. If the port number is 443 after you go through nginx, then AFFINE_SERVER_PORT should be 443

from affine.

not work for me.
log-in does not work.

from affine.

not work for me. log-in does not work.

@attorneyatlaw I noticed that your AFFINE_SERVER_HOST is wrong, it should not contain https://

If issue still exists, please tell me your configuration and what URL you use to access affine.

from affine.

same problem with selfhost, my configuration is :

.../...
     AFFINE_SERVER_HOST=affine.example.com
     AFFINE_SERVER_PORT=3010
     AFFINE_SERVER_HTTPS=true
.../...

from affine.

I tried without https:// and it worked. after log-in, mine is changed from local to AFFiNE Cloud.
I wrote down only the below in the yml file.

AFFINE_SERVER_HOST=affine.example.com

log-in worked but another problem happened.
The problem is that my affine is reset for the next time log-in.

Connection to my affine URL is directed to
https://af.example.com/onboarding (initialization setup display including 'AFFiNE is a workspace with fully merged docs,
whiteboards and databases' )

Initialization setup process happens again and again(when session is out, connected with other web browser).
Whenever I log-in, Demo Workspace is generated.

I used a stable image(ghcr.io/toeverything/affine-graphql:stable).

from affine.

@attorneyatlaw When start on a new browser, affine will always create a new workspace (just a temporary workspace stored locally in the browser).

You can ignore it and click the workspace button from the upper sidebar to sign in to your account.

If you click Sign in and enable, it means logging in and upload this local workspace into cloud.

If you are experiencing other issues, please provide a screen recording.

from affine.

You mean that whenever I connect my affine URL to sign-in, I should see the below and click to go to the next steps(clicking 3 next buttons, 1 Get Started button and 1 Got it! button), right?
(I use my web browser with the setting of clearing all data when the browser is closed.)

The above process is too burdensome.

I hope I can see the sign-up/sign display directly whenever I connect my affine URL.
I am curious that others use affine self host like this.

from affine.

@attorneyatlaw This onboarding animation has been removed from the web version. You can try updating to the latest version.

from affine.

@EYHN I tried the stable version again(2024. 03. 28. 09:53 AM UTC +9) and no onboarding animation is shown!
Thank for your help and effort.

from affine.